20

We are concerned about accessibility on our web site and would like to see how it is perceived and decoded by a common screen reader?

TylerH
  • 20,799
  • 66
  • 75
  • 101
Matoeil
  • 6,851
  • 11
  • 54
  • 77

1 Answers1

33

No. At least not one that is any good nor represents how a screen reader actually reads a page or responds to ARIA.

The best answer is to test in real screen readers, ideally by getting real users as they know how to use these tools. Consider contacting your local blind association and see if they offer testing services.

Screen Readers

Each platform has a screen reader, most are built in. Windows has the most variety.

For Windows

  • Use Narrator (it is built in, though not very good right now it is getting much better). Use it with Edge.

  • Download the free NVDA screen reader (but please donate to support it). Use it with Firefox

  • Download JAWS and use it in 40 minute increments for free. Use it with IE11.

For macOS

For iOS

For Android

For Ubuntu

For ChromeOS

  • Use ChromeVox (but only use ChromeVox in this scenario, not as a plug-in for Chrome on Windows or macOS).

Resources

These are handy to get started with testing on your own. Keyboard shortcuts are necessary to use a screen reader well, beyond just hitting the Tab key over and over and over.

Community
  • 1
  • 1
aardrian
  • 8,581
  • 30
  • 40
  • 3
    I'm here because of https://twitter.com/scottohara/status/852866736848293888 – Jacob Evans Apr 14 '17 at 13:52
  • 1
    What's wrong with the [50+ online accessibility checker tools that the W3 lists](https://www.w3.org/WAI/ER/tools/?q=online-tool)? – RubberDuck Apr 14 '17 at 21:24
  • 1
    @RubberDuck those aren't screen reader emulators. An accessibility checker can only give a comparison against a spec, and even then it cannot test everything. It can also not account for the different features and quirks of screen readers. This [2012 piece outlines what can and cannot be tested](http://www.karlgroves.com/2012/09/15/accessibility-testing-what-can-be-tested-and-how/) and the author has much more to say on the topic on his site. – aardrian Apr 15 '17 at 21:21
  • @aardrian you should really include some of that in your answer. – RubberDuck Apr 16 '17 at 00:45
  • @RubberDuck The question was about screen reader emulators. – aardrian Apr 16 '17 at 02:22
  • 4
    Echoing @aardrian, testing with real screen readers and real users is essential. I built https://assistivlabs.com to help with that — it's like a Browserstack for screen readers and other ATs — nothing is emulated. But please don't omit testing with real disabled users. – Weston Oct 15 '20 at 21:59
  • [Silktide](https://chrome.google.com/webstore/detail/silktide-website-accessib/okcpiimdfkpkjcbihbmhppldhiebhhaf) seems promising, but still looking for something that can be integrated into E2E-tests or similar. – LHSnow Oct 29 '20 at 09:11
  • Silktide emulates low-vision, not screen readers. Still handy for testing but not as a screen reader emulator. – aardrian Oct 29 '20 at 20:42
  • For e2e tests have listed out screen reader automation tools as of 2023 in https://stackoverflow.com/a/75276390 – C.. Feb 01 '23 at 18:54