What the FTC's $1M accessiBe settlement means if you use an overlay

In January 2025, the US Federal Trade Commission announced that accessiBe, maker of the accessWidget overlay, would pay $1,000,000 to settle charges that it deceptively claimed its AI product could make any website compliant with WCAG (FTC press release, Jan 3, 2025). The final order was approved on April 21, 2025 (FTC press release, Apr 21, 2025). If your compliance plan is "we installed a widget," this settlement is worth ten minutes of your time.

Quick note before we start: I'm not a lawyer and this isn't legal advice. It's a plain-English read of public documents, with links so you can check everything yourself.

What the FTC actually alleged

The complaint had two parts, and both matter.

First, the marketing claims. The FTC alleged that accessiBe's claims that accessWidget could make any website WCAG compliant were false, misleading, or unsubstantiated. Not a technicality about wording. The core pitch (install one line of JavaScript, become compliant) was the thing the FTC said couldn't be backed up. And "unsubstantiated" is doing real work in that sentence. US advertising law doesn't just punish claims proven false; it requires you to have evidence for objective claims before you make them. The agency's own business guidance blog later walked through the case as a cautionary tale for anyone making unsubstantiated performance claims about AI products.

Second, the reviews. The FTC alleged that accessiBe paid for reviews and articles that were formatted to look like independent, impartial opinions, without disclosing the material connection. So a buyer researching "is accessiBe legit" could land on what looked like a neutral third-party review and actually be reading sponsored content.

Disability rights lawyer Lainey Feingold, who has tracked overlay litigation for years, has a detailed breakdown of the complaint and order at lflegal.com. The full docket, including the complaint and the order itself, is on the FTC's site under case 2223156.

The timeline

Here's how it played out:

• January 3, 2025. The FTC announces the proposed consent order and the $1,000,000 payment (source). The proposal then goes through a public comment period.
• April 21, 2025. The Commission approves the final order (source). At that point it stops being a proposal and becomes a binding order.

Why does the gap matter? Because the final order survived public comment unchanged in substance. This wasn't a trial balloon that got walked back.

What the order requires going forward

The money is the headline, but the forward-looking requirements are the useful part for the rest of us. Under the order, accessiBe is:

• Prohibited from misrepresenting what its products can do, including claims that an overlay can make websites WCAG compliant, unless such claims are true and substantiated.
• Prohibited from misrepresenting endorsements, meaning paid reviews can't be dressed up as independent opinions, and material connections have to be disclosed.
• On the hook for $1,000,000, paid to the FTC.

Read that first bullet again. A US regulator has ordered an overlay vendor to stop claiming its widget makes websites WCAG compliant. That's about as direct a statement as you'll get on the gap between overlay marketing and overlay reality.

What accessiBe said

Fairness matters here, so here's their side. accessiBe disputed the FTC's characterizations. In press coverage, the company said it strongly disagreed with the allegations, arguing they were based on flawed testing methodologies and outdated information, and noted that the settlement involved no admission of wrongdoing. They framed settling as a way to move forward without the distraction of a lengthy legal process (PYMNTS coverage).

That's a normal thing for a company to say, and no-admission settlements are common. But note what the response doesn't do: it doesn't change the order. The prohibitions stand either way.

What this means if you have an overlay installed

Here's the uncomfortable question: if the vendor can no longer claim the widget makes your site WCAG compliant, what exactly are you paying for?

The FTC action was about accessiBe's marketing, not about your website. Nothing in the order fines overlay customers. But it removes the main comfort blanket. If a complaint or lawsuit lands on your desk, "the vendor told us we were compliant" was always a thin defense. After this settlement, it's thinner. The regulator that polices advertising claims has said, in a binding order, that this specific claim couldn't be substantiated.

And the lawsuit data backs that up. Sites with overlays installed still get sued regularly, and in some complaints the overlay itself is cited as a barrier. The settlement didn't create that problem. It just made it much harder to ignore.

There's a second lesson hiding in the reviews allegation, too. If you evaluated your overlay by reading "independent" comparison articles, it's worth asking who paid for them. When you research alternatives (we keep an honest accessiBe comparison ourselves), look for vendors that show you what they actually detect and fix, not testimonial pages.

What to do instead

I won't pretend there's a one-line-of-JavaScript answer, because that pitch is exactly what just cost a vendor a million dollars. The honest path has three parts:

1. Find the real failures. Run automated WCAG checks against your actual pages. Contrast, missing alt text, unlabeled form fields, broken heading structure. These are detectable and they're the same things plaintiffs' testers find.
2. Fix them at the source. In your templates, components, and content. Most individual fixes are small once someone owns them. An overlay papers over symptoms in the visitor's browser; a source fix removes the failure for everyone.
3. Keep a record. Dates, findings, fixes, re-scans. A documented remediation program is real evidence of good-faith effort, which matters if a demand letter ever shows up. "We installed a widget" is not a program. A history of issues going to zero is.

Not sure where to start? Start with the pages where money and access change hands: your homepage, product or service pages, forms, and checkout. Those are the flows a real user gets stuck in, so they're the flows a tester checks first. Getting five key pages genuinely clean beats sprinkling a widget across five hundred.

That's the boring answer, and it's the one that holds up.

Full disclosure: this is the workflow BugPort is built for. We scan against WCAG success criteria, turn findings into bug reports with element-level evidence, and track re-scans so you can show the count going down. We will never tell you a tool makes you compliant, because compliance is a property of your site, not of anything bolted onto it.

FAQ

Did the FTC ban accessibility overlays?

No. The order targets accessiBe's marketing claims and endorsement practices, not the existence of overlay products. Overlays are still legal to sell and to use. What the order prohibits is claiming, without substantiation, that an overlay makes websites WCAG compliant.

Am I at risk if I currently use accessWidget or another overlay?

The FTC order doesn't penalize customers. But separate from the FTC, ADA lawsuits are filed against widget-equipped sites every month, so an overlay alone shouldn't be your whole plan. If accessibility matters to your business (it should), treat the widget as a supplement at most, and fix the underlying failures. Again, not legal advice; talk to a lawyer about your specific exposure.

Did accessiBe admit wrongdoing?

No. The company said it disagreed with the FTC's allegations and characterizations and settled without admitting wrongdoing, describing the settlement as a way to avoid a lengthy legal process (PYMNTS). The order's prohibitions apply regardless.

Where can I read the actual order?

The complaint, proposed order, and final order are all public on the FTC docket for accessiBe. The two press releases (January and April 2025) are the fastest summaries.

Want to know what a plaintiff's tester would find on your site today? Run a free WCAG audit and see the actual failures, mapped to the success criteria they violate.