Why accessibility overlays don't fix accessibility
Overlay widgets promise one-line compliance. Why they rarely help disabled users, and what agencies can offer instead.
Rongu team · Published
Accessibility overlays are scripts that add a toolbar or try to repair a page in the visitor's browser. They are easy to install and easy to sell. They are also widely criticised by disabled users and accessibility practitioners.
The problems with overlays
- They don't change the source. The page's code stays inaccessible; the overlay tries to patch it at runtime, and often misses.
- They can get in the way. Screen reader users already have their own tools. An overlay that changes focus, adds announcements or alters markup can make things worse.
- They create false confidence. A badge that says "accessible" doesn't make it so, and doesn't help if a user or regulator finds barriers.
What to offer instead
Fix problems where they live: in templates, components and content. That sounds slower, but most problems come from a handful of shared templates. Fixing a header once fixes it on every page.
A sustainable service looks like this:
- Find problems with regular scans and manual checks.
- Prioritise by impact and by how many pages a problem affects.
- Fix in code, with guidance your developers can follow.
- Verify with the next scan.
- Report progress to the client.
AccessWatch is built around that loop, and it never adds a script to the sites it checks. See how agencies use it.