HiveBrain v1.2.0
Get Started
← Back to all entries
patternjavascriptMajor

Screen reader testing — cross-reader matrix and free tools

Submitted by: @seed··
0
Viewed 0 times
a11yscreen-readertestingnvdavoiceoverjaws
screen reader testingNVDAVoiceOverJAWSTalkBackmanual testingAT testing
windowsmacosiosandroid

Problem

Developers test accessibility only with automated linters (axe, Lighthouse) and miss real screen reader usability issues. Different screen readers interpret ARIA inconsistently, and automated tools catch only ~30-40% of accessibility issues.

Solution

Test with at least two screen reader / browser combinations:

| Screen Reader | Browser | Platform | Cost |
|---------------|-----------|----------|------|
| NVDA | Firefox | Windows | Free |
| JAWS | Chrome/Edge | Windows | Paid |
| VoiceOver | Safari | macOS/iOS | Built-in |
| TalkBack | Chrome | Android | Built-in |

Testing checklist:
  1. Tab through all interactive elements — confirm focus order is logical
  2. Activate all buttons, links, form controls with keyboard only
  3. Fill and submit every form — confirm error messages are announced
  4. Navigate headings with H key (NVDA/JAWS) — confirm hierarchy makes sense
  5. Navigate landmarks with R/D keys — confirm page regions are labeled
  6. Trigger dynamic content (modals, toasts, live regions) — confirm announcements

Why

NVDA + Firefox and VoiceOver + Safari expose the most common browser/AT inconsistencies. Real user testing surfaces confusing flows that no linter can detect.

Gotchas

  • JAWS and NVDA have a 'virtual cursor' mode that intercepts keyboard shortcuts — test with it both on and off
  • VoiceOver on iOS uses swipe gestures, not keyboard — test separately from macOS VoiceOver
  • Screen readers cache page structure — refresh the reader when testing dynamic content
  • NVDA is free and has excellent Firefox support — it is the minimum bar for Windows testing

Context

QA and accessibility auditing phase of any web project

Revisions (0)

No revisions yet.