If you have read anything about web accessibility overlays in the last year, you have probably seen a sentence like this one: "the FTC fined accessiBe one million dollars." It appears in trade press, in agency blog posts, in LinkedIn threads, and, until recently, on this website too.
It is wrong. Not the number, not the company, not the subject matter. The legal characterisation. And the difference matters enough that it is worth spending an article on, because the way the case is usually described makes it sound like something it is not, and that gets in the way of the useful lesson inside it.
Two documents matter.
On 3 January 2025 the Federal Trade Commission announced a complaint and a proposed consent order against accessiBe Inc. and accessiBe Ltd., File No. 2223156. The FTC's own press release describes it plainly:
"The Federal Trade Commission will require software provider accessiBe to pay $1 million to settle allegations that it misrepresented the ability of its AI-powered web accessibility tool to make any website compliant with the Web Content Accessibility Guidelines (WCAG) for people with disabilities."
Note the verb: settle.
On 22 April 2025 the Commission approved the final consent order, by a vote of 3 to 0, after a public comment period.
So: one million dollars, paid to the FTC, which the agency may use to provide refunds to consumers. Announced January 2025, final April 2025.
The FTC cannot simply impose a fine in a first-time deception case under Section 5 of the FTC Act. It does not have that power. What it can do is bring a complaint and negotiate an order that the company agrees to.
That is what a consent order is: a settlement. The company agrees to stop doing the thing, agrees to pay, and does not admit liability. No court found accessiBe liable. No judge ruled on the merits.
The order does have teeth going forward. The FTC's release spells it out:
"When the Commission issues a consent order on a final basis, it carries the force of law with respect to future actions. Each violation of such an order may result in a civil penalty of up to $51,744."
So the penalties come later, if the order is breached. They did not come now.
This distinction is not pedantry. Writing "the FTC fined accessiBe" states something legally false about a named company. If you publish that on a commercial page, you are making a false statement about a competitor, which is a worse position to be in than simply describing the settlement accurately. Plenty of otherwise careful sources got this wrong, including trade press and at least one accessibility non-profit. Copying them does not make it safer.
This is the part worth reading, and almost nobody quotes it. From the FTC's administrative complaint:
"Respondents claim that installing accessWidget's 'one line of code' makes a website compliant with 30% of WCAG's requirements immediately and initiates an AI process that makes the website fully compliant with the remaining 70% of WCAG requirements within 48 hours."
And the FTC's answer to that claim:
"Contrary to accessiBe's promises, in a number of instances accessWidget fails or has failed to make basic and essential website components like menus, headings, tables, images, recordings, and more, compliant with WCAG and accessible to persons with disabilities."
There was a second, separate allegation that gets even less attention:
"accessiBe has made these advertising claims on its website and social media, as well as in paid advertisements that Respondents knew were deceptively formatted to appear like impartial reviews and articles."
So two things: the compliance promise was not substantiated, and some of the independent-looking praise for the product was paid for and not disclosed as such.
That second point is quietly the more useful one for anyone evaluating accessibility tooling. If you are researching a vendor and the reviews look glowing and oddly uniform, the FTC has already documented one case where that pattern was manufactured.
Being precise cuts both ways, so here is the other side.
It is not a ruling that overlays are illegal. It is a settlement about specific marketing claims made by one company. Nothing in it says a merchant may not install a widget.
It is not a court decision. No judicial finding, no precedent, no admission.
It does not say overlays do nothing. It says a specific product did not do what its marketing promised, on named categories of page components.
You will sometimes see the further claim that "courts have held that overlay widgets do not relieve merchants of their compliance obligations." I went looking for the case behind that sentence and could not find one. It was on this site until this week and I have removed it, because I could not stand it up with a citation. If a published decision holding that exists, I would genuinely like to see it.
What exists instead is a putative class action brought by a merchant against accessiBe in the Southern District of New York in June 2024, whose exhibit lists federal cases where the defendant's site was running the widget on the day it was sued. That is a party's pleading and a list of docket numbers, not a holding. It is suggestive. It is not a ruling, and I am not going to dress it up as one.
Here is the thing: you do not need a court decision to make the point, because the statutes say it directly.
Accessibility law puts the duty on the trader providing the service. Germany's BFSG addresses the Dienstleistungserbringer, the service provider. In France, article L412-13 of the Consumer Code addresses the economic operator supplying the service. Poland's transposition puts the obligations on the usługodawca and, under article 32, requires that provider to carry out its own conformity assessment.
Installing a third-party script does not move that duty to the script vendor. It cannot. The duty is attached to whoever offers the service to the consumer, and that is the merchant.
Which means a vendor's promise about compliance is not evidence that your store is compliant. It is evidence about the vendor's marketing. The FTC case is a well-documented illustration of exactly that gap.
Poland's Fundacja Widzialni made the same point in January 2025, writing that in its experts' view relying solely on such technologies does not deliver accessible digital content for the user, and that a real audit plus fixes needs a range of tools and, above all, human involvement.
Three practical things.
Ask what the evidence looks like. If a regulator or a customer asks how your store meets the requirements, what do you hand over? A runtime widget changes the page in the visitor's browser and leaves nothing behind. A change to the theme code leaves a diff, in a file, with a date on it. When the Polish statute asks for "dowodów potwierdzających dokonanie tych czynności", evidence confirming the work was done, one of those two answers is a lot easier to give.
Treat compliance claims as claims. "Makes your site WCAG compliant" is a marketing sentence, not a technical result. The FTC complaint is the clearest available demonstration that the sentence and the result can come apart.
Check your own store rather than trusting a category. This applies to us as much as to anyone else. We sell a scanner that proposes Liquid fixes, and I would rather you scanned your store and looked at the actual findings than took my word for what your theme does.
No. The FTC brought a complaint and accessiBe agreed to a consent order, which is a settlement. The company pays 1 million USD and does not admit liability. No court found accessiBe liable and no judge ruled on the merits. The FTC cannot simply impose a fine in a first-time deception case under Section 5 of the FTC Act.
One million US dollars, paid to the Commission, which the agency may use to provide refunds to consumers. The complaint and proposed order were announced on 3 January 2025 and the Commission approved the final consent order on 22 April 2025 by a vote of 3 to 0.
Two things. First, that accessiBe's claim that installing its widget makes a website compliant with WCAG was not substantiated, and that in a number of instances the product failed to make basic page components such as menus, headings, tables and images accessible. Second, that paid advertisements were formatted to look like impartial reviews and articles.
No. It is a settlement about specific marketing claims made by one company. Nothing in it says a merchant may not install a widget, and it does not establish that overlays do nothing. It says one product did not do what its marketing promised, on named categories of page components.
No. Accessibility law places the duty on the trader providing the service. Germany's BFSG addresses the service provider, article L412-13 of the French Consumer Code addresses the economic operator supplying the service, and Poland's transposition puts the obligation on the service provider and requires it to carry out its own conformity assessment. A third-party script cannot move that duty to the script vendor.
I looked for one and could not find it. That sentence was on this site and I removed it because I could not support it with a citation. What does exist is a putative class action filed against accessiBe in the Southern District of New York in June 2024, whose exhibit lists federal cases where the defendant's site was running the widget when it was sued. That is a party's pleading, not a holding.
Treat compliance claims as claims rather than results, and ask what evidence you could hand a regulator or a customer. A runtime widget changes the page in the visitor's browser and leaves nothing behind. A change to the theme code leaves a diff, in a file, with a date on it.
Everything above is quoted from primary documents. They are short and worth reading yourself.
One note on the Widzialni article: it is a solid statement of position, but it describes the FTC action as a fine, sourced to TechCrunch. That is the same error this piece is about. Good source for the position, not for the legal characterisation.