Why accessibility overlay widgets don't stop ADA lawsuits

Published September 8, 2026 · about a 7-minute read

Someone sold you a line of JavaScript that promised to make your site "ADA compliant" overnight. You pasted it in, saw a little accessibility toolbar appear in the corner, and crossed the problem off your list. Then the demand letter showed up anyway. If that's you, you're not alone — and the widget you're paying for may actually be making your case worse.

I want to be specific about this, because "overlays are bad" gets said a lot without the receipts. Here are the receipts.

What an overlay actually is

An accessibility overlay (also called a widget or plugin) is a third-party script — usually one line of JavaScript — that loads a toolbar on your site and runs some automated adjustments on top of your existing page. Bigger text, higher contrast, a "screen-reader mode," maybe an attempt to guess at some missing labels. The pitch is seductive: no dev work, no audit, instant compliance, often for a modest monthly fee.

The problem is right there in the description. It sits on top of your page. It doesn't change your underlying HTML. And the things that actually get sites sued — a checkout you can't complete with a keyboard, form fields with no labels, images with no alt text, a menu a screen reader can't operate — live in the underlying HTML.

The data: overlays are getting sued, not saved

This is the part that should end the debate. According to UsableNet's 2025 midyear report, about 22.6% of web accessibility lawsuits in the first half of 2025 — roughly 456 cases — were filed against sites that had an accessibility overlay installed. In full-year 2024, more than a thousand suits explicitly named an overlay or widget as a barrier to access.

Read that again. Nearly a quarter of these cases now involve a site that had already "solved" accessibility with a widget. The tool people buy specifically to avoid lawsuits is present in a large and growing share of the lawsuits. Total filings keep climbing too — UsableNet counted 4,928 U.S. web accessibility lawsuits in 2025, with federal filings up 27% year over year. Overlays are not bending that curve.

An overlay doesn't make you invisible to a plaintiff's tester. It makes you easier to spot — the widget announces that you know accessibility matters, and its failures are simple to document.

Why they fail, concretely

Turn on a real screen reader and try to use a page that's running an overlay. A few things tend to happen:

• The structural stuff is still broken. An overlay can bump contrast, but it can't give your icon-only buttons real names, wire up your form labels, or write meaningful alt text for images it doesn't understand. Those are the exact failures cited in demand letters.
• It can fight the assistive tech. Screen readers and browsers already have accessibility features built in. An overlay that tries to take over focus, re-announce content, or inject its own controls can conflict with the tools a disabled user already relies on — making the experience worse, not better.
• Users turn it off. Many people who use assistive technology have learned to dismiss these widgets on sight, because they get in the way. A fix nobody keeps enabled isn't a fix.

Regulators are on the record now

This isn't just the accessibility community grumbling. In April 2025 the U.S. Federal Trade Commission finalized a $1 million order against overlay vendor accessiBe. The FTC's complaint said the company misrepresented that its automated, AI-powered tool could make any website WCAG-compliant, when in practice the plug-in failed to make basic components — navigation menus, form fields, image descriptions — accessible. The order bars the company from making those blanket compliance claims without evidence to back them. When a federal regulator fines a vendor a million dollars for the exact promise the category is built on, that tells you how much weight the promise carries.

There's also the Overlay Fact Sheet, a public statement signed by hundreds of accessibility professionals and developers who won't recommend overlays as a compliance solution. It's worth reading if a vendor is pressuring you.

What to do instead

Fix the site, not the surface. It's less glamorous than a magic script, but it's the only thing that holds up. In order of leverage:

• Run an automated scan to clear the machine-detectable failures — missing alt text, unlabeled fields, contrast problems, missing page language. That's the fast third of the work and it's exactly what serial-plaintiff tools scan for.
• Do a keyboard-only pass through your key flows — navigation, search, checkout. If you can't finish without a mouse, that's a lawsuit waiting to be written.
• Fix the code where the scan and the keyboard pass flag problems: real <label>s, button names, heading structure, focus styles. The WCAG 2.2 AA checklist walks through what "fixed" looks like, and the ADA compliance guide covers the legal picture.

Our free accessibility checker runs that automated layer against your live page and grades it — so you can see the real failures a widget was hiding, and fix the ones that actually get cited.