Yes. On January 3, 2025, the Federal Trade Commission announced an action against accessiBe, the maker of the accessWidget overlay, and the final order was approved in April 2025. The FTC accessiBe fine was $1 million, and the FTC alleged the company deceptively claimed its overlay could make any website WCAG-compliant — ‘30% immediately and the remaining 70% via AI within 48 hours’ — while formatting paid reviews to look independent. The order bars the company from making unsubstantiated compliance claims going forward. In plain terms, a federal regulator has now said that selling a script as an instant fix for accessibility law is deceptive advertising.
What did the FTC actually say about overlays?
The FTC did not ban accessibility technology. It targeted the marketing claim — specifically the promise that a single line of JavaScript could take a broken website and make it conform to the Web Content Accessibility Guidelines automatically. That claim, the agency alleged, was not substantiated by evidence.
This matters because it draws a bright line under something the accessibility community has said for years. Automated tools, including overlays, can only detect and address a portion of the problem. Automated scanning catches roughly a third of the WCAG success criteria; the rest — things like whether a screen reader can actually complete a checkout, whether focus order makes sense, whether error messages are understandable — require human testing. A tool that markets itself as covering all of it is overpromising by design.
The National Federation of the Blind, the largest organization of blind Americans, has gone further, formally opposing overlay products and describing them as ‘not only ineffective but harmful.’ The FTC action is the first time a federal agency has put money behind that critique.
Does an overlay actually protect you from a lawsuit?
The evidence says no. WebAIM's analysis of the top one million homepages found that sites running overlays averaged roughly as many detectable errors as sites without them. And UsableNet's year-end reports repeatedly find that hundreds of companies sued for web accessibility each year already had a widget or overlay installed when the lawsuit landed.
That is the trap. A business owner installs an overlay, sees a marketing badge claiming compliance, and believes the problem is solved. Meanwhile the underlying code — the missing alt text, the unlabeled forms, the low-contrast buttons — is untouched, and a serial plaintiff's tester finds those failures in minutes. If you want the fuller breakdown of why the technology falls short, why overlay widgets fail walks through the mechanics.
The litigation numbers make the stakes concrete. More than 5,000 digital-accessibility lawsuits were filed in 2025, up roughly 20% over the prior year, and most settle for between $10,000 and $75,000 plus a remediation commitment. An overlay that doesn't fix the code doesn't lower that risk — it just adds a subscription fee on top of it. See the 2026 ADA lawsuit trends for where the filings are concentrated.
Is a compliance overlay the same as an accessibility widget?
No, and the distinction is worth understanding before you rip anything off your site.
The two are not the same thing
A preference widget is a user-facing set of display controls — a button that lets a visitor bump up text size or switch to higher contrast — layered on a site that is already accessible at the code level and makes no compliance claims. ADA Fail's own site runs one. It's a convenience, not a legal shield.
A compliance overlay is a third-party script sold on the promise that it makes a broken website conform to the law. That marketing claim — not the button itself — is what the FTC went after, and it's what puts a false sense of security between you and a real remediation plan.
The FTC's order is aimed squarely at the compliance claim. If a vendor tells you their tool will make you ‘ADA compliant’ or ‘WCAG compliant’ by tomorrow, that is exactly the kind of language the Commission found deceptive. Our deeper comparison lives at accessibility widget vs. overlay.
What should you do if your site runs an overlay?
Don't panic, and don't assume the badge on your footer means anything to a court. Take these steps in order.
- Stop relying on the compliance claim. The overlay may still function as a preference widget, but treat it as zero legal protection. The underlying code is what a tester examines.
- Get an honest baseline. Run an automated scan to see your machine-detectable failures — the low-contrast text, missing alt attributes, and empty links that make up the most common issues in the WebAIM data, where 94.8% of top homepages had detectable WCAG failures. Remember that a clean automated scan means you have zero automated-scan violations, not that you conform to WCAG.
- Get expert human testing for the rest. The two-thirds of criteria a scanner can't see — keyboard traps, screen-reader flow, form error handling — need a person. This is the only path to genuine WCAG 2.2 AA conformance.
- Fix the code, not the surface. Real remediation edits your HTML, ARIA, and templates so the site works for assistive technology directly, with no script papering over the gaps.
If you'd rather start with a clear read on where you stand, a free accessibility audit from ADA Fail shows your automated-scan grade and flags the human-testing issues an overlay was never going to catch. If a demand letter has already arrived, what to do about an ADA website demand letter covers your next move.
What the FTC action does and doesn't change
It doesn't create a new law. ADA Title III still has no formal federal regulation naming a web standard; courts and settlements continue to treat WCAG — specifically the 2.2 AA benchmark ADA Fail audits against — as the de facto measure. What changed is the marketing environment. Vendors can no longer safely claim a script delivers compliance, because a federal regulator has ruled that claim deceptive and made it cost a million dollars.
For a decision maker, the takeaway is simple. The shortcut was never real. The businesses that reduce their legal exposure are the ones that fix their code to a genuine WCAG 2.2 AA standard, document it honestly, and skip the tools that sell certainty they can't deliver. That is more work than pasting in a script — and it's the only version that holds up when a tester, or a court, actually looks.
If your site currently leans on an overlay — or you simply don't know where it stands — start with a free accessibility audit. ADA Fail will show you your automated-scan grade, flag the human-testing issues no script can catch, and give you a straight answer on what real remediation would take. No badge, no false promises.
Frequently asked questions
Do I have to remove my accessibility overlay after the FTC order?
The FTC order targets the vendor's advertising, not your obligation to run or remove any specific tool. You are not legally required to remove an overlay. The practical question is whether it's doing anything useful: if it's making unsubstantiated compliance claims on your behalf, that's a liability, but if it functions purely as a display-preference button on top of accessible code, it's harmless. If you decide to take one off, how to remove an accessibility overlay covers the process cleanly.
If an overlay doesn't work, how do I actually reduce my lawsuit risk?
By fixing the site itself. That means correcting the machine-detectable issues an automated scan finds — contrast, alt text, form labels — and then having a human tester verify the criteria a scanner can't, such as keyboard navigation and screen-reader flow. The goal is genuine WCAG 2.2 AA conformance, documented in an accessibility statement. Our ADA website compliance checklist lays out the full sequence.
Does the FTC action apply to companies outside the United States?
The FTC order binds the specific vendor it names, but the underlying lesson — that ‘instant compliance’ claims are unsubstantiated — applies anywhere. If you sell into the EU, you also face the European Accessibility Act, whose enforcement began June 28, 2025 and which expects EN 301 549 (built on WCAG 2.1 AA) for e-commerce. See the European Accessibility Act and US companies for how that overlaps with US obligations.