Read time: 45 seconds
Did your accessibility testing provide accurate results?
- Including automated testing throughout development helps catch errors as you build.
- When accessibility is part of the project from the start, the benefits increase.
- The Digital Transformation Agency report trying to retrofit accessibility at the end of a project can cost up to 30 times the cost of incorporating accessibility progressively.
Steps to take
- Always combine automated testing with ongoing manual testing.
- Read our guide on accessibility testing.
- Integrate tools like axe-core, Lighthouse Audits, or AccessLint.js into your development.
- Use a tool like AccessLint to find accessibility issues in your GitHub pull requests.
- Understand the problems faced by people with slight to extreme vision problems. Use a tool like No Coffee Vision Simulator to simulate:
- colour blindness
- low vision
- visual snow, glare and ghosting
- obstructed visual field
- low contrast sensitivity
- Video tutorials: Auditing an existing site with lighthouse (YouTube)
- Video tutorial: How I do an accessibility check, tools and extensions (YouTube)
- What we found when we tested tools on the world’s least-accessible webpage (GOV.UK)
Last update: 27 December 2019, minor edits.