screen-reader-testing

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.

by wshobson 39k GitHub stars MIT Updated Aug 24, 2026
screen-reader-testing skill by wshobson
screen-reader-testing — Testing skill by wshobson

Overview

screen-reader-testing is an open-source testing skill for Claude Code and compatible agents, published by wshobson. Its author describes it as: “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.”. The project has 39k stars on GitHub and is available under the MIT license. Add it to your setup with `/plugin marketplace add wshobson/agents`.

What screen-reader-testing does

Practical guide to testing web applications with screen readers for comprehensive accessibility validation.

What’s inside

The SKILL.md for screen-reader-testing is organised into these sections:

  • When to Use This Skill
  • Core Concepts
  • 1. Major Screen Readers
  • 2. Testing Priority
  • 3. Screen Reader Modes
  • VoiceOver (macOS)
  • Setup
  • Essential Commands
  • Testing Checklist
  • Common Issues & Fixes
  • NVDA (Windows)
  • Browse vs Focus Mode

Installation

Add screen-reader-testing to your agent with:

/plugin marketplace add wshobson/agents

Review a skill’s source before installing it — skills can instruct your agent to run commands. This command comes from the skill’s public repository, which is the source of truth for setup steps. New to skills? Read how to install Claude Code skills.

Supported agents

  • Claude Code — ships a claude code plugin marketplace
  • Codex — declared in the repository topics
  • Cursor — declared in the repository topics
  • OpenCode — declared in the repository topics
  • GitHub Copilot — declared in the repository topics
  • Antigravity — declared in the repository topics

License

screen-reader-testing is published under the MIT license.

Strengths

  • Clear MIT license — safe to read and adapt within its terms
  • Ships in wshobson/agents, an established project with 39,066 GitHub stars
  • Works with Claude Code, Codex, Cursor, OpenCode, GitHub Copilot, Antigravity
  • Actively maintained — repository updated in the last 90 days
  • Its repository gained 669 GitHub stars over the last 24 days

Author

wshobson 54 skills in the catalog · GitHub profile ↗
View skills

Topics

Alternatives to screen-reader-testing

Similar skills from other repositories:

Need a skill like this, tailored to your team?Build a custom skill →

Frequently asked questions

What does screen-reader-testing do?
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.
How do I install screen-reader-testing?
Run /plugin marketplace add wshobson/agents in your agent, then reload your skills. Review the source at https://github.com/wshobson/agents before installing.
Is screen-reader-testing free to use?
Yes. screen-reader-testing is free and open source under the MIT license, so you can read, run, and adapt it within that license's terms.
Which agents does screen-reader-testing work with?
screen-reader-testing lists Claude Code, Codex, Cursor, OpenCode, GitHub Copilot, and Antigravity — named in its SKILL.md, its plugin marketplace or its repository topics. Skills use the portable SKILL.md format, so other agents that read that format may load it too.
Where does screen-reader-testing come from?
screen-reader-testing ships inside wshobson/agents, a repository that contains 54 catalogued skills in total. The repository's 39,066 GitHub stars apply to that whole collection, not to this skill on its own.

Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.

↑ Growing Claude CodeCodexCursor+3
39k GitHub stars MIT Updated Aug 24, 2026 Free

Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.

↑ Growing Claude CodeCodexCursor+3
39k GitHub stars MIT Updated Aug 24, 2026 Free

Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.

Claude CodeCodexCursor+3
38k GitHub stars MIT Updated Jul 22, 2026 Free

Use when designing an A/B or split test: define the hypothesis, control and variants, estimate sample size, verify tracking, and predeclare metrics and stopping rules.

↑ GrowingActive Claude CodeCodexCursor+2
47k GitHub stars MIT Updated Sep 21, 2026 Free

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.

↑ GrowingActive Claude CodeCodexCursor+2
47k GitHub stars MIT Updated Sep 21, 2026 Free