Buyer's guide
How to choose the right tool
What to look for
- Checks mapped to WCAG.
- Reports should tell you which WCAG success criterion each issue relates to, so you can prioritise and explain fixes.
- Tools for each stage.
- Catching contrast in Figma is cheaper than fixing it after launch. Combine a design tool, a page checker and a scheduled scan.
- Clear help text.
- Pick tools that explain why something fails and how to fix it, so writers and designers can act without a developer.
- Manual testing support.
- Automated scans miss many problems, such as confusing focus order or poor alt text. Use a screen reader and a guided assessment for key pages.
- Reporting you can share.
- For monitoring, look for trend reports that show whether errors are going down month to month.
Common mistakes
- Chasing a perfect score.
- A 100 in Lighthouse does not mean a page is accessible. Use the score as a floor and test key journeys by hand.
- Relying on an overlay widget.
- Many accessibility experts and disabled users say overlays do not fix the source code and can conflict with screen readers. Fix the site itself.
- Testing only the home page.
- Forms, checkout, pop-ups and PDFs are where people get stuck. Include them in every audit.
- Leaving it to developers.
- Alt text, link text, headings and colour choices are content decisions. Train the people who publish.