Practical screen reader support by browser and OS (10/10/2012)
When testing aspects of support for new HTML5, WAI-ARIA features and HTML features in general, I often test browsers that do not have practical support for screen readers on a particular operating system. I find they have support for feature X, but lack support for feature Y that is required to enable practical support to web content for screen reader users. While it is useful to test and find successful implementations of discrete features, it needs to be viewed in the broader context of which browsers can be considered usable with popular OS level screen readers.
I found it difficult to get a complete understanding from the resources available on the web, but have put together a high level support table based on information I could glean. If you have any further information or find any inaccuracies please comment.
Practical support for screen readers means that a browser can be successfully used to browse and interact with commonly encountered web content, using current versions of OS level screen readers such as, on Windows; JAWS, NVDA, Window Eyes. On Mac OSX and iOS; VoiceOver. On Linux; Orca and on Chrome OS; ChromeVox.
- “supported” means that the browser is usable with a screen reader on the operating system (OS).
- “partial support” lacks support for some important features. For example, Chrome on Windows supports browsing using JAWS, but does not fully support accessible name calculation.
- “not applicable” means the browser does not run on the OS
- “not supported” means the browser does not have practical support for screen readers on the OS.
- “not known” means that accessibility support information is not publicly available.
- browsers recently added to OS’s, Early data indicates usable accessibility support.
Note: The table refers to the current (10/10/2012) versions of browsers and current versions of operating systems.