6. Testing
Most accessibility testing needs to be performed manually.
Automated tests can help point out the most glaring or apparent issues, but accessibility is more than a checklist of technical issues: it’s a user experience consideration.
For consideration
To meet accessibility objectives—ensuring access and engagement with content—we have to do manual testing; we can’t rely on automated tests.
Test the experience for screen readers, keyboards, zoom, and other assistive technology users to ensure that the functions work and provide a delightful experience for users who visit your website.
Putting it into action
- Test with automated review tools
- Test with a screen reader
- Test by zooming the browser
- Test with a keyboard only
- Test with users who use different access methods to learn from their routine approach, especially for unfamiliar interaction modes
Suggested additional resources
Why automated accessibility checkers can’t make your website accessible
This article explores the limitations of automated checkers and why it’s essential to supplement automated checkers by working through the interface using all interaction methods, including:
- Mouse/touch
- Keyboard
- Screen reader
- Zooming
- Voice navigation
- Accommodating different screen sizes
- Ideally, with with users who use these different interaction methods on an everyday basis in order to gain new insights into improving user experience, access, and engagement
Suggested additional resources
Our Accessibility Testing documentation in Confluence includes more detail on available screen readers (including for Windows, Mac, iOS and Android), automated testers, and more.
Suggested approach
More detail on ensuring the representation of diverse employee groups when testing can be found in the Market and user research considerations section of this guide, with specific detail in the Recruiting and participants section.