Why accessibility overlays don't make you compliant

An overlay widget can't fix the code underneath your pages, so it can't make a site meet WCAG. In 2025 the FTC fined accessiBe $1 million for claiming otherwise, and about a quarter of that year's website accessibility lawsuits named sites that already had a widget installed.

Written by the nextwebsite.co team, and last checked on November 7, 2026.

What an overlay is

An accessibility overlay is a script you add to your site, usually shown as a small person icon in a corner. It offers visitors controls such as bigger text or higher contrast, and the vendor's software tries to patch problems in the page as it loads. It's sold as a one-line fix for compliance.

Why it can't make a site compliant

WCAG is about how the page itself is built: whether a form field has a real label, whether a button can be reached with a keyboard, whether an image has an accurate description⁴. An overlay guesses at those after the fact. It can't know what an image means or what a link without text does, and the controls it adds are ones people who rely on assistive technology already have in their own browser or screen reader.

Even the best automated testing finds only about 57% of accessibility issues³. A script that runs in the visitor's browser is working with less information than those tools, not more.

The FTC's order against accessiBe

In April 2025 the Federal Trade Commission finalised an order requiring accessiBe, one of the largest overlay vendors, to pay $1 million. The FTC said the company had misrepresented that its tool could make any website comply with WCAG, and had presented paid reviews as independent¹. The order bars the company from claiming its product makes sites compliant unless it can back the claim with evidence.

Sites with widgets still get sued

About a quarter of the website accessibility lawsuits filed in 2025 were against sites that already had an overlay widget installed². For a plaintiff, a widget can even suggest the owner knew about accessibility and chose a shortcut.

What to do instead

Test the site with the widget switched off, and fix the problems in the pages themselves: labels, headings, contrast, image descriptions and keyboard access. Then test with a keyboard and a screen reader. Once the underlying pages pass, remove the widget; it adds weight to every page and does nothing a fixed site needs.

Checklist

Note what the widget claims to fix, then test the site with it switched off.
Fix labels, contrast, headings and image descriptions in the site itself.
Test with a keyboard and a screen reader, which automated checks can't replace.
Remove the widget once the underlying pages pass.

Check your own site

The free scan checks your pages for the accessibility problems a machine can find, and marks the checks that need a person. It takes under a minute.

Or run just this check: the accessibility checker.