
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS
by wshobsonFree
Description
screen-reader-testing is an agent skill from the wshobson/agents collection that gives a practical guide to testing web applications with screen readers, the assistive technology that many blind and low-vision people use. It covers the major screen readers, including VoiceOver, NVDA and JAWS, because each announces the same page slightly differently and a page can work in one and fail in another. The skill covers validating screen reader compatibility, testing ARIA implementations, where incorrect roles or labels can make an interface confusing, verifying that forms are labeled and their errors are announced, and testing whether dynamic content changes are announced when they happen, such as a status message or a new search result. It also covers checking navigation, including how users move between headings, landmarks and links, and debugging the assistive technology issues that appear in production. The skill applies when validating screen reader support, testing ARIA, debugging assistive technology problems, checking form accessibility, testing dynamic content announcements, and ensuring navigation is usable without sight. It is most useful as a test plan that a team runs with real screen readers, because automated checks miss many of these problems. The agent can write the test checklist and help fix the markup, and people who use these tools should review the results. The skill is installed with the skills CLI from the wshobson/agents repository. Its skills.sh page showed about 10.4K installs and passing results from three security audits at the time of the scan.…
Highlights
- Testing with VoiceOver, NVDA and JAWS
- ARIA implementation checks
- Form labels and error announcements
- Dynamic content announcement tests
- Navigation by headings, landmarks and links
- Installs with the skills CLI
Ratings & Reviews
No ratings yet
Be the first to rate screen-reader-testing.
People also visit
screen-reader-testing FAQ
Which screen readers does it cover?
VoiceOver, NVDA and JAWS.
What does it test?
Screen reader compatibility, ARIA, form labels and errors, dynamic announcements and navigation.
Can automated tests replace this?
The skill is a guide for testing with real screen readers, because automated checks miss many accessibility problems.
Who is it for?
Teams building web applications that need to work for screen reader users.
How do I install it?
Run npx skills add https://github.com/wshobson/agents --skill screen-reader-testing.
What security audits does it have?
skills.sh lists three audits: Gen Agent Trust Hub Pass, Socket Pass and Snyk Pass.
What are the best screen-reader-testing alternatives?
Popular alternatives to screen-reader-testing include a11y-debugging, react-testing and accessibility. See all screen-reader-testing alternatives





