screen-reader-testing Skill (wshobson) for Claude: What It Does and How to Install It

Gives Claude a practical guide to testing web apps with VoiceOver, NVDA, JAWS and TalkBack.

Installs: 10.9K; on skills.sh
Stars: 42.1K; on GitHub
Files: 4; besides SKILL.md
Updated: Oct 2026; last repo commit

This skill is a guide from wshobson's agents collection for testing web apps with real screen readers. It compares VoiceOver, NVDA, JAWS, TalkBack and Narrator, and sets a minimum test set of three screen reader and browser pairs plus an extended set of six. It also explains browse, focus and application modes.

SKILL.md includes accessible markup and focus code for a modal dialog, live regions and a tab interface, plus a snippet that logs an element's accessible name. Four reference files hold commands and checklists for VoiceOver on macOS and iOS, NVDA, and JAWS with TalkBack. It loads when you validate screen reader support or debug assistive technology issues.

Good for

Accessibility testers planning screen reader checks
Front-end developers fixing ARIA and focus issues
QA engineers writing test scripts for NVDA or VoiceOver
Teams that must cover iOS and Android

Install screen-reader-testing

Claude Code

Copy this prompt.

Install the screen-reader-testing skill in Claude Code. Run this command:

/plugin marketplace add wshobson/agents
/plugin install accessibility-compliance@claude-code-workflows

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Pick one route. The plugin routes install the whole accessibility-compliance plugin: 1 agent, 1 command and 2 skills (counted from the plugin folder in the repo tree, which has no hooks or MCP config files). The skills-only routes install just this skill, with no agents or commands. The guide is about testing with real screen readers: VoiceOver, NVDA, JAWS and TalkBack.

From the project README. Source.

What's in the skill

When it loads

Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.

Sections in SKILL.md

When to Use This Skill
Core Concepts
1. Major Screen Readers
2. Testing Priority
3. Screen Reader Modes
Common Test Scenarios
1. Modal Dialog
2. Live Regions
3. Tab Interface
Debugging Tips
Best Practices
Do's
Don'ts

Key facts

Author: wshobson (repo owner)
License: MIT
Installs on skills.sh: 10,919 (Nov 2, 2026)
GitHub stars: 42,081 for the whole wshobson/agents repo (Nov 2, 2026)
Last repo commit: Oct 30, 2026
What it includes: 5 files including SKILL.md: four reference files for VoiceOver (macOS and iOS), NVDA, and JAWS with TalkBack (no scripts)
Needs: The screen readers you want to test with, on matching devices. SKILL.md says to test with actual screen readers, not just simulators
Part of: The accessibility-compliance plugin (version 1.2.4) in wshobson/agents. Counted from the plugin folder: 1 agent, 1 command and 2 skills
Works in: Claude Code, Codex CLI, Cursor, OpenCode, Antigravity CLI, GitHub Copilot and Pi, per the README. Skills-only installers ask which tool you use

What it includes

VoiceOver, NVDA, JAWS, TalkBack and Narrator
A table of the five screen readers with their platform and usual browser.
Read · Screen reader overview
Minimum set of three, extended set of six
Minimum: NVDA with Firefox, VoiceOver with Safari on macOS, VoiceOver with Safari on iOS. The extended set adds JAWS with Chrome, TalkBack with Chrome and Narrator with Edge.
Read · Testing priority
Browse, focus and application modes
Explains which mode is used for reading, filling forms and custom widgets.
Read · Reading modes
Accessible markup and focus trap code
HTML for a dialog plus JavaScript that stores focus, moves it into the dialog, traps Tab and returns focus on close.
Write · Modal dialog scenario
Polite, assertive, progress and log regions
Markup for status messages, alerts, progress bars and logs.
Write · Live regions scenario
Tab roles with arrow-key navigation
HTML and keyboard handling for ArrowLeft, ArrowRight, Home and End.
Write · Tab interface scenario
Log an element's accessible name, role and state
A JavaScript function that prints what a screen reader would see for an element.
Read · Debugging snippet
Five do's and five don'ts
Includes testing with actual screen readers, keyboard first, browse and focus modes, and error states.
Read · Best practices
Setup, commands and a six-part checklist
references/voiceover.md covers page load, navigation, links and buttons, forms, dynamic content and tables, plus common issues.
Read · VoiceOver on macOS
Touch gestures for Safari testing
references/voiceover-ios.md has a table of five gestures and notes on rotor categories.
Read · VoiceOver on iOS
Setup, commands, modes and a test script
references/nvda.md has an NVDA test script for initial load, landmarks, headings, forms, interactive elements and dynamic content.
Read · NVDA
Setup and command lists for Windows and Android
references/jaws-talkback.md covers JAWS essentials and TalkBack setup and gestures.
Read · JAWS and TalkBack

From the official docs

Questions

What does the screen-reader-testing skill do?

It gives Claude a guide to testing web pages with screen readers. Claude uses it to plan which screen reader and browser pairs to cover, write test steps and review accessible markup.

How do I install screen-reader-testing?

Use the install box at the top of this page. It lists the plugin route and two skills-only commands: npx skills add wshobson/agents --skill screen-reader-testing and gh skill install wshobson/agents screen-reader-testing (GitHub CLI 2.90 or later), which skip the plugin's agents and commands.

Does it run screen reader tests for me?

No. It is a guide that bundles no scripts. SKILL.md says to test with actual screen readers, not just simulators.

Which screen readers should I test first?

SKILL.md's minimum set is NVDA with Firefox on Windows, VoiceOver with Safari on macOS and VoiceOver with Safari on iOS. The extended set adds JAWS with Chrome, TalkBack with Chrome and Narrator with Edge.

Does it cover mobile?

Yes. A VoiceOver on iOS reference covers touch gestures, and the TalkBack setup and gestures are in the JAWS and TalkBack reference. SKILL.md's don'ts include ignoring mobile.

Is this skill from Anthropic?

No. It is in wshobson/agents, a community collection. The skill sits in the accessibility-compliance plugin there.

Should I install the whole accessibility-compliance plugin?

Only if you want the rest. The README documents a plugin route for Claude Code and Codex. The plugin folder holds 1 agent, 1 command and 2 skills (screen-reader-testing, wcag-audit-patterns), and the repo tree shows no hooks or MCP config files in it. The install box offers the plugin and skills-only commands.

Does it work in Codex or Cursor?

The README documents Codex CLI as a plugin route and a skills-only install. For Cursor it points to a plugin marketplace and its setup docs, which we did not check, so follow the README there.

Is it safe?

The folder holds SKILL.md and four reference files and bundles no scripts. The files contain HTML and JavaScript examples, setup steps and key commands for each screen reader. Review any markup Claude changes in your app as you would any other edit.

Information

updated Nov 2, 2026

Repository: wshobson/agents
Folder: plugins/accessibility-compliance/skills/screen-reader-testing

wshobson/agents skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 7

screen-reader-testing SKILL.md · github.com
wshobson/agents README · github.com
accessibility-compliance plugin.json · github.com
screen-reader-testing voiceover.md · github.com
screen-reader-testing voiceover-ios.md · github.com
screen-reader-testing nvda.md · github.com
screen-reader-testing jaws-talkback.md · github.com