Accessibility ≠ Overlay: FTC sanctions misleading accessiBe claims about WCAG compliance
In April 2025, the U.S. Federal Trade Commission approved a final order against accessiBe. The company must pay $1 million and may not claim that its automated products can make any website WCAG-compliant or maintain compliance over time unless it has evidence supporting those claims.
From marketing promise to regulatory action
This fifth installment adds a consumer-protection regulator to the debate. The FTC announced its complaint in January 2025 and approved the final order on April 22, 2025.
According to the FTC, accessiBe marketed accessWidget as an AI-powered tool able to make any website comply with WCAG. The complaint alleged that the product did not make all customer websites compliant and that the claims were false, misleading, or unsubstantiated.
What the final order requires
The order does not say all automation is unlawful. It specifically bars accessiBe from claiming that its automated products can make any website WCAG-compliant or ensure continued compliance unless it has evidence to substantiate the claim. The company must also pay $1 million, which the FTC said may be used for consumer refunds.
Evidence is the key word
A promise such as “install this script and your website will comply with WCAG” should not be treated as a demonstrated technical fact merely because it appears in marketing. WCAG conformance depends on verifiable criteria across pages, components, content and interactions. Websites also change over time, making claims of continuous compliance particularly demanding.
It was not only about WCAG
The FTC also challenged marketing practices. It alleged that some third-party articles and reviews were formatted to appear independent and objective without adequately disclosing material connections to the company. The final order restricts misrepresentations about independent endorsers and material facts about the products.
What the FTC did not say
The FTC did not issue a general ban on accessibility overlays, nor did it decide that every use of AI in accessibility is deceptive. It acted on specific compliance claims that, according to its complaint, were not supported by the product’s actual performance.
What businesses should ask before buying an overlay
Ask which criteria are covered, how performance was verified, what remains outside automation, how the solution works with keyboards and screen readers, what happens when the site changes, and what evidence supports any percentage or compliance promise. A tool that helps find or repair issues is not the same as proof that an entire site conforms.
Accessibility remains a property of the product
Accessibility must still be verified in the interface people use: semantics, keyboard navigation, focus, forms, text alternatives, accessible names and states, contrast and component behavior. Automation can assist, but a marketing promise cannot replace evaluation.
Official sources
FTC final order — April 22, 2025
Complaint and proposed order — January 3, 2025
Part 05 of Accessibility ≠ Overlay.