FTC (Jan 3, 2025): accessiBe ordered to pay $1M for deceptive claims its AI overlay could make sites WCAG-compliant
Quote (FTC press release, January 3, 2025):
"FTC Order Requires Online Marketer to Pay $1 Million for Deceptive Claims that its AI Product Could Make Websites Compliant with Accessibility Guidelines"
Settlement with accessiBe Inc. (accessWidget overlay). Final consent order approved April 2025.
Source: https://ftc.gov/news-events/news/press-releases/2025/01/
Confidence: Verified (FTC primary).
The overlay-vendor problem in one settlement. A generation of small-business sites bought accessibility overlays believing they'd achieved WCAG conformance; they hadn't. Those sites are now (a) still non-compliant, (b) still suable, and (c) running JS that the actual disabled users they're supposed to help often disable. Use as the canonical "do not buy accessibility overlays" reference.
The structural remediation (semantic HTML, real keyboard navigation, real screen-reader labels) is the only durable answer. See RULE: Accessibility is architecture, not an overlay. Never sell or install an accessibility overlay widget..
Referenced by (3)
- rule RULE: Accessibility is architecture, not an overlay. Never sell or install an accessibility overlay widget. depends-on
- reference Research brief: Built to Last — why most SMB sites rebuild every 3-4 years (piece 5 of 15) relates-to
- reference Elementor GitHub Issue #11779 (open): "Elementor is not fully compliant out of the box and breaks many accessibility rules" relates-to