← ClaudeAtlas

screen-reader-test-authorlisted

Use when a feature needs manual screen-reader testing before sign-off: step-by-step scripts for NVDA, JAWS, VoiceOver or TalkBack with keystrokes and expected announcements, WCAG 2.2 checklists per page type, widget keystroke matrices and a guided session with a signed report.
testland/qa · ★ 13 · Testing & QA · score 80
Install: claude install-skill testland/qa
# screen-reader-test-author ## Overview Automated tools (axe-core, pa11y, Lighthouse) catch ~30-40% of accessibility issues - the structural ones. The remaining 60-70% require **manual screen-reader testing** by an actual human using NVDA / JAWS / VoiceOver / TalkBack. The team needs a repeatable script that any tester (not just the original author) can follow. This skill takes a user flow and produces that script: per-step keystroke + expected announcement. Two sibling artifact shapes live in references/: a per-archetype WCAG 2.2 checklist generator for spec-review-time acceptance criteria ([references/wcag-checklist.md](references/wcag-checklist.md)) and per-widget keystroke matrices for hand-run NVDA / VoiceOver passes ([references/widget-matrix.md](references/widget-matrix.md)). The "Running the session" section below turns script + checklist into a guided, signed session. ## When to use - A high-stakes feature ships and needs accessibility sign-off. - Automated a11y tools are green but the team wants confidence the actual screen-reader experience is good. - Onboarding a new accessibility tester - they need a script to follow until they internalize the conventions. - Documenting an "a11y regression repro" when a bug ships. ## Step 1 - Pick the screen reader Most a11y audit conventions cover at least: | Screen reader | Platform | Browser pairing | |---------------|----------------------|------------------------------| | NVDA |