Overlays and widgets
Do accessibility overlays work?
Updated 23 October 2026 · 3 min read
Accessibility overlays are scripts that add a toolbar or an automatic repair layer on top of a website, often with the promise that one line of code makes the site accessible. This guide explains what they can and cannot do, and what to do instead.
What an overlay is
An overlay is a third-party script added to every page. It usually shows an accessibility icon that opens a menu with options such as larger text, higher contrast or a dyslexia font, and it may also try to repair the page automatically while it loads, for example by guessing alt text with image recognition or adding labels.
What overlays cannot fix
The problems that stop disabled people from using a site are in its code and content. A script running on top cannot reliably repair them:
- It cannot know what an image means in context, so generated alt text is often wrong or useless.
- It cannot reliably turn a clickable box into a real, keyboard-operable button, or fix a custom menu, slider or date picker.
- It cannot fix keyboard traps, focus order, confusing error messages or missing captions.
- It cannot fix content you add after it was set up, PDFs, or pages where the script fails to load.
Most of the toolbar features, such as text size and contrast, already exist in browsers and operating systems, where disabled people have them set up the way they need.
Why many disabled users object to overlays
Screen reader users and accessibility professionals have reported that overlays can interfere with assistive technology, change how a page is announced, or add barriers of their own. In 2021 more than 700 accessibility professionals and disabled people signed the Overlay Fact Sheet, which asks site owners not to rely on overlays and vendors to stop claiming they make sites accessible.
Overlays and legal risk
Websites using overlays are still the subject of accessibility lawsuits in the United States, and complaints about overlays appear in some of them. In 2025 the US Federal Trade Commission finalised an order requiring the overlay provider accessiBe to pay 1 million dollars over claims that its tool could make any website meet WCAG, and over reviews presented as independent.
Laws such as the European Accessibility Act look at whether the service itself is accessible. A script on top does not change that.
What works instead
- Find the problems: run an automated scan of your main templates and add the manual keyboard, zoom and screen reader checks.
- Fix them at the source: in the theme, components and content, starting with anything that blocks a task such as checkout or sign-up.
- Test with real users where you can, including people who use assistive technology.
- Publish an accessibility statement with a way to report barriers, and act on reports.
- Keep checking: scan on a schedule so new content and updates do not bring the problems back.
AccessibilityBrief works this way: it never adds a script to your site. It finds problems and gives you the exact fix for each one, with code, platform steps and a prompt for AI coding tools, so the fix lives in your website itself.
Questions and answers
Do accessibility overlays make a website meet WCAG?
No. Overlays do not change the site's underlying code and cannot fix many WCAG failures, such as keyboard access to custom controls, meaningful alt text, captions and error handling.
Are accessibility widgets bad?
A widget that only repeats browser features is usually harmless but unnecessary. Overlays that change the page automatically can interfere with screen readers and other assistive technology, and they can give a false sense of being done.
Can I be sued if I use an overlay?
Yes. Websites with overlays have been sued in the United States. Using an overlay is not a defence if the site still has barriers.
What should I use instead of an overlay?
A scanner to find problems, the fixes made in your site's code and content, manual testing, an accessibility statement, and regular re-checks.
This guide is general information, not legal advice. Automated tests cover only part of WCAG; combine them with the manual checks described here.