Testing with assistive technologies
Steps for product teams to test that web content works with assistive technologies (AT).
Disabled people are the experts in using AT. However, depending on the disability and the site or application, non-AT users might sometimes be in a better position to spot issues. To get some insights on this subject from a blind accessibility auditor, see Accessibility testing as a screen reader user — TPGi.
For this reason, even though testing content with disabled people using their preferred operating systems, browsers and AT is critical to understanding the user experience, it’s important for digital practitioners to also test the content themselves using AT.
For an overview of which AT to test with and what to do if you find an issue, see Testing with assistive technologies — GOV.UK.
Testing with screen readers
- Testing with Screen Readers: Questions and Answers — WebAIM
- Screen readers — How to test — Testing with Assistive Technologies — GOV.UK
- Basic screen reader commands for accessibility testing — TPGi
- How to Test for JAWS Compatibility — TPGi
- Using JAWS to Evaluate Web Accessibility — WebAIM
- Using NVDA to Evaluate Web Accessibility — WebAIM
- Using VoiceOver to Evaluate Web Accessibility — WebAIM
- Using TalkBack to Evaluate Web Accessibility — WebAIM
- VoiceOver on iPhone testing steps — BBC News Accessibility
Testing with screen magnifiers
- Screen magnifiers — How to test — Testing with Assistive Technologies — GOV.UK
- Zoom on OS X — Screen magnifier testing — DWP Accessibility Manual — UK Government
- ZoomText for Windows testing steps — BBC News Accessibility
Testing with speech recognition software
- Speech recognition — How to test — Testing with Assistive Technologies — GOV.UK
- Testing with speech recognition — TPGi
- Dragon for Windows testing steps — BBC News Accessibility
- Voice Access on Android testing steps — BBC News Accessibility
- Voice Control on iPhone testing steps — BBC News Accessibility
Testing with keyboards
Interactive controls that are keyboard accessible can be activated more easily by users of screen readers, braille displays and speech recognition software. Of course, there’s more to making content accessible, but keyboard accessibility is a critical component for many AT users.
To test that all interactive content is focusable and operable via keyboard, see Testing keyboard accessibility — Knowledge Area: Keyboard accessibility.