screen-reader-testing
This skill teaches you how to evaluate web applications through the lens of assistive technology users. You'll gain practical experience with industry-standard screen readers, understand common accessibility barriers, and develop testing strategies that ensure your interfaces work for everyone.
screen-reader-testing teaches you to evaluate web applications through the lens of assistive technology users by working hands-on with industry-standard screen readers. You'll learn the testing workflows for NVDA on Windows, JAWS for comprehensive enterprise testing, and VoiceOver on macOS, gaining practical experience with each tool's unique features and keyboard commands. This skill covers how to navigate web content, identify what screen reader users actually hear, and validate that your interface announcements match user expectations.
AI-generated summary based on this skill's SKILL.md
Install
zernie/vigiles/screen-reader-testing · repository language: TypeScript
git clone https://github.com/zernie/vigiles
cp -r vigiles/test/dogfood/wshobson-accessibility@cf6059d/skills/screen-reader-testing ~/.claude/skills/screen-reader-testingFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How to test with screen readers like NVDA, JAWS, and VoiceOver?
screen-reader-testing teaches you to evaluate web applications through the lens of assistive technology users by working hands-on with industry-standard screen readers. You'll learn the testing workflows for NVDA on Windows, JAWS for comprehensive enterprise testing, and VoiceOver on macOS, gaining practical experience with each tool's unique features and keyboard commands. This skill covers how to navigate web content, identify what screen reader users actually hear, and validate that your interface announcements match user expectations.
What does screen-reader-testing cover for validating ARIA implementations?
screen-reader-testing provides strategies for validating ARIA implementations and assistive technology compatibility by teaching you to test how screen readers interpret your semantic markup. You'll learn to verify that ARIA roles, properties, and states are correctly announced, understand common accessibility barriers that emerge in testing, and develop testing approaches that ensure your ARIA code works as intended across different assistive technologies.
How can screen-reader-testing help debug and fix accessibility issues?
screen-reader-testing equips you with practical debugging techniques to identify and fix accessibility issues for screen reader users. By learning to operate NVDA, JAWS, and VoiceOver, you'll discover exactly where your interface fails assistive technology users, understand the root causes of common problems, and develop solutions that work in real-world testing scenarios. The skill emphasizes hands-on problem-solving rather than theory alone.
What accessibility testing screen readers does this skill cover?
screen-reader-testing focuses on the three most widely-used accessibility testing screen readers: NVDA (free, Windows-based), JAWS (enterprise standard), and VoiceOver (built into macOS and iOS). You'll also gain exposure to mobile screen reader testing with TalkBack on Android. The skill teaches you to work with each tool's unique interface, understand their strengths for different testing scenarios, and validate web accessibility across the assistive technology landscape.
Does screen-reader-testing address form accessibility and dynamic content?
Yes, screen-reader-testing covers both form accessibility with screen readers and dynamic content announcements. You'll learn to verify that form fields are properly labeled, error messages are announced correctly, and that dynamic content updates trigger appropriate screen reader notifications through live regions and ARIA techniques. The skill ensures you can test the full user journey—from form discovery through submission and response handling—from an assistive technology perspective.
Is screen-reader-testing open source and what license does it use?
screen-reader-testing is released under the MIT license, making it freely available for both personal and commercial use. This open-source approach ensures that accessibility testing knowledge and resources remain accessible to developers at all levels, supporting the broader goal of making web applications work for everyone, including assistive technology users.
SKILL.md
rendered from the published skill — quoted content, verbatim
Screen Reader Testing
Practical guide to testing web applications with screen readers for comprehensive accessibility validation.
When to Use This Skill
- Validating screen reader compatibility
- Testing ARIA implementations
- Debugging assistive technology issues
- Verifying form accessibility
- Testing dynamic content announcements
- Ensuring navigation accessibility
Core Concepts
1. Major Screen Readers
| Screen Reader | Platform | Browser | Usage |
|---|---|---|---|
| VoiceOver | macOS/iOS | Safari | ~15% |
| NVDA | Windows | Firefox/Chrome | ~31% |
| JAWS | Windows | Chrome/IE | ~40% |
| TalkBack | Android | Chrome | ~10% |
| Narrator | Windows | Edge | ~4% |
2. Testing Priority
``` Minimum Coverage: 1. NVDA + Firefox (Windows) 2. VoiceOver + Safari (macOS) 3. VoiceOver + Safari
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
test/dogfood/wshobson-accessibility@cf6059d/skills/screen-reader-testing/SKILL.md