4 ms·

Thanks for the info! We may well switch over if that's what users are more likely to be using.

• robin_reala 9y ago
  It’s very difficult to tell what people are actually using as assistive tech interfaces with browsers rather than connecting to the site directly, but you can run surveys. We did one last year on GOV.UK and found JAWS at 38.5%, ChromeVox at 1%: https://accessibility.blog.gov.uk/2016/11/01/results-of-the-2016-gov-uk-assistive-technology-survey/ https://accessibility.blog.gov.uk/2016/11/01/results-of-the-...
  • scaryclam 9y ago
    Again, thanks for the information. I'll definitely take that back to my team and see what we can improve on!
    • jscholes 9y ago
      To provide some practical reasoning behind this: ChromeVox and software like it, naturally, runs in the browser. A blind person is unlikely to have a visual impairment which means they can't use a browser but can use every other part of the system without speech feedback. Therefore, system-wide screen readers see much higher use - who wants to keep switching between screen readers all the time? On the plus side, though, keyboard predictability breeds accessibility, so any testing in this area is often better than none.