Agent skill

Screen Reader Testing Skill: VoiceOver, NVDA and JAWS Guide

Screen reader testing is a wshobson agents skill that guides an AI coding agent through testing web apps with VoiceOver, NVDA, JAWS and TalkBack, with ready-made test scenarios.

Install
gh skill install wshobson/agents screen-reader-testing
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the screen reader testing skill?

Screen reader testing is a skill in wshobson/agents for validating web apps with VoiceOver, NVDA, JAWS, TalkBack and Narrator. It sets a minimum test matrix, explains browse and focus modes, and gives test patterns for modals, live regions and tab interfaces, with reference files per screen reader.

Screen reader testing is a skill in the accessibility-compliance plugin of wshobson/agents. It is a practical guide to checking a web application with real assistive technology rather than relying on automated scans alone.

The main SKILL.md holds the testing strategy and three common scenarios. Setup, commands and checklists for each screen reader sit in separate reference files the agent reads before testing.

What changes in your agent's output

  • Test plans name specific screen reader and browser pairs, starting with NVDA and Firefox, VoiceOver and Safari, and VoiceOver on iOS Safari.
  • Findings distinguish browse mode, focus or forms mode and application mode, since each behaves differently.
  • Modals, live regions and tab widgets are checked against known-good markup and keyboard behavior.
  • Dynamic content announcements and error states are tested, not only the happy path.
  • The agent logs role, name and state of an element to approximate what assistive technology sees.

Who it is for

Best for

  • Developers who must confirm ARIA work actually announces correctly.
  • QA planning a manual accessibility pass across several platforms.
  • Teams debugging a report that a widget is unusable with a screen reader.

Not for

  • Running a screen reader for you. An AI agent cannot listen to speech output, so a person must test.
  • Automated contrast or markup scanning, which belongs to an audit skill.
  • Native mobile app testing beyond the browser coverage it lists.

Use it with UiChemy

After UiChemy produces a WordPress page, run the same screen reader checks on the live page. UiChemy Figma to WordPress converts designs to editable pages, but accessibility still needs a human pass. Click Get Started on uichemy.com.