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.

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 3. Screen Reader Modes Mode Purpose When Used Browse/Virtual Read content Default reading Focus/Forms Interact with controls Filling forms Application Custom widgets ARIA applications Before testing on macOS, read [VoiceOver setup, commands, and checklists](references/voiceover.md). For the required iOS Safari coverage, read [VoiceOver touch setup and gestures](references/voiceover ios.md). Before testing with NVDA, read [NVDA setup, modes, commands, and test scripts](references/nvda.md). Before testing with JAWS or TalkBack, read [platform setup and commands](references/jaws talkback.md). Common Test Scenarios 1. Modal Dialog 2. Live Regions 3. Tab Interface Debugging Tips Best Practices Do's Test with actual screen readers Not just simulators Use semantic HTML first ARIA is supplemental Test in browse and focus modes Different experiences Verify focus management Especially for SPAs Test keyboard only first Foundation for SR testing Don'ts Don't assume one SR is enough Test multiple Don't ignore mobile Growing user base Don't test only happy path Test error states Don't skip dynamic content Most common issues Don't rely on visual testing Different experience

screen-reader-testing