Why accessibility overlays fail — and what to do instead

The pitch is irresistible: paste one line of JavaScript into your website, and an “AI-powered” widget makes it accessible and protects you from lawsuits. Tens of thousands of businesses bought that pitch. Then the FTC fined the biggest vendor a million dollars, the lawsuits kept coming, and the accessibility community published an open letter begging site owners to stop.

This guide explains what happened, why overlays can't do what they promise, and what a defensible approach actually looks like.

What an overlay is

An accessibility overlay (also sold as a “widget” or “one-line solution”) is a third-party script that loads on top of your website. It adds a floating accessibility button and attempts to repair problems live in each visitor's browser — guessing image descriptions, re-labeling buttons, adjusting colors — every single time a page loads.

The crucial detail: your website's actual code never changes. The broken HTML is still there, under a coat of JavaScript paint.

The $1 million FTC settlement

In January 2025, the US Federal Trade Commission announced a $1,000,000 settlement with accessiBe, the largest overlay vendor, over claims that its widget could make any website compliant with WCAG accessibility standards. The FTC's complaint said those claims were false — and that the company had also presented paid reviews as independent opinions.

A regulator didn't fine a vendor for having bugs. It fined the core promise of the product category: that a script can make your site compliant.

If a tool's marketing tells you it makes you “instantly compliant,” you're not reading a feature list. You're reading the exact claim the FTC just made a public example of.

The lawsuits kept coming — often because of the widget

According to UsableNet's long-running lawsuit tracking, hundreds of businesses sued over web accessibility every year were already running an overlay when the complaint was filed — more than 900 in a single year at the peak. Some complaints now cite the overlay itself as a barrier.

Think about the mechanics: plaintiffs' firms test sites with the same screen readers real users rely on. An overlay doesn't stop that test — the broken markup is still what assistive technology encounters. Worse, the floating accessibility button advertises that the owner knew about accessibility and chose a shortcut.

Why overlays can't work — technically

1. The source stays broken

WCAG conformance is evaluated against your pages' actual content and code. A repair applied after page load, only for visitors who have JavaScript enabled and only while the vendor's servers are up, isn't a fix — it's a runtime patch that vanishes under audit conditions.

2. Guessed alt text is often wrong

Overlays generate image descriptions with no knowledge of your business or the page's intent. A photo of your founding team becomes “group of people standing.” A chart becomes “image.” Wrong descriptions can be worse than none — they actively mislead the people who depend on them.

3. They fight the tools they claim to help

Many screen reader users have their setup tuned exactly how they need it. Overlays that intercept keyboard behavior and re-announce content routinely make the experience worse — which is why so many users install browser extensions specifically to block overlays.

4. Every page view depends on a third party

The overlay script loads from the vendor's servers on every visit, adding weight to every page and a dependency you don't control. If it's slow, your site is slow. If it's down, your “accessibility” is down.

5. The experts signed a letter about it

The Overlay Fact Sheet — an open statement signed by hundreds of accessibility practitioners, including people who build and test with assistive technology daily — asks site owners to stop using overlays as a compliance strategy. When the people you're trying to serve tell you the tool doesn't serve them, that's the whole answer.

The stakes changed in 2025

The European Accessibility Act became enforceable in June 2025, extending accessibility obligations to many businesses that sell to EU customers — wherever the business is based — with the first enforcement actions following within months. In the US, federal and state courts continue to see thousands of ADA website cases a year. “We'll deal with it later” now has a price tag on two continents.

What to do instead: find, fix, prove

There's no honest shortcut, but there is a practical path that doesn't require a $10,000 audit:

Find. Test your real pages with the same rules engine auditors use, and rank what you find by actual legal risk — missing alt text, unlabeled buttons, and unreadable text account for most complaints.

Fix at the source. Change the actual HTML: real alt text in your media library, real labels on your buttons, real contrast in your stylesheet. Then re-test the live page to confirm each fix worked — and didn't break something else.

Prove it. Publish an accessibility statement backed by your real results, work through the checks that need human judgment, and keep a dated record. If a demand letter ever arrives, demonstrated ongoing effort is your strongest position — and it's the one thing an overlay can never give you, because an overlay is evidence you didn't fix the site.

Side by side

Aspect	Overlay widget	Source-level remediation (EqualSites)
Where the fix lives	A script painted over each visit	Your site's actual HTML and media library
If you remove it	Everything reverts instantly	Content fixes remain permanently
Verification	None — you trust the widget	Every fix re-tested on the live page
Visitor impact	Extra JavaScript on every page view	Zero added JavaScript for visitors
The compliance claim	“Instant compliance” — fined $1M by the FTC	No false promises: documented, ongoing effort
Typical cost	$490–$1,490 per year	From free; Pro at $199 per year