CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/screen-reader-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a strong, action-dense overview: exact tool pairings, keystrokes, and per-issue fixes make it immediately executable, and detail is properly deferred to a real one-level-deep reference file. The main weakness is the 'Explain' section and parts of the intro restating background knowledge Claude already has, which could be cut or trimmed without losing actionability.

DimensionReasoningScore

Conciseness

The Check and Fix sections are tight and instruction-dense, but the 'Explain' section ('Screen readers convert web content to audio or braille output... a parallel representation of the DOM constructed from HTML semantics and ARIA attributes') and parts of the intro ('Screen readers are the primary interface for blind users...') re-explain concepts Claude already knows. This is more than anchor 4's 'minor instances that could be trimmed', fitting 'mostly efficient but includes some unnecessary explanation'.

3 / 5

Actionability

Fully executable, instruction-only guidance: exact screen reader/browser pairings ('NVDA + Chrome (Windows) or VoiceOver + Safari (macOS)'), exact keystrokes ('H key in NVDA/JAWS', 'D/R keys', 'Insert+F7'), and named fixes per common issue ('aria-live=polite', 'aria-describedby', 'return focus to the trigger element', 'roving tabindex for menus, arrow keys for tabs'). Specific examples cover the common cases, matching the anchor-5 example's copy-paste-ready command quality.

5 / 5

Workflow Clarity

A clear sequence is present (Quick Reference → Check → Fix → Explain → Code Review) with concrete verification targets ('all interactive elements are reachable and announced with name + role + state'), and the Code Review section says to 'note how to verify the fix'. However, there is no explicit re-test-after-fix feedback loop ('apply fix, then re-run the screen reader check'), so it lands at anchor 4 rather than 5's 'explicit validation steps; feedback loops for error recovery'. This is a non-destructive audit skill, so the destructive-batch cap does not apply.

4 / 5

Progressive Disclosure

The body is a lean, well-sectioned overview (~40 lines) and the detailed material (implementation details, code examples, framework guidance) is split into a single, clearly signaled, one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — a file that exists in the bundle. This matches 'clear overview with well-signaled one-level-deep references; content appropriately split'.

5 / 5

Total

17

/

20

Passed

Description

50%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 has an explicit, well-developed 'Use when...' trigger clause with good context coverage, but it never states what the skill does or names the core technology. A user asking to 'test with a screen reader' or mentioning NVDA/VoiceOver would not match any term in this description. Adding the skill's action and reader names would substantially improve it.

Suggestions

State the 'what' explicitly, e.g. prefix with 'Test web pages and user flows with screen readers (NVDA, JAWS, VoiceOver, TalkBack) to verify announcements, reading order, focus management, and keyboard operability.'

Add the central natural trigger terms users would actually say: 'screen reader', 'NVDA', 'JAWS', 'VoiceOver', 'TalkBack', and the common synonym 'a11y'.

Narrow the opening scope from the broad 'accessibility audits' to assistive-technology/manual testing specifically, so it does not compete with general accessibility-scan or WCAG skills.

DimensionReasoningScore

Specificity

Names the domain ('accessibility audits of web pages, components, or full user flows') and concrete application contexts ('custom JavaScript widgets, single-page applications, dynamically updated content, modal dialogs, and forms with validation'), but lists no concrete testing actions. It never states what the skill actually does (screen reader testing), so it does not reach anchor 4's 'several specific actions', while its rich domain and context naming exceeds anchor 2's bare domain mention.

3 / 5

Completeness

The 'when' is explicit and detailed ('Use when performing accessibility audits... Particularly important for custom JavaScript widgets...'), but the 'what' is absent — the description never states the skill's action (testing with screen readers). It cannot score 4 ('has both what and when'), but the comprehensive, explicit trigger guidance lifts it above anchor 2's minimal 'Use when working with documents' pattern.

3 / 5

Trigger Term Quality

Relevant natural phrases are present ('accessibility audits', 'assistive technology', 'modal dialogs', 'forms with validation'), but the most central natural terms users would say are missing: 'screen reader', 'NVDA', 'JAWS', 'VoiceOver', 'TalkBack', 'a11y'. Anchor 4 allows only 'a few natural terms missing'; omitting the core trigger term ('screen reader') entirely is a bigger gap, so it sits at anchor 3.

3 / 5

Distinctiveness Conflict Risk

The assistive-technology framing is somewhat specific, but because the description never names 'screen reader' or the reader software, 'accessibility audits of web pages' would plausibly trigger for related skills (WCAG compliance, automated accessibility scanning, keyboard navigation testing). This matches 'somewhat specific but could still overlap with similar skills' rather than anchor 4's 'minor overlap risk'.

3 / 5

Total

12

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/screen-reader-testing/SKILL.md

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.