You bought the widget. You pasted the script into your <head>. A little wheelchair icon appeared in the corner of your site, and the sales page promised it would make you ADA compliant. Then the demand letter arrived anyway — and it specifically mentioned your accessibility widget. If that sounds familiar, you are not an unlucky outlier. You are part of a documented, growing pattern.
The lawsuits keep coming — overlay or not
The headline numbers are not subtle. Law firm Seyfarth Shaw counted 2,452 website accessibility lawsuits filed in federal court in 2024, on top of 2,749 in 2023 (Seyfarth ADA Title III blog). State court filings and pre-suit demand letters — which never show up in any docket — push the real total far higher.
The part that should worry overlay buyers is what UsableNet found when it looked at which sites were getting sued. In its 2024 report, roughly 1,023 of that year’s complaints — about a quarter — involved companies that had an accessibility widget or overlay installed (UsableNet). The widget did not deter the plaintiff. In a lot of cases it did the opposite: the complaint cited the overlay as evidence that the business knew accessibility was an issue and reached for a shortcut instead of fixing it.
That trend did not cool off. Through the first half of 2025, plaintiffs filed 2,019 digital accessibility lawsuits, a pace that projects to roughly 4,975 for the full year. Suits against companies running widgets landed every single month — with a peak of 132 in February 2025 alone (UsableNet). If overlays worked as advertised, you would expect those businesses to be the safest in the dataset. They are among the most frequently named.
Why the widget doesn’t save you
An overlay is a piece of JavaScript that loads after your page and tries to patch accessibility problems on the fly — guessing at alt text, relabeling form fields, toggling contrast. The trouble is that the barriers blocking a real assistive-technology user live in your underlying HTML, ARIA, and content, and most of them cannot be reliably automated.
The disability community has been blunt about this. The Overlay Fact Sheet, now co-signed by more than 1,000 accessibility professionals and advocates, lays out why: meaningful alt text requires human judgment a script can’t supply, keyboard navigation and focus order can’t be patched from the outside reliably, and modern JavaScript frameworks rewrite the page faster than an overlay can keep up. WebAIM’s survey of accessibility practitioners is just as damning: 67% rated overlay tools as “not at all” or “not very” effective, rising to 72% among respondents who themselves have disabilities (WebAIM).
This matters in court because the legal test is the user’s actual experience. A plaintiff’s tester opens your site with a real screen reader, hits an unlabeled button or a checkout form they can’t complete, and documents it. The widget in the corner doesn’t change what they encountered. We walk through the mechanics in depth in why overlays don’t work.
The FTC just put it in writing
For years this was a debate between vendors and advocates. In January 2025 a federal regulator weighed in. The Federal Trade Commission ordered overlay vendor accessiBe to pay $1 million to settle charges that it falsely claimed its accessWidget product “can make any website compliant with WCAG” (FTC). The Commission approved the order as final in April 2025.
The FTC’s complaint went further than the compliance claim. It charged that the company “deceptively formatted third-party articles and reviews to appear as if they were independent opinions by impartial authors” while hiding its paid connection to those reviewers (FTC). The disability-rights attorney Lainey Feingold called it a watershed: a government finding that the central promise of the overlay industry — instant, automated WCAG compliance — was not true.
For a business owner, the takeaway is practical, not academic. If a federal agency has formally barred the leading vendor from claiming its tool makes sites compliant, that marketing promise cannot be your defense when a plaintiff’s lawyer asks what you did to make your site accessible.
This is general information, not legal advice. Every case turns on its own facts and jurisdiction. If you’ve received a demand letter or been served, talk to a qualified attorney — and read our practical guide on what to do when a demand letter lands.
What actually reduces your risk
The thing the overlay promised — a site a disabled person can genuinely use — is still the goal. You just have to reach it by fixing the real code instead of layering a script on top of broken markup. That’s the entire case for manual remediation over an overlay.
Here’s the path we recommend to clients who arrive with a widget and a worried email:
- Find the real barriers. A code-level accessibility audit tests your site the way a plaintiff’s tester would — with assistive technology and against WCAG 2.1 AA — so you know what’s actually wrong, not what a scanner guesses.
- Fix them in the source. Manual remediation corrects the HTML, ARIA, content, and components themselves: real alt text, properly labeled accessible forms, keyboard operability, sane heading structure. These are durable fixes that survive a redesign and hold up under scrutiny.
- Keep it from regressing. New pages and product launches reintroduce barriers, so ongoing monitoring catches problems before a tester does.
None of this is exotic, and it isn’t only a legal expense — an accessible site is faster, ranks better, and serves the millions of customers an overlay was never going to help. If you want a concrete plan, our guide on how to avoid an ADA lawsuit lays out the steps in order.
The overlay sold you a sticker that says “compliant.” The litigation data, the disability community, and now the FTC all agree the sticker is not the same as the building being accessible. The good news is that the real fix is well understood — and far more defensible than the widget you’re paying for now.
Want to see what your overlay is papering over? Start with a free scan.