The FTC accessiBe Order (File 222-3156, $1M) Explained

What happened, in one paragraph

On January 3, 2025 the U.S. Federal Trade Commission announced a complaint and a proposed consent order against accessiBe, the company behind the accessWidget accessibility overlay. The matter is docketed as FTC File No. 222-3156. The Commission later approved the order as final in April 2025. The final order requires accessiBe to pay $1,000,000 that, in the FTC's own words, “may be used to provide refunds to consumers.” This article summarizes what the FTC alleged, attributed strictly to the agency's public filings, and explains why a documentation-based approach avoids the specific kind of marketing claim the FTC took issue with. It is informational and not legal advice.

• FTC press release, January 3, 2025 (complaint and proposed order)
• FTC press release, April 2025 (final order approved)
• Case landing page, File No. 222-3156

What the FTC alleged

According to the FTC's filings, the agency alleged that accessiBe's accessWidget did not make websites WCAG-compliant in the way the product was marketed. The FTC characterized claims that an AI-powered overlay could make a website compliant as deceptive. The agency also alleged that third-party reviews of the product were presented in a way that appeared independent when, per the FTC, they were not. Every characterization in this section is the FTC's, drawn from its January 3, 2025 announcement and the case record under File No. 222-3156. We are not asserting anything about accessiBe beyond what is in the public record.

The FTC alleged that accessiBe deceptively claimed its AI-powered accessWidget could make any website compliant with accessibility standards, and that it formatted and promoted third-party reviews in a way that did not disclose its connection to them.

Summarizing the U.S. FTC complaint, File No. 222-3156, January 2025

What an accessibility overlay is

An accessibility overlay (the accessWidget category) is a JavaScript widget added to a website with a single line of code. Once loaded, it re-styles the page at runtime. In practice this usually means an accessibility icon that opens a toolbar with controls for contrast, text size, spacing, and similar adjustments. The widget lives on top of the existing site and changes how it renders in the browser.

Re-styling a page at runtime is not the same as the underlying site conforming to WCAG. WCAG conformance is a property of the markup, structure, and content that a site ships, evaluated against the success criteria. A toolbar that lets a visitor enlarge text or flip on a high-contrast mode does not, by its presence, establish that a page meets those criteria. That gap, between presenting a compliance-flavored control and the site actually conforming, is the territory the FTC's marketing-claims case sits in.

The $1,000,000 and where it goes

The final order, approved in April 2025, requires accessiBe to pay $1,000,000. The FTC's order language states that this money “may be used to provide refunds to consumers.” In other words, the sum is framed as consumer redress rather than a penalty paid to the government and kept there. The figure and the redress framing both come directly from the FTC's April 2025 announcement of the final order. We have not added to or reinterpreted those numbers.

• Case: FTC matter re: accessiBe, File No. 222-3156
• Timeline: complaint and proposed order announced January 3, 2025; final order approved April 2025
• Amount: $1,000,000 that the FTC says may be used to provide refunds to consumers

The takeaway: documentation, not a widget

The throughline of the FTC's case is about marketing claims, specifically the claim that an automated product could make a website compliant with one click. A posture built on documentation rather than a runtime widget does not make that claim in the first place.

Paperfort sits on the documentation side. It runs an automated WCAG 2.2 AA scan using axe-core and produces three artifacts: a timestamped audit report that records what the scan found, a VPAT 2.5 conformance report that procurement and enterprise buyers ask for, and a hosted accessibility statement page on your own domain. It installs nothing on your storefront and re-styles nothing at runtime. The deliverable is a record of an evaluation and a prioritized list of what to fix, handed to you and your developer.

That framing matters for an honest reason. Automated scanning is a real tool, but it is a partial one. Industry baselines from Deque, the maker of axe-core, put the share of WCAG issues detectable by automated means at roughly 30 to 50 percent. The rest, things like whether alt text is meaningful or whether a keyboard flow makes sense, require human judgment. Paperfort does not claim to catch everything, and it does not claim to make a store compliant. It documents what an automated scan can see and tells you where to look next. This is informational content, not legal advice; consult your own counsel about your specific obligations.

What this does and does not mean for your store

The FTC order does not make overlays illegal. It concerned specific marketing claims the FTC alleged were deceptive, not the overlay technology itself. Plenty of merchants run overlays today, and that is a decision to make with your own advisors. What the order is, fairly read, is a signal about marketing claims: regulators are willing to challenge “one-click compliance” messaging when, in the agency's view, the product does not deliver what the marketing promises.

For a Shopify merchant, the practical reading is modest. Be skeptical of any product, overlay or otherwise, that promises automatic ADA or WCAG compliance. Treat accessibility as ongoing work on your actual site, supported by documentation you can point to. And keep the limits of automation in view: no scanner, Paperfort included, detects every issue. None of this is legal advice. If you need to know what your store specifically must do, talk to a lawyer who handles accessibility matters.