← Back to home
Web AccessibilityScreen ReaderWCAGTestingCross Browser

Which screen reader and browser combinations should you prioritise in testing?

3 min read

Updated

Testing with a screen reader requires a decision that's easy to overlook: which screen reader, and which browser.

Each combination relies on a different accessibility API implementation, produces different output and exposes different gaps in the same code. A component that works in one pairing can fail silently in another.

The WebAIM Screen Reader User Survey #10, run between December 2023 and January 2024 with 1,529 valid responses, is one of the most comprehensive sources of data on how screen reader users interact with the web.

Dark background with five rows showing the most common screen reader and browser combinations from the WebAIM Survey #10. From top: JAWS with Chrome at 24.7%, NVDA with Chrome at 21.3%, JAWS with Edge at 11.4%, NVDA with Firefox at 10.0%, and VoiceOver with Safari at 7.0%. A closing note reads: global data is a starting point — your analytics are the real answer.

The five combinations that cover most users

According to the survey's screen reader and browser combination data, these pairings represent the largest share of users:

  1. JAWS + Chrome: 24.7% (373 respondents). The most common combination overall, and especially dominant in North America, where JAWS primary usage reaches 55.5%.

  2. NVDA + Chrome: 21.3% (323 respondents). NVDA is free and open source, which drives its lead in Europe, Asia and Africa. In Europe, NVDA primary usage reaches 37.2%, ahead of JAWS at 29.7%.

  3. JAWS + Edge: 11.4% (173 respondents). Microsoft Edge has grown as a testing target, especially in enterprise environments where JAWS is the default assistive technology.

  4. NVDA + Firefox: 10.0% (152 respondents). Firefox has historically had strong accessibility API support, and this combination remains relevant for users who prefer open-source tools across the stack.

  5. VoiceOver + Safari: 7.0% (107 respondents). The only native macOS and iOS combination. VoiceOver comes free on Apple devices, so it covers a distinct group of users, particularly on mobile.

Together, these five combinations make up the majority of desktop screen reader usage reported in the survey.

Global data is a starting point

The WebAIM survey gives you a useful baseline, with a caveat the researchers themselves acknowledge: the sample isn't controlled and may not represent all screen reader users.

The most accurate data about which combinations your users rely on comes from your own analytics.

Browser usage, operating system distribution and, where available, assistive technology signals from tools like Google Analytics or Plausible can tell you what your audience runs. A public government service in Germany has a very different user profile from a commercial SaaS product in North America, and one global dataset can't reflect both accurately.

That's why analytics belongs in accessibility decisions. Testing a combination that 25% of global survey respondents use is useful. Testing a combination that 60% of your actual users run is essential.

Cross-browser testing as an accessibility practice

Cross-browser testing is often treated as a visual consistency check. In accessibility it goes deeper.

When two screen readers in two browsers announce the same ARIA role differently, users in each environment get a different product. One may receive complete, useful information. The other may get partial or incorrect output, or silence.

It's not a bug in the usual sense. It comes from how accessibility APIs, browser implementations and screen reader interpretations interact, and the only way to know the result is to test the combination.

Start with the five pairings above, then let your analytics tell you where to focus.

Reference: WebAIM Screen Reader User Survey #10, December 2023 / January 2024

LinkedInX

Related posts