I find it helpful to keep my default test stacks handy, and I prefer to incorporate screenreaders in the “Browser compatibility” section of contracts and testing plans whenever possible to normalize the need for screen reader testing and to make sure it doesn’t fall through the cracks.
The primary source I consult for screen reader usage patterns is the WebAIM Screen Reader Survey, which they have been conducting since 2009. The latest survey was published in June 2021.
For browsers, I incorporate trends from my personal and professional projects and data from varios web sources (like https://gs.statcounter.com/ and https://netmarketshare.com/, which allows segmenting by Operating System) and come up with some useful defaults that can serve as the basis for negotiating any particular project.
I find the exercise of prioritizing and optimizing the stacks for efficiency and completeness to be valuable to me personally.
A few notes:
-
In general, I do not need to support uber-legacy platforms, such as Internet Explorer or Chrome versions frozen by corporate IT at some point in the past.
-
Chrome, Edge, and Firefox “current” are generally sufficient. All three of these browsers are in a “continually updating” state where version management becomes useless and the “current minus 1 version” or “current minus 2 versions” rule of thumb is pretty worthless.
-
For iOS and Mac OS, Safari versions are tied to OS versions
-
iOS usage seems to average ~80% on the latest major version, 15% on the previous, and a long tail from there.
-
There is more version fragmentation on Android with the previous 3-5 versions being in play.
Using this data as well as experience from my practice, I try to keep updated test stacks for inclusion in statements of work and testing plans.
My preferred approach is to integrate assistive technology into the browser/device compatibility/testing section rather than include it in a separate “accessibility” section. I do it this way because it normalizes assistive technology as part of the core of compatibility and testing.
Comprehensive:
Browser compatibility:
-
Mac:
- Current version of Chrome and Firefox.
- Safari on current and previous OS major release version, latest point release.
- VoiceOver screen reader
-
Windows:
- Current version of Chrome, Edge, and Firefox on Windows 10
- NVDA, JAWS, Windows Narrator screen readers
-
iOS:
- Safari on current and previous iOS major release version, latest point release.
- VoiceOver screen reader
-
Android
- Chrome on current and previous major release version
- TalkBack screen reader
Practical:
Browser compatibility:
-
Mac:
- Current version of Chrome.
- Safari on current and previous OS major release version, latest point release.
- VoiceOver screen reader
-
Windows:
- Current version of Chrome, Edge, and Firefox on Windows 10
- NVDA or JAWS screen readers
-
iOS:
- Safari on current iOS major release version, latest point release.
- VoiceOver screen reader
-
Android
- Chrome on current and previous major release version
- TalkBack screen reader
Minimal:
Browser compatibility:
-
Mac:
- Safari on current OS major release version, latest point release.
- VoiceOver screen reader
-
Windows:
- Current version of Chrome on Windows 10
- JAWS screenreader
-
iOS:
- Safari on current iOS major release version, latest point release.
- VoiceOver screen reader
-
Android
- Chrome on current major release version
- TalkBack screen reader
Barebones:
Browser compatibility:
-
Windows:
- Current version of Chrome on Windows 10
- JAWS screenreader
-
iOS:
- Safari on current iOS major release version, latest point release.
- VoiceOver screen reader
-
Android
- Chrome on current major release version
- TalkBack screen reader
If you have any feedback or had different takeaways, I would love to discuss it, just email me.