Why Accessibility Overlays Keep Getting Sued — And What to Do Instead

You bought the overlay. You copied the script tag. You watched the little widget badge appear in the corner of your site and assumed you were done. Then the demand letter arrived anyway. This is not a rare story. Accessibility overlay widgets — products like accessiBe, UserWay, and AudioEye — are sold on the promise of instant, effortless compliance. The reality is documented in FTC enforcement actions, signed statements from hundreds of accessibility professionals, and a growing pile of ADA lawsuits against sites that were already running one.

What an Overlay Actually Is

An accessibility overlay is a JavaScript snippet that injects a floating toolbar onto your page. Depending on the product, it may offer controls for adjusting text size, contrast, or spacing, and it may attempt to automatically patch keyboard navigation or ARIA attributes using client-side JavaScript. Vendors often describe this as "AI-powered" remediation.

The core claim — that a single script can make an arbitrary website compliant with WCAG 2.1 AA or the ADA — is the problem. WCAG conformance is assessed against the underlying HTML, CSS, and scripting that the browser delivers to the user. An overlay runs after that code is already rendered. It can add a widget, but it cannot rewrite the document structure that screen readers parse, it cannot fix missing form labels in your CMS, and it cannot give meaningful alternative text to images it knows nothing about.

The FTC Fine: accessiBe, $1 Million, Deceptive Claims

In 2024 the Federal Trade Commission reached a settlement with accessiBe, one of the largest overlay vendors. The FTC found that accessiBe had made deceptive marketing claims — specifically that their product made websites "fully ADA compliant" and "fully accessible." The settlement required the company to pay $1 million in civil penalties and to stop making those claims.

This is not an advocacy group opinion. It is a formal regulatory finding by a federal agency with enforcement authority. The practical implication for any business that bought an overlay based on compliance marketing: the vendor's own claims have been ruled false by the government.

The Overlay Fact Sheet: 700+ Accessibility Professionals Agree

The Overlay Fact Sheet (overlayFactSheet.com) is a public statement, now signed by more than 700 accessibility practitioners, engineers, and researchers, that documents specific technical and ethical problems with overlay products. The signatories include professionals from universities, government agencies, assistive technology companies, and major corporations. The document is not a legal filing. It is a professional consensus statement from the people who actually test websites with screen readers for a living.

Their core finding: overlays do not and cannot make websites accessible. Several signatories note that overlays can actively worsen the experience for users of assistive technology by injecting conflicting ARIA attributes into a page that a screen reader is already interpreting.

Paid and Still Sued: The 2025 Lawsuit Pattern

Data compiled from ADA Title III web accessibility lawsuit filings shows that roughly a quarter of suits filed in 2025 targeted websites that already had an accessibility overlay installed at the time of the complaint. The overlay did not prevent the suit. In several cases the complaint specifically named the overlay as evidence that the defendant knew about their accessibility obligations and chose a quick fix over a real one.

Plaintiffs' firms that specialize in ADA web litigation have developed tooling to test sites before filing. They are aware of which sites run overlays. An overlay widget visible in a screenshot does not deter a demand letter; in some readings it may attract one, because it signals that the owner is aware of the issue.

Why Screen Reader Users Often Turn Overlays Off

Users who depend on screen readers — the population overlays claim to serve — frequently disable them. The most common complaints: overlays intercept keyboard shortcuts that the screen reader itself uses, overlays inject ARIA roles that conflict with the existing page structure, and the overlay toolbar itself is often not accessible without a mouse. There is documented evidence of blind users being locked out of content entirely when an overlay conflicted with their screen reader.

An accommodation tool that the intended beneficiaries are actively avoiding is not an accommodation. It is a liability with a badge.

What Honest Compliance Actually Looks Like

Real WCAG 2.1 AA conformance requires identifying failures and fixing them in the underlying code. The process that actually produces evidence of good-faith effort involves several layers:

• Automated scanning with multiple engines. No single automated tool catches everything. Running both axe-core and IBM Equal Access together covers substantially more of the WCAG success criteria than either tool alone. Automated tools can reliably flag missing alt attributes, contrast failures, missing form labels, and many structural issues.
• AI-assisted review. Automated tools cannot evaluate context. They can confirm that an image has an alt attribute; they cannot judge whether that alt text is meaningful. An AI review pass catches the next tier of failures — vague link text, redundant descriptions, logical reading-order problems — that require language understanding.
• Manual review with assistive technology. Some failures only surface during actual keyboard navigation or screen reader use. Tab order, focus management in modals, live region announcements: these require a human tester with a screen reader. This is the premium-tier differentiator that separates genuine compliance work from automated-only reports.
• Dated, archived documentation. If a demand letter arrives, your defense is a timestamped audit trail showing what you tested, what you found, and what you fixed. An overlay receipt is not that. A dated scan report from a recognized engine, paired with documented remediation, is.

The accessible EU Accessibility Statement, required under the European Accessibility Act for businesses operating in the EU, must describe what you tested, the method you used, and what known failures remain. An overlay cannot generate that statement, because it has no knowledge of what your actual failures are.

The Honest Position

No tool, including this one, will guarantee that you are lawsuit-proof. Accessibility is an ongoing practice, not a one-time certificate. What honest scanning gives you is a clear picture of your actual failures, a prioritized remediation list, and dated documentation that demonstrates systematic good-faith effort. That is what courts and regulators look at. That is what an overlay cannot provide.

The contrast is simple: overlays sell you a badge. Real scanning tells you what is broken and gives you the records to prove you fixed it.