An Accessibility Widget Is Not a Defense — and the Lawsuit Data Proves It

There's a comforting story that gets sold with accessibility overlays — the little floating button that adjusts contrast and font size. Add one line of code, the pitch goes, and your website is compliant and protected. It's fast, it's cheap, and it lets a busy team check a box.

The litigation data tells a different story.

The number that should give you pause

UsableNet, which tracks ADA digital-accessibility lawsuits across federal and state courts, found that more than 900 organizations with an accessibility widget or overlay installed were sued in 2023 — a 62% jump over the prior year. In 2024, the figure climbed past 1,000, accounting for more than a quarter of all digital-accessibility lawsuits filed that year. Across just those two years, that's well over 1,900 organizations that did exactly what the overlay vendors recommended and were sued anyway.

It gets sharper. In a growing share of those cases, plaintiffs cited the overlay itself as a barrier — not as evidence of a good-faith effort, but as part of the problem.

The widget didn't protect them. In many cases, it painted a target.

Why the widget didn't help

An overlay is a script that loads when your page does and tries to patch accessibility problems in the browser, on the fly. The trouble is threefold.

It only reaches a fraction of the problem. Automated tools — which is what an overlay is — reliably detect only about a third of the issues in the WCAG standard. The rest require human judgment: keyboard navigation, focus order, meaningful reading sequence, whether alt text actually describes the image. An overlay can't see most of that, let alone fix it.

It doesn't touch your documents. For most public organizations, the largest accessibility liability isn't the website template — it's the library of PDFs, agendas, plans, and forms. Overlays don't remediate documents at all. That exposure sits there untouched while the widget reports success.

It can make things worse for the people it's meant to help. The National Federation of the Blind has formally opposed overlays, and the Overlay Fact Sheet — signed by hundreds of accessibility professionals — states plainly that these tools don't meet legal requirements and in many cases degrade the experience. A WebAIM survey of screen-reader users found that more than 70% felt overlays made sites harder to use, and many disable them on sight.

The regulators noticed too

In 2025, the Federal Trade Commission finalized a $1 million order against accessiBe, one of the most heavily marketed overlay vendors, for deceptively claiming its automated tool could make any website WCAG-compliant. The order bars the company from making that claim for the next twenty years.

The lesson generalizes well beyond one vendor: no automated tool, by itself, can deliver — or guarantee — accessibility compliance. When the marketing says otherwise, the regulator now disagrees in writing.

What courts actually credit

Here's the part that matters most if your concern is legal exposure. Courts have consistently declined to treat the mere presence of an overlay as evidence of a good-faith accessibility effort. You can't outsource the obligation to a script.

What does hold up is the opposite of a quick fix: a documented program. An honest assessment of where you stand. Real remediation in the underlying code and documents. A record of the issues you found, who owns them, and how they were resolved over time. That's what demonstrates good-faith effort — and it's also, not coincidentally, what actually serves people with disabilities.

Accessibility isn't a product you install. It's a practice you maintain.

For public agencies, the stakes are specific

State and local governments now operate under the Department of Justice's Title II rule, which sets WCAG 2.1 Level AA as the standard for public websites and content. Enforcement doesn't ask whether you bought a tool. It looks for the things a program produces: a current assessment, a remediation plan, a way for the public to report barriers, ongoing monitoring, and a documented record of effort.

An overlay produces none of that. And because so much of a government's content lives in documents — the very thing overlays ignore — the gap between "we installed a widget" and "we can show a defensible program" is widest exactly where public agencies are most exposed.

What actually protects you

The path that works isn't glamorous, but it's the one that survives scrutiny:

1. Measure honestly — find out where you actually stand, across your website and your documents, not just the homepage a checker can see.
2. Fix at the source — remediate the code and the documents, so the accessibility is real, not a runtime illusion.
3. Document the effort — keep the assessment, the plan, and the record of progress. That's the difference between "we tried" and a defensible position.

That's the program courts credit, regulators expect, and residents deserve. A widget is none of it.

See where you actually stand

OctoComply runs a complimentary scan of your website and your document library and gives you your OctoScore — a clear, evidenced baseline of where you are today, including the parts an overlay never looks at. No widget, no obligation.

This article is for general information and is not legal advice. For guidance on your organization's specific obligations, consult qualified counsel.

Sources: UsableNet 2023 and 2024 Digital Accessibility Lawsuit Reports; U.S. Federal Trade Commission order regarding accessiBe (2025); National Federation of the Blind and the Overlay Fact Sheet; WebAIM screen-reader user survey.