Rough Guide: browsers, operating systems and screen reader support – Updated 23/06/2017

Practical screen reader support by browser and OS (updated 23/06/2017)

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

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, Narrator. Talkback on Android. On Mac OS and iOS; VoiceOver. On Linux; Orca and on Chrome OS; ChromeVox.

Table legend

  • supported “supported” means that the browser is usable in practice with a screen reader on the operating system (OS).
    Note: in the case of Internet Explorer it lacks support for some important features, but due to its market share screen readers hack around its lack of support.
  • “partial support” lacks support for some important features.
  • not applicable “not applicable” means the browser does not run on the OS
  • not supported “not supported” means the browser does not have practical support for screen readers on the OS.
  • not known “not known” means that accessibility support information is not publicly available.
  • not knownlikely, not supported not known, but likely is unsupported.

Note: The table refers to the current (23/06/2017) versions of browsers and current versions of operating systems.

Practical screen reader support by browser and OS (23/06/2017)
ChromeFirefoxInternet Explorermicrosoft edgeOperaSafari
Windowssupportedsupportedsupported notepartial supportpartial supportnot supported
OSXsupportedpartial supportnot applicablenot applicablepartial supportsupported
Linuxnot supportedsupportednot applicablenot applicablenot knownnot applicable
IOSsupported, but limited support datanot applicablenot applicablenot applicablenot knownsupported
Androidpartial supportsupportednot applicablenot applicablenot knownpartial support
(Android browser
webkit based)
Chrome OSsupportednot knownnot applicablenot applicablenot applicablenot applicable


Categories: Development

About Steve Faulkner

Steve is the Technical Director at TPGi. He joined TPGi in 2006 and was previously a Senior Web Accessibility Consultant at vision australia. He is the creator and lead developer of the Web Accessibility Toolbar accessibility testing tool. Steve is a member of several groups, including the W3C Web Platforms Working Group and the W3C ARIA Working Group.


JOnathan Cohn says:

The column and header rows appeared to not be red correctly OS X 10.9.5 with Safari 7.1.9537.

Steve Faulkner says:

Hi Jonathan,

The table is a standard HTML data table, headers are marked up using th elements with scope attributes.

Olly Hodgson says:

When your table says “Safari on Android”, does it mean the built-in Android browser (based on Webkit)?

Steve Faulkner says:

@Olly, yes have updated, thanks!