Do accessibility overlays actually work? (What the FTC said, and what to do instead)
Short answer: no — an accessibility overlay does not make your website compliant, and treating it as if it does is now a documented legal risk. In April 2025 the US Federal Trade Commission finalised a $1,000,000 order against accessiBe, one of the best-known overlay vendors, for claiming its widget could make any website WCAG-compliant. Overlays are a script you paste in; they run in the browser after your page loads, never touch your source code, and can't fix the things a real audit finds. This guide explains why, and what to do instead.
What an accessibility overlay is
An overlay (also called an accessibility widget or plugin) is a snippet of third-party JavaScript you add to your site. It typically adds a floating button that opens a menu of toggles — bigger text, higher contrast, “screen-reader mode” — and its vendor usually promises automatic, ongoing compliance with standards like WCAG, the ADA, or the European Accessibility Act.
The pitch is seductive: one line of code, and you're compliant. The problem is that isn't how accessibility, or the law, works.
Why overlays don't deliver compliance
Four reasons, and they're true of any client-side overlay by construction — not gossip about one vendor:
1. Your code stays broken
An overlay runs after your page loads. It never edits your source. The markup your developers maintain — and that every screen reader, crawler, and integration actually reads — is exactly as broken as before. You've added a layer, not fixed the foundation.
2. It has to guess at meaning
Good alt text says what an image means in context — whether it's decorative or the only place a price appears. That's a human judgment about intent. A script that never saw your intent fills the gap with a plausible-sounding guess, which is often wrong in ways that mislead the people relying on it.
3. It can fight the tools people already use
People who use assistive technology already have it configured the way they need. An overlay that reaches in at runtime and reassigns roles, focus, and labels can conflict with that setup — sometimes making a site harder to use, not easier. This is why many disabled users and advocates actively ask sites to remove overlays.
4. It isn't evidence
When someone asks what you've done about accessibility, the answer that holds up is a record: what was wrong, what you changed, and when. A widget in your footer isn't remediation — it's evidence you bought a widget.
The legal reality (with the qualifiers intact)
- The FTC fined accessiBe $1,000,000 (final order, April 2025) for deceptive claims that its automated tool could make any site WCAG-compliant, and for failing to disclose paid reviews. This is the clearest official signal yet that “install an overlay = compliant” is a claim regulators will act on.
- US ADA website lawsuits remain common — 4,000+ were filed in 2024 (full year). Notably, many suits have named businesses that had an overlay installed: the widget didn't prevent the claim.
- The European Accessibility Act has been in force since 28 June 2025. As of mid-2026 no monetary fines have been confirmed under the transposed national laws yet, and enforcement so far has centred on formal notices, civil-society action, and (in Germany) private warning letters. The deadline has passed — which makes now the low-cost time to fix real issues, before enforcement matures.
Curbcut is not a law firm and does not provide legal advice; the above are verified facts with sources, not a legal opinion on your specific situation.
What to do instead
Fix the real thing. It's less magical and more durable:
- Scan your site against WCAG 2.1/2.2 AA to find what's actually broken, where, and why it matters.
- Fix it in your code — the exact element, the rule it breaks, the plain-English change. These fixes help everyone (the “curb-cut effect”), not just users of one widget.
- Keep a record — a report and a remediation history are the evidence that actually holds up.
- Monitor so regressions get caught, not rediscovered by a complainant.
| Accessibility overlay | Fixing the code (e.g. with Curbcut) | |
|---|---|---|
| Touches your source | No | Yes |
| Creates real compliance | No | Moves you toward it, genuinely |
| Produces evidence of remediation | No | Yes — report + history |
| Works with users' own assistive tech | Often conflicts | Yes |
| Regulator's view | FTC fined a leading vendor $1M | The standard, expected approach |
Curbcut will never ship an overlay — not in a later version, not as an upsell. We find the real issues in plain English and hand them to whoever fixes your code.
Run a free scan →
FAQ
- Are accessibility overlays legal?
- Using one is not illegal, but relying on one for compliance is risky: the FTC fined accessiBe $1M in 2025 over its compliance claims, and overlays have not stopped ADA website lawsuits against businesses that had them installed.
- Does an overlay make my site ADA or EAA compliant?
- No. Compliance comes from your site actually meeting WCAG in its code. An overlay runs on top of unchanged code and cannot guarantee that.
- What's a good accessiBe alternative?
- Anything that finds and helps you fix the real issues rather than masking them. Curbcut scans your site against WCAG 2.1/2.2 AA and gives you a prioritised, plain-English fix list — free to start, no overlay.
- Should I remove my overlay?
- Talk to your developer, but at minimum stop treating it as your compliance solution. Run a real scan to see where you actually stand.
Sources: FTC press release on the accessiBe final order (April 2025); ADA Title III website-lawsuit filing trackers (2024); Directive (EU) 2019/882 (EAA) and 2026 enforcement analyses.