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.

62

Quality

73%

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

72%

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

A well-structured, actionable testing skill with good progressive disclosure, weakened by an 'Explain' section that re-teaches known concepts and a workflow that lacks an explicit re-test verification loop.

Suggestions

Trim or remove the 'Explain' section's background on screen readers and the accessibility tree; assume Claude's competence and keep only non-obvious quirks.

Add an explicit feedback loop in the workflow, e.g. 'After each fix, re-run the screen reader navigation to confirm the announcement/name/role/state is now correct.'

Cut the motivational opening paragraph or condense it to one line so the actionable content starts sooner.

DimensionReasoningScore

Conciseness

Quick Reference, Check, and Fix are tight and concrete, but the 'Explain' section restates concepts Claude already knows (what screen readers are, the accessibility tree, reading vs forms mode) and the intro is partly motivational padding.

2 / 3

Actionability

It gives specific executable guidance — exact screen-reader keys (H, D/R, Insert+F7) and exact ARIA fixes (aria-live='polite', roving tabindex, aria-describedby) — which meets the actionability bar for an instruction-only skill.

3 / 3

Workflow Clarity

The Check→Fix sequence is present, but the re-test/verify feedback loop is only implicit (a passing nod in Code Review) rather than an explicit validation checkpoint after each fix.

2 / 3

Progressive Disclosure

The body is a well-sectioned overview (Quick Reference, Check, Fix, Explain, Code Review) that points to a real one-level-deep reference, references/rule.md, with a clearly signaled link.

3 / 3

Total

10

/

12

Passed

Description

75%

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

A well-formed description with explicit 'Use when' triggers and a clear accessibility niche, but it leans on one broad action and misses the most natural trigger term ('screen reader').

Suggestions

Add the natural trigger term 'screen reader' (and variants like 'a11y', 'screen reader testing') so users who say those phrases match this skill.

List a couple more concrete actions (e.g., 'verify keyboard reachability, check live-region announcements, validate focus management') to lift specificity from a single broad action to multiple concrete ones.

DimensionReasoningScore

Specificity

It names the domain and one action ('performing accessibility audits of web pages, components, or full user flows') but lists a single broad action rather than multiple concrete actions like extract/fill/merge, so it is not comprehensive enough for a 3.

2 / 3

Completeness

It explicitly answers both what ('performing accessibility audits... Applies to all web content accessed via assistive technology') and when via explicit triggers ('Use when...', 'Applies to...', 'Particularly important for...').

3 / 3

Trigger Term Quality

It includes relevant natural terms ('accessibility audits', 'web pages', 'modal dialogs', 'forms with validation') but omits the most common user phrasing — 'screen reader', 'a11y', 'WCAG' — so coverage is incomplete.

2 / 3

Distinctiveness Conflict Risk

The assistive-technology/screen-reader-testing niche with distinct triggers (custom JS widgets, SPAs, modal dialogs) is clearly scoped and unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.