How to Test Your Website with a Screen Reader
Why Screen Reader Testing Matters
Automated accessibility testing tools can detect approximately 30-50% of WCAG issues. The remainder requires manual testing, and screen reader testing is one of the most important manual checks you can perform. Screen readers are used by people who are blind or have significant vision impairments to navigate and interact with websites using audio output and keyboard input.
Testing with a screen reader reveals issues that no automated tool can catch: whether your content makes sense when read aloud, whether interactive elements are properly announced, whether dynamic content updates are communicated, and whether users can complete key tasks using only a keyboard and audio feedback.
Choosing a Screen Reader
NVDA (Windows) — Recommended for Testing
NVDA (NonVisual Desktop Access) is a free, open-source screen reader for Windows. It is the most commonly used screen reader for testing because it is free, actively maintained, and widely used by actual screen reader users.
- Cost: Free (donation supported)
- Platform: Windows
- Best browser pairing: Firefox or Chrome
- Download: nvaccess.org
JAWS (Windows)
JAWS (Job Access With Speech) is the most feature-rich commercial screen reader. It has the largest market share among daily screen reader users, making it important for comprehensive testing.
- Cost: $90/year (home) or $1,000+ (professional)
- Platform: Windows
- Best browser pairing: Chrome or Edge
VoiceOver (Mac/iOS)
VoiceOver is Apple's built-in screen reader, available on all Mac computers, iPhones, and iPads at no additional cost. It is the primary screen reader for testing on Apple devices.
- Cost: Free (built into macOS and iOS)
- Platform: macOS, iOS, iPadOS
- Best browser pairing: Safari
- Activate on Mac: Cmd + F5
TalkBack (Android)
TalkBack is Android's built-in screen reader. Essential for testing mobile web experiences on Android devices.
- Cost: Free (built into Android)
- Platform: Android
- Best browser pairing: Chrome
Getting Started with NVDA
Here is a step-by-step guide to testing with NVDA, the most accessible option for beginners:
Essential NVDA Keyboard Shortcuts
The NVDA modifier key is typically the Insert key (or Caps Lock if configured):
- Start/Stop NVDA: Ctrl + Alt + N
- Stop speaking: Ctrl
- Read next line: Down Arrow
- Read previous line: Up Arrow
- Navigate to next heading: H
- Navigate to next link: K
- Navigate to next form field: F
- Navigate to next button: B
- Navigate to next landmark: D
- List all headings: NVDA + F7
- Read page title: NVDA + T
- Tab through interactive elements: Tab
- Activate a link or button: Enter
- Toggle browse/focus mode: NVDA + Space
What to Test
1. Page Title and Language
When you first load a page, the screen reader should announce the page title (from the title element). Check that it is descriptive and unique. The screen reader should also detect the correct page language.
2. Heading Structure
Press H repeatedly to navigate through all headings on the page. Check that:
- There is exactly one H1 that describes the page content
- Headings follow a logical hierarchy (H1, H2, H3 — no skipped levels)
- Headings are descriptive and help users understand the page structure
- All major sections have headings
3. Navigation
Test the main navigation menu:
- Can you navigate to the menu using keyboard?
- Are menu items announced with their role (link, button)?
- Do dropdown/submenu items work with keyboard?
- Is the current page indicated (e.g., "current page" announcement)?
- Is there a skip navigation link at the top of the page?
4. Images
Navigate through images using G (graphic shortcut in NVDA). For each image, check:
- Does it have alt text?
- Is the alt text meaningful and descriptive in context?
- Are decorative images hidden from screen readers?
5. Links
Navigate through links using K. Check that:
- Link text describes the destination or purpose
- Links are not just "click here" or "read more" without context
- Links that open new windows indicate this
6. Forms
Navigate to forms using F. For each form field, check:
- Is the field label announced correctly?
- Are required fields indicated?
- Are error messages announced when they appear?
- Can you complete and submit the form using only the keyboard?
- Are help text and instructions associated with their fields?
7. Dynamic Content
Test areas where content changes dynamically:
- Are loading states announced?
- Are error and success messages announced?
- Are content updates in live regions communicated?
- Do modals trap focus correctly and announce their title?
8. Tables
Navigate to tables using T. Check that:
- Data tables have proper header cells (th elements)
- Screen readers announce column and row headers when navigating cells
- Tables have captions or accessible labels
Common Issues You Will Find
Here are the most common issues discovered during screen reader testing:
- Missing or generic alt text: Images announced as "image" or "graphic" without description
- Unlabeled form fields: Fields announced only as "edit" without indicating what to enter
- Inaccessible dropdown menus: Submenus that cannot be opened or navigated via keyboard
- Missing live region announcements: Form submissions, errors, or content changes that happen silently
- Focus traps: Areas where keyboard focus gets stuck and cannot escape
- Incorrect heading levels: Headings that skip levels or do not reflect content hierarchy
- Ambiguous link text: Multiple "read more" links that sound identical out of context
Combining Automated and Manual Testing
The most effective testing strategy combines automated scanning with screen reader testing. Start with EAAPass to automatically identify the majority of WCAG issues across your entire site, fix those issues, then use screen reader testing to verify the fixes and catch the issues that only manual testing can reveal.
This approach ensures comprehensive coverage while being efficient with your time. Automated tools handle the high-volume, easily detectable issues, while screen reader testing focuses on the nuanced, context-dependent issues.
Run your automated audit with EAAPass first, then use this guide to complete your accessibility testing with screen reader checks.