CtrlK
BlogDocsLog inGet started
Tessl Logo

screen-reader-testing

Use when performing accessibility audits of web pages, components, or full user flows. Applies to all web content accessed via assistive technology. Particularly important for custom JavaScript widgets, single-page applications, dynamically updated content, modal dialogs, and forms with validation.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and actionable with a clear single-level reference to a real rule.md file. Its main weakness is mild over-explanation of concepts Claude already knows in the 'Explain' section and the absence of explicit validation checkpoints in the test workflow.

Suggestions

Trim the 'Explain' section: drop the explanation of the accessibility tree and reading vs forms/application mode — Claude already knows these; keep only the screen-reader-specific quirks that are non-obvious.

Add an explicit validation step in the 'Check' workflow, e.g. 'After each fix, re-run the failing screen reader command and confirm the correct name/role/state is announced before moving on.'

Include at least one concrete code snippet in 'Fix' (e.g. a roving tabindex pattern or an aria-live region) so the guidance is copy-paste ready rather than prose.

DimensionReasoningScore

Conciseness

The body is largely lean and well-organized into Quick Reference / Check / Fix / Explain sections, but the 'Explain' section describes concepts Claude already knows (the accessibility tree, reading vs forms/application mode, virtual cursor), which is mild over-explanation that could be trimmed; this is the 4-anchor 'minor instances of over-explanation'.

4 / 5

Actionability

It gives concrete, executable guidance — specific screen reader + browser combos, key commands (H key, D/R keys, Insert+F7), and six numbered fixes with attribute names (aria-live='polite', roving tabindex, aria-describedby); minor gaps are that there is no copy-paste code snippet and the fixes are prose rather than examples, landing at 4.

4 / 5

Workflow Clarity

The 'Check' section sequences the test workflow clearly (choose 2 combos, navigate by keyboard, verify name/role/state, check dynamic content, manage focus) and 'Fix' enumerates issues with remedies, but there is no explicit validation checkpoint confirming the fix resolved the announcement, which is the 4-anchor 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview with well-signaled one-level-deep reference to references/rule.md (which exists as a real file), section headers organize the content, and detailed material is offloaded to that single reference, matching the 5-anchor clear-overview pattern.

5 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinct: it states concrete actions, opens with an explicit 'Use when' trigger, and covers natural synonyms a user would mention. It closely matches the rubric's strongest anchors across all four dimensions.

DimensionReasoningScore

Specificity

The description lists concrete actions and a clear domain ('performing accessibility audits of web pages, components, or full user flows') and enumerates specific contexts ('custom JavaScript widgets, single-page applications, dynamically updated content, modal dialogs, and forms with validation'), giving comprehensive coverage analogous to the 5-anchor example.

5 / 5

Completeness

It explicitly answers 'what' ('performing accessibility audits...') and 'when' via the 'Use when performing...' clause with concrete trigger phrases, mirroring the 5-anchor good example that pairs a what-clause with a Use-when clause.

5 / 5

Trigger Term Quality

It contains natural terms a user would say ('accessibility audits', 'web pages', 'components', 'user flows', 'modal dialogs', 'forms with validation') plus synonyms and the assistive-technology framing, matching the comprehensive synonym coverage of the 5 anchor.

5 / 5

Distinctiveness Conflict Risk

The accessibility/screen-reader-testing niche is specific and unlikely to fire for unrelated skills, with distinct triggers ('assistive technology', 'modal dialogs', 'SPA') and minimal overlap risk, matching the clear-niche 5 anchor.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.