The FTC ordered overlay vendor accessiBe to pay $1 million for deceptive WCAG-compliance claims. If you run an accessibility widget, you're not just non-compliant — you're a documented lawsuit target. Here's what changed and what to do.
Accessibility overlays promise compliance in one line of code. Install a widget, the marketing says, and your site is ADA-ready. It sounds effortless. The problem is that courts, regulators, and the disability community have reached the opposite conclusion — and the data is no longer ambiguous.
In early 2025, the Federal Trade Commission penalized an overlay company for lying about what its product does. For any business running an accessibility widget as a shield against ADA lawsuits, this is the moment that shield officially stopped working. Here's what the FTC actually found, why the order matters far more than the dollar figure, and what real WCAG 2.2 AA compliance requires instead.
The $1 million wake-up call
In January 2025, the FTC announced a complaint and proposed order requiring software provider accessiBe — one of the largest AI-powered web accessibility widget vendors — to pay $1 million to settle allegations that it misrepresented its product. The Commission approved the order as final in April 2025. It was the first federal enforcement action against an overlay vendor.
accessiBe marketed its accessWidget tool as a one-line script that could make any website compliant with the Web Content Accessibility Guidelines (WCAG). The FTC found those claims "were not supported by competent and reliable evidence." As the agency's Bureau of Consumer Protection put it, companies seeking WCAG compliance must be able to trust that products do what they're advertised to do — and overstating an AI product's capabilities without adequate evidence is deceptive.
Translation: a federal regulator has now gone on the record that an automated widget cannot, by itself, make a website compliant. If you installed one thinking you'd bought a layer of legal protection, the FTC just said otherwise.
What accessiBe actually got caught doing
According to the FTC's complaint, accessiBe ran afoul of the FTC Act in two distinct ways — and both matter for any business evaluating an overlay.
Overstating WCAG compliance
accessiBe's marketing claimed that installing accessWidget's "one line of code" made a website compliant with 30% of WCAG's requirements immediately, then used AI to reach full compliance within 48 hours. The FTC's complaint alleged the opposite: in numerous instances, accessWidget failed to make basic, essential components — menus, headings, tables, images, recordings — compliant and accessible to people with disabilities. WCAG is a comprehensive technical standard covering keyboard navigation, semantic structure, focus management, and more. No script injected into a finished site can retroactively fix problems baked into the underlying code.
Faking independent reviews
The complaint also alleged that accessiBe deceptively formatted third-party articles and reviews to look like independent, impartial editorial coverage — while failing to disclose its material connections to those reviewers. That's a separate violation of consumer-protection law: deceptive endorsements. For a company selling trust, getting cited by the FTC for faking trust signals is its own kind of damning.
Why the order matters more than the fine
The $1 million is the small story. accessiBe reportedly earned tens of millions in 2024, so the fine alone is a rounding error. The consequential part is what the final order locks in.
Under the order, accessiBe is barred for 20 years from representing that its automated products can make any website WCAG-compliant — or ensure continued compliance over time — unless it has competent, reliable evidence to support the claim. It must disclose material connections to endorsers. And it must file annual compliance reports with the FTC throughout that period. Future violations can trigger civil penalties of up to $51,744 per occurrence.
The federal government has now formally classified "this widget makes you WCAG-compliant" as a deceptive business practice.
That's the precedent. Every other overlay vendor making the same promise is now operating on borrowed time — and some are quietly rewriting their marketing copy. Watch for it.
The lawsuit problem widgets were supposed to solve — and made worse
Here's the irony at the center of the overlay business. Companies install accessibility widgets specifically to avoid ADA Title III lawsuits. Then they get sued anyway — often at higher rates than businesses with no widget at all.
According to UsableNet's 2024 report, roughly a quarter of all US web accessibility lawsuits that year targeted sites that already had an overlay installed — the widget cited as a barrier, not a defense. That trend continued into 2025. Plaintiff firms know overlays don't deliver compliance and specifically target sites running them, because the widget is two things at once: evidence the business knew about its accessibility obligations, and proof it chose a solution that doesn't work.
The widget, in other words, is the lawsuit's smoking gun. And post-FTC, it's also evidence the business relied on a product category a federal regulator has called deceptive. Expect plaintiffs' attorneys to cite this order in demand letters for years.
What actually makes a website compliant
The technical reason is simple. An overlay injects JavaScript on top of your existing code at page load — it can't repair the underlying HTML structure, broken keyboard navigation, or flawed ARIA logic baked into your site. Automated tooling, overlay or otherwise, only detects a fraction of accessibility issues; the rest require human judgment with real assistive technology. A script layered over the problem doesn't remove it.
Real WCAG 2.2 AA compliance — the standard courts look to in ADA Title III claims — requires three things, none of which is a script tag.
- A real audit. Every page tested against every relevant WCAG success criterion: keyboard navigation, color contrast, semantic structure, alt text, form labels, focus order, error identification, landmarks. Automated scans catch a portion of issues; the rest need a human reviewer with screen-reader experience.
- Real code fixes. Not a JavaScript overlay that paints over problems at runtime, but actual changes to your HTML, CSS, and components so screen-reader, keyboard, voice-control, and zoom users can use the site as intended.
- Ongoing verification. Every deploy can introduce new violations. A site compliant in January isn't necessarily compliant in March. Re-scan, re-audit, re-fix.
There's no shortcut. Anyone selling you one is selling you the next enforcement action.
How to respond if you're running a widget
If you have an overlay installed today, a practical sequence:
- Don't panic, but don't wait. The widget isn't protecting you; leaving it indefinitely just extends the exposure.
- Get a real audit of your site against WCAG 2.2 AA, so you know your actual violations rather than the ones a widget claims to have fixed.
- Remediate at the code level, prioritizing the high-frequency, high-severity issues that drive litigation.
- Decide on the widget deliberately. Some businesses keep an overlay for the genuine end-user features it does provide (text resizing, contrast toggles), but never as a substitute for real conformance — and never with compliance claims attached.
- Move to continuous monitoring, so conformance holds across future deploys and you have a time-stamped record of your remediation practice.
The bottom line
The FTC's action against accessiBe — the $1 million payment, the 20-year order, the public statement — is now part of the federal record, and it says plainly that automated widgets do not make websites compliant. If you're running one, two things are true at once: your customers with disabilities still can't fully use your site, and you now have a regulator on record describing the thing you relied on as deceptive.
That's why Accessive doesn't hide issues behind a widget. Every audit combines automated scanning (axe-core) with expert review against WCAG 2.2 AA, ADA Title III, and Section 508. You get concrete, code-level fixes for each finding, and continuous monitoring catches new regressions as your site changes — so compliance holds between audits.
Take the widget off the pedestal, get an actual audit, fix the code, and verify it over time. That's the only path to accessibility that holds up — in court, with the FTC, and with the customers you're trying to serve.
This article is for general information and is not legal advice. For guidance on your specific situation, consult a qualified attorney. Source: FTC, "FTC Approves Final Order Requiring accessiBe to pay $1 Million," April 2025.