The FTC accessiBe Order, One Year Later: What Actually Changed

The FTC’s $1 million order against overlay vendor accessiBe became final on April 22, 2025. A year on, the order has done what an advertising order can do: the banned promise — that an automated widget can make any website WCAG-compliant — has quietly disappeared from the vendor’s marketing. What it could not do is make widgets work. In the first quarter of 2026, 265 sued websites had an accessibility widget installed — 25.55% of every ADA website lawsuit filed that quarter (EcomBack Q1 2026 report).

If you’re a business owner weighing an overlay right now, this retrospective covers what the order actually banned, how the marketing changed since, and what the current lawsuit data says. We pulled the receipts — the order text, archived sales pages, and fresh litigation numbers — so you don’t have to.

What did the FTC accessiBe order actually prohibit?

The order bans specific marketing claims — it does not ban the product. The heart of the final Decision and Order (Docket No. C-4817) is its first six provisions; the remaining ones are compliance housekeeping. Here they are in plain English:

Two housekeeping details from the order text are worth knowing. It remains in force for 20 years. And accessiBe had to file a compliance report one year after issuance — sworn under penalty of perjury — describing every change it made to comply. That first report came due in spring 2026, which makes right now a fitting moment to check the scoreboard.

Just as important is what the order did not do. It did not find that overlays are illegal, did not shut the product down, and does not bind UserWay, AudioEye, or any other vendor. (The FTC noted the $1 million “may be used to provide refunds to consumers.”) If you’re comparing those tools, our guide to accessiBe, UserWay, and AudioEye alternatives walks through the landscape.

How did the case start?

The FTC announced the settlement on January 3, 2025, alleging that accessiBe’s claims that accessWidget could make any website WCAG-compliant “were false, misleading, or unsubstantiated, in violation of the FTC Act” (FTC press release).

The complaint had a second prong that got less attention: the FTC alleged accessiBe “deceptively formatted third-party articles and reviews to appear as if they were independent opinions by impartial authors” while hiding its paid connections to the reviewers. In other words, some of the glowing coverage a buyer might have Googled in 2023 was, per the FTC, the company reviewing itself.

“Overstating a product’s AI or other capabilities without adequate evidence is deceptive, and the FTC will act to stop it,” said Samuel Levine, then-Director of the FTC’s Bureau of Consumer Protection, in the January announcement. The Commission voted 5-0 to accept the proposed order, took public comment, and then voted 3-0 to finalize it on April 22, 2025.

How has overlay marketing changed since the order?

The compliance promise got replaced with a support promise. To measure the shift, we compared accessiBe’s homepage as archived on December 2, 2024 — one month before the FTC announcement — against the live page in July 2026. The before-and-after is striking:

Read those side by side. “Make your website compliant” became “support ongoing compliance.” The AI-does-it-all framing became “AI, dev tools, and expert services.” The absolute promise became a risk-mitigation pitch.

To be fair: softening the copy is exactly what the order requires, and complying with a federal order is the right thing to do. Our point is for buyers, not against the vendor. The promise you may remember from overlay ads — instant, automatic, guaranteed compliance — is no longer on the page, because a federal agency concluded the evidence didn’t support it. If a salesperson still makes that promise verbally, the vendor’s own website no longer backs them up.

Do accessibility widgets prevent lawsuits?

No — and the year since the order made the pattern clearer, not fuzzier. EcomBack’s litigation tracking counted 1,037 ADA website lawsuits in the first quarter of 2026, and 265 of them — 25.55% — involved websites with an accessibility widget installed. That’s up from 209 widget-equipped defendants in Q1 2025 (EcomBack Q1 2026 report).

Roughly one in four sued sites was paying for the very product marketed as lawsuit protection. If widgets deterred plaintiffs, that share should have collapsed after a year of FTC-mandated honesty in the market. It grew instead. We covered why complaints often cite the widget itself in Is Your Accessibility Overlay Getting You Sued? — the short version is that a widget signals you knew about the problem and chose a shortcut.

What hasn’t changed: the technical reality

An overlay is still a script that loads on top of your existing code. It cannot rewrite your HTML, restructure your headings, fix your form labels in the source, or supply the human judgment that meaningful alt text requires. The Overlay Fact Sheet, signed by 1,031 accessibility professionals and advocates as of July 2026, puts it flatly: “No overlay product on the market can cause a website to become fully compliant with any existing accessibility standard and therefore cannot eliminate legal risk.”

That’s the same conclusion the FTC’s evidence standard forced onto accessiBe’s marketing, arrived at from the technical side. We’ve tested this ourselves — when we ran popular widgets against a real screen reader, the core barriers stayed put (our widget vs. screen reader test). The mechanics are laid out in plain language in why overlays don’t work.

How to read overlay marketing in 2026

The order gives every buyer a free due-diligence checklist. Use the exact things the FTC required and prohibited as your questions:

1. Look for the word “compliant.” If any vendor promises its widget makes you ADA or WCAG compliant automatically, you’re hearing the precise claim the FTC found unsubstantiated when accessiBe made it.
2. Check who wrote the reviews. Search the vendor’s name plus “review” and ask whether the article discloses a paid relationship. Undisclosed connections were half the FTC’s complaint.
3. Ask about third-party content. Provision V exists because widgets can’t fix embedded checkouts, booking tools, or chat services. Ask the salesperson, in writing, what the widget does not cover.
4. Ask for the evidence. The order permits compliance claims backed by “competent and reliable evidence.” Any vendor making the claim should be able to hand you that evidence. Ask for it.
5. Price the alternative. Compare the widget’s annual subscription against actually fixing your code once. Our overlay vs. manual remediation comparison shows the math and the trade-offs honestly.

If a vendor passes all five, you’re dealing with an unusually honest one — and even then, the Q1 2026 lawsuit data applies to their customers too. The deeper question of whether overlays work at all has a well-documented answer.

Where this leaves a small-business owner

One year of enforcement settled the marketing question: the “instant compliance” promise is gone because it couldn’t be substantiated. The engineering question was never really open. What protects you is the thing the widget was impersonating — a site that a screen-reader or keyboard user can genuinely operate.

That path is boring and proven: a code-level accessibility audit to find the real barriers, manual remediation to fix them in the source, and monitoring so new pages don’t reintroduce them. It’s what we do at Curbcut all day, and unlike a widget subscription, the fixes are yours permanently.

Not sure where your site actually stands — with or without a widget running? Start with a free accessibility scan.