Accessibility overlays are JavaScript widgets that sit on top of your website and promise "instant WCAG compliance with one line of code." They do not work. On 3 January 2025, the FTC announced a $1 million civil penalty settlement with accessiBe — the largest overlay vendor — for deceptive marketing of its accessWidget product. The final consent order was approved on 22 April 2025 (Decision and Order issued 21 April 2025, Docket C-4817). The FTC found that accessWidget did not make basic website components like menus, headings, tables and images accessible, and that accessiBe paid for third-party reviews presented as independent. If you run a European business with an overlay installed, you are as exposed to EAA enforcement as a business without one.
The FTC case: what exactly happened
The FTC's complaint against accessiBe alleged that its accessWidget product misrepresented its ability to make any website WCAG-compliant. The marketing claim was specific: accessWidget would cover 30% of accessibility requirements immediately, reaching full WCAG compliance within 48 hours through an AI process. The FTC alleged those claims were false, misleading or unsubstantiated — a violation of the FTC Act.
The FTC documented a specific technical example that illustrates the problem with clarity. A photo of a filet mignon on a ceramic plate received the following automatically generated alternative text from accessWidget:
Accurate description enabling a visually impaired user to understand what the image shows.
Wrong. Fabricated. Potentially misleading to a screen-reader user in a food ordering context.
The terms of the consent order: what accessiBe can no longer do
The FTC's final consent order, approved on 22 April 2025 (Decision and Order issued 21 April 2025, Docket C-4817), imposes specific bars on accessiBe's conduct going forward. These bars define exactly what the FTC considers impermissible in overlay marketing.
No WCAG-compliance claims without supporting evidence
accessiBe is barred from representing that its automated products can make any website WCAG-compliant or ensure continued WCAG compliance over time, unless it has substantiated evidence to support such claims.
No misrepresentation of material facts about its products
accessiBe is prohibited from misrepresenting the capabilities of its accessibility products in any material respect.
No presenting paid endorsements as independent opinions
accessiBe is prohibited from misrepresenting that third-party reviews or articles reflect independent opinions of impartial authors, when those authors have material connections to the company.
Mandatory disclosure of material connections with endorsers
accessiBe must clearly and conspicuously disclose any "unexpected material connection" that an endorser has to the company. This applies to blog posts, reviews, social media posts and similar content.
The $1 million may be used for consumer refunds
The civil penalty settlement amount may be directed toward providing refunds to consumers who purchased accessWidget in reliance on the misrepresentations the FTC found unlawful.
Why overlays technically cannot deliver WCAG compliance
The FTC case is regulatory confirmation of what accessibility engineers have documented for years. Overlays fail for five specific technical reasons that cannot be engineered around:
Cannot modify the underlying code
An overlay sits on top of your HTML, CSS and JavaScript. It cannot restructure your DOM, fix your heading levels, or correct your semantic markup. The accessibility problems remain in the source.
Interfere with existing assistive technologies
Screen reader users typically disable overlays immediately because they conflict with their established browser and AT configurations. An overlay can create new barriers for the very users it claims to help.
Cannot fix content-level issues
Missing alt text, poor heading structure, unlabeled form fields — these are content decisions that require human editorial judgment. The filet mignon example is the proof: automated content generation without oversight produces wrong results.
Automated detection misses 60%+ of real violations
According to Deque and TPGi industry research, automated accessibility tools — including those used by overlays — miss 60% or more of real WCAG violations. Manual audit by users relying on assistive technology is irreplaceable.
Cannot address keyboard traps and complex components
Custom interactive widgets, modal dialogs, date pickers and complex navigation patterns require code-level remediation. An overlay cannot inject the keyboard event handlers these components require to be accessible.
Creates a false sense of compliance
The most dangerous effect: businesses install an overlay, assume they are compliant, and stop pursuing real remediation. The delay directly increases legal exposure — as hundreds of US ADA lawsuits in recent years confirm (UsableNet reports 119 defendants with accessibility widgets sued in May 2025 alone).
US lawsuits filed against businesses with overlays installed
The FTC case is not an isolated data point. The US litigation landscape in 2024 and 2025 provides direct empirical evidence that overlays do not protect businesses from accessibility lawsuits.
Courts have consistently ruled that overlay installation does not constitute evidence of genuine WCAG compliance and does not provide a defense against ADA accessibility lawsuits. The pattern is unambiguous: an overlay does not reduce your litigation risk. In some cases — where the overlay interferes with users' AT and creates new barriers — it may increase it.
Other overlay vendors cited in industry reporting alongside accessiBe include UserWay, EqualWeb and AudioEye. All have faced ADA lawsuits from customers using their products. The accessiBe FTC action is the first major regulatory enforcement against an overlay vendor; it will not be the last.
Why this matters for European businesses under the EAA
The FTC action is a US regulatory action. But it has direct relevance for any EU business that has installed an overlay as a substitute for EAA compliance.
The European Accessibility Act requires genuine compliance with EN 301 549, which incorporates WCAG 2.1 Level AA. Compliance is not a checkbox or a widget installation — it is an audit, a remediation, and a documented process. European regulators have signaled the same position as the FTC:
France — DGCCRF
The French Direction générale de la concurrence, de la consommation et de la répression des fraudes is the competent authority for EAA enforcement against private operators in consumer-facing sectors (e-commerce, banking, telecommunications) under Loi 2023-171 and the Code de la consommation. ARCOM remains competent for the public sector and audiovisual services under Article 47 of Loi 2005-102.
Netherlands — ACM
The Dutch Authority for Consumers and Markets has signaled the same position: automated overlay tools are not a substitute for genuine WCAG remediation.
Italy — AgID
The Italian Agenzia per l'Italia Digitale has indicated that overlay tools do not constitute compliance with Italy's national transposition of the EAA.
A European business with an overlay installed is as exposed to EAA enforcement as one without. The only path to real compliance is source-code remediation, tested with real users relying on assistive technology, documented in an honest accessibility statement, and backed by a remediation roadmap with dates. That is not a widget. That is a process.
| Requirement | Accessibility overlay | Source-code remediation |
|---|---|---|
| Fixes underlying HTML/CSS/JS barriers | ✗ No | ✓ Yes |
| Works with users' existing assistive tech | ✗ Often interferes | ✓ Yes |
| Addresses content-level issues (alt text, headings) | ✗ Unreliably | ✓ Yes, with human review |
| Passes manual accessibility audit | ✗ No | ✓ Yes, when done correctly |
| Valid defense in EAA enforcement | ✗ No | ✓ Yes, if documented |
| FTC-compliant marketing claims | ✗ accessiBe case says no | ✓ Yes |
⚠️ Important notice: The FTC case details on this page are sourced directly from FTC.gov press releases of 3 January 2025 and 22 April 2025 (Decision and Order issued 21 April 2025, Docket C-4817). The EU regulator positions on overlays are based on sector reporting and not direct published regulator statements — labeled accordingly. This page is not legal advice. EAA-Report is a compliance reporting tool, not an overlay and not legal counsel.
Frequently asked questions
What is an accessibility overlay and why is it controversial?
What exactly did the FTC find about accessiBe?
Do overlays provide any legal defense if a business gets sued?
If overlays don't work, how does a business actually comply with the EAA?
Why is the filet mignon example cited by the FTC important?
Is an accessibility overlay better than nothing?
Official legal sources
- Directive (EU) 2019/882 — European Accessibility Act — full text
Get a real compliance report, not an overlay
EAA-Report is not an overlay. It is a structured legal compliance report with the exact WCAG 2.1 AA criteria that apply to your business, a documented remediation roadmap, and honest accessibility statement content. Auditable, not a widget.