
Screen Reader Testing
Test web apps with VoiceOver, NVDA, JAWS and TalkBack for accessibility issues
- Repository
- wshobson/agents
- Stars
- 42,095
- Licence
- MIT
- Files
- 5 files
What it does
Once installed, the agent follows a structured guide for checking how websites and web apps sound to people who use screen readers, which are programs that read interface content aloud. It explains which screen reader and browser pairs to test, how to switch between reading and form-filling modes, and what to check for dialogs, live announcements, tabs and forms. It also suggests ARIA markup patterns and a small JavaScript helper for inspecting what a screen reader would see.
Great for
- Front-end developers checking that a new web feature works with assistive technology
- QA testers who need a checklist for VoiceOver, NVDA, JAWS or TalkBack passes
- Accessibility reviewers auditing modals, live regions, tabs and forms
Skip it if
- Replacing testing with real disabled users, since the guide itself says to test with actual screen readers and not simulators
- Non-web apps or native mobile UI beyond the iOS and Android screen reader basics it covers
- Anyone expecting legal compliance certification, as the skill gives testing guidance only and no conformance verdict
Try asking
- “Walk me through testing my checkout form with NVDA and Firefox”
- “Review this modal dialog's ARIA and focus handling for screen reader support”
- “Create a test plan for live status messages in my upload progress bar”
- “Which screen reader and browser combinations should I cover for minimum accessibility coverage?”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 5 original files, the MIT licence and an attribution note.
screen-reader-testing.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip screen-reader-testing.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip screen-reader-testing.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Give the agent your actual HTML or component code so it can check ARIA roles, names and focus handling against the examples.
- Still run the real screen reader yourself, because the skill's own advice is that simulators and visual checks are not enough.
- Ask for a specific screen reader and browser pair so the agent can use the matching setup and commands reference.
What's inside
- references/jaws-talkback.md
- references/nvda.md
- references/voiceover-ios.md
- references/voiceover.md
- SKILL.md
Redistributed unmodified from wshobson/agents under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.