Do accessibility overlays make you compliant? The honest answer

If you have searched for a quick way to make your website accessible, you have met the overlay pitch: add one line of JavaScript and a widget appears that promises to make your site WCAG-, ADA- and EAA-compliant automatically. It sounds perfect. It is also, unfortunately, not true. Here is the honest answer, and what to do instead.

What an overlay actually is

An accessibility overlay (sold by vendors such as accessiBe, AudioEye, UserWay and EqualWeb) is a script that loads on top of your existing site. It typically adds a floating button that opens a menu of user controls - bigger text, higher contrast, a reading guide - and runs automated detection that tries to patch some issues on the fly, such as guessing missing image descriptions or adding ARIA attributes.

The user-facing controls are not the problem. The problem is the claim that bolting this on makes a site conformant.

Why an overlay can't make you compliant

Automated tooling only finds a fraction of the problem. Across the industry, automated checks reliably detect somewhere around 30-40% of WCAG issues. The rest - whether the keyboard order makes sense, whether a screen reader announces a custom control correctly, whether alt text is meaningful rather than merely present, whether an error message is actually helpful - require a human to judge. An overlay automates the part that was already automatable and leaves the harder majority untouched.

The accessibility community has said so, loudly. The Overlay Fact Sheet, signed by more than a thousand accessibility professionals and practitioners, names the major overlay products and states plainly that overlays do not achieve compliance and can actively interfere with assistive technologies.

Regulators agree. In 2025 the US Federal Trade Commission finalised a $1,000,000 order against accessiBe over deceptive claims that its AI tool could make any website WCAG-compliant. The US Department of Justice has separately made clear that installing an overlay does not, by itself, satisfy the ADA.

The lawsuits keep coming anyway. Sites running an overlay are still sued for inaccessibility - in some years a meaningful share of accessibility complaints have targeted sites that had an overlay installed. The widget is not a legal shield.

Why overlays can make things worse

Because an overlay manipulates the page after it loads, it can collide with the assistive technology a disabled user already runs. Screen-reader users have reported overlays hijacking focus, announcing the wrong things, or duplicating controls. Many experienced users now block known overlays outright. So the tool marketed as helping disabled people can be the thing they switch off first.

What actually works

There is no one-click route, but the real path is well-trodden and not as daunting as it sounds:

1. Scan, then test by hand. Run an automated checker to clear the obvious failures (low-contrast text, missing labels, missing alt text), then test with a keyboard and a screen reader. That combination catches far more than any widget.
2. Fix the source, not the surface. Real remediation changes your templates, components and content so the underlying HTML is correct - not a script that papers over it at runtime.
3. Work from a checklist. Our free WCAG 2.2 AA checklist breaks the standard into plain-English items so you can see exactly where you stand and what to fix.
4. Check colour as you design. Low-contrast text is the single most common failure on the web; our colour contrast checker catches it in seconds.
5. Get an independent audit when it matters. If you face an EAA, ADA or procurement deadline, a manual audit gives you evidence behind every claim - the thing an overlay can never provide.

The uncomfortable truth is also the reassuring one: accessibility is real engineering and content work, but it is work you (or an independent auditor) can actually do and stand behind. A widget that promises to skip it is selling the one thing it cannot deliver.

For a deeper look, see our guide on whether accessibility overlays work. This is guidance, not legal advice - confirm specifics with the official sources or a qualified adviser.