Accessibility overlays and widgets — do they work?
Overlays promise one line of code and instant compliance. What they actually change, why disabled users and regulators push back, and what to do instead if you want a site people can use.
By Sergio Gualda Last reviewed:
What an overlay is
An accessibility overlay, often sold as an “accessibility widget”, is a script you add to your site with one line of code. It usually does two things:
- shows a toolbar (a floating icon) where visitors can enlarge text, change colors, stop animations or turn on a reading mode;
- runs automatic repairs in the browser, trying to guess missing alternative text, labels and roles after the page has loaded.
The pitch is attractive: no developer, no audit, instant compliance. The reality is more limited.
Why it does not make a site accessible
People who need accessibility already have their own tools. A blind person uses a screen reader; someone with low vision uses their operating system’s zoom and contrast settings. A toolbar on your site duplicates what they have, and often conflicts with it.
The barriers are in the code. A field with no label, a button that is only an icon, a modal that traps the keyboard, a checkout step a screen reader cannot announce: an overlay sees the same broken code you published and has to guess. Sometimes it guesses right. Often it does not, and sometimes it makes a working page worse.
Compliance is judged on the site, not the widget. WCAG criteria apply to the content people receive. Sites with overlays installed are still named in ADA lawsuits every year.
Regulators have noticed. In 2025 the US Federal Trade Commission ordered accessiBe to pay $1 million over claims that its automated tool could make any website WCAG compliant. Hundreds of accessibility professionals have signed the Overlay Fact Sheet, which explains the same problems in more detail.
What actually works
- Find the real problems. Run an automated test on your most important pages. Uxerfy’s free checker opens the page in a real browser and lists every WCAG 2.2 AA failure it finds, and where.
- Fix them at the source. Add the missing alt text in your CMS, give icon buttons a name, label every field, make focus visible, raise low contrast colors. Most fixes are a line of HTML or CSS.
- Check the journey with a keyboard. Complete a purchase or a signup with only the Tab key. Our testing guide shows how in an afternoon.
- Keep it fixed. Re-test after theme updates, new apps and redesigns.
The work is done once, it lives in your site, and it helps every visitor, including the ones using their own assistive technology.
When a plugin does help
Not every tool that installs with one click is an overlay. These are genuinely useful:
- checkers that report problems for you to fix (axe DevTools, WAVE, Lighthouse, Uxerfy);
- theme fixes that change your own code, such as adding a skip link, restoring focus outlines or labeling a search field;
- CMS fields and workflows that make it easy to write good alt text for every image.
The test is simple: does it fix your site, or does it sit on top of it?
If you already use an overlay
You do not have to remove it today, but do not rely on it. Test your site with the overlay turned off, because that is the code assistive technology users meet first, and fix what fails. Once the site works on its own, the widget is no longer doing anything useful.