4 ms·

I think the move towards accessibility is great. I didn't know about pa11y so will probably bring it (or something similar) into our own build cycle to help kee

I think the move towards accessibility is great. I didn't know about pa11y so will probably bring it (or something similar) into our own build cycle to help keep track of WCAG issues. We also find it's useful to test out the core functionality using the keyboard, but extend that to using a text only browser and Chromevox so we can get a feel for what user stories would get broken if JS breaks, the user is trying to use the tools in older/incompatible browsers or the user has visual impairment. So far, it's been quite enlightening and we've not run into anything within the core functionality that couldn't be fixed with better UX and competently written HTML.

robin_reala 9y ago
For what it’s worth, ChromeVox doesn’t see much use from users of assistive tech. If you don’t want to pay for JAWS you’re better off testing with NVDA on Windows or VoiceOver on Mac / iOS.
- scaryclam 9y ago
  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.

robin_reala 9y ago

For what it’s worth, ChromeVox doesn’t see much use from users of assistive tech. If you don’t want to pay for JAWS you’re better off testing with NVDA on Windows or VoiceOver on Mac / iOS.

scaryclam 9y ago
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.