Accessibility Watch › Overlays, Honestly

Do Accessibility Overlays Protect You From Lawsuits? The 2025 Data Says No.

By Accessibility Watch · June 5, 2026

If you’ve added an accessibility overlay — one of those floating “accessibility” buttons that promises instant compliance — you may believe your site is now protected from an ADA lawsuit. The 2025 litigation data says otherwise.

Do accessibility overlays protect you from ADA lawsuits?

No. In 2025, 983 US businesses were sued over web accessibility while already running an overlay or widget on their site — about one in four of all such lawsuits that year. An overlay on the page did not stop the demand letter from arriving.

The reason is mechanical: overlays sit on top of your site and try to patch issues in the browser after the page loads. They don’t change the underlying HTML a screen reader actually reads, and they can’t fix most of the things that matter — meaningful alt text, correct headings, keyboard operability, focus order, form labels. A plaintiff’s tester (or the automated scanner many demand-letter operations run) evaluates the real page, finds the real failures, and the overlay is irrelevant to that finding.

How many businesses with accessibility widgets were sued in 2025?

983, according to EcomBack’s 2025 annual lawsuit report — 24.9% of the 3,948 ADA website-accessibility lawsuits filed that year. One overlay vendor’s customers accounted for 424 of those cases.

And the overall trend is up: 2025’s 3,948 filings were roughly 24% higher than 2024. This is not a shrinking problem you can paper over.

Was accessiBe fined by the FTC?

Yes. In 2025 the US Federal Trade Commission ordered the overlay vendor accessiBe to pay $1,000,000 over marketing that misled customers about how compliant its widget actually made their sites. When the government’s consumer-protection agency penalizes a vendor for overstating what its product does, that tells you something about relying on the product as legal cover.

What actually reduces web accessibility lawsuit risk?

The goal most small site owners actually have is concrete: get your site compliant enough that the automated scanners used by demand-letter operations no longer flag it as an easy target. That means fixing the real issues in the real page, against the standard that matters for US litigation — WCAG 2.1 Level AA.

That’s a finite, fixable list. The practical steps:

1. Find the real issues. Run a genuine audit against WCAG 2.1 Level AA — not a one-number “accessibility score,” but the actual failing criteria, in context.
2. Fix them at the source. Each finding has a concrete remediation. Alt text, headings, labels, contrast, focus, keyboard operability — these are edits to your code or your CMS, not a widget toggle.
3. Keep a record. Re-checking on a schedule, and keeping a dated history of your audits, demonstrates good-faith, ongoing effort — which matters if a claim ever does arrive.

You don’t need an overlay for any of that. You need to know what’s broken and how to fix it.

Accessibility Watch publishes a free browser extension that does exactly the first two steps: it finds your WCAG 2.1 Level AA issues and gives you the fix recipe for each one, at no cost. Check your site’s exposure free.