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.
screen-reader-testing
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.
Installation
Add screen-reader-testing to your agent with:
/plugin marketplace add wshobson/agentsAlways review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
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
When to use it
Reach for screen-reader-testing when you want testing help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Clear MIT license — safe to read and adapt
- Ships in wshobson/agents, an established project with 38,890 GitHub stars
- Actively maintained (recent commits)
Topics
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.
- 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 38,890 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Testing →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.
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.
Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this,"...