Myth-busting
Do Accessibility Overlays Actually Work?
A one-line script that makes you “instantly compliant” sounds great. The FTC, the courts, and screen-reader users all disagree. Here’s the honest breakdown.
An accessibility overlay is a single line of JavaScript a vendor tells you to paste into your site, promising it will make you “ADA compliant” or “WCAG compliant” automatically. The pitch is irresistible: instant compliance, no developers, a reassuring badge in the corner. The reality is that overlays don’t fix your code, don’t satisfy the law, and in 2025 earned the category’s biggest player a $1 million FTC fine. Here’s the honest breakdown.
What an accessibility overlay actually is
An overlay is client-side JavaScript that loads on top of your existing site and tries to detect and patch accessibility problems in the browser at runtime — auto-generating alt text, adjusting contrast, adding ARIA attributes, and offering a widget with toggles (bigger text, dyslexia font, etc.). Crucially, your underlying HTML and CSS are unchanged. The overlay is a layer, not a fix.
What they promise vs. what they do
| The promise | The reality |
|---|---|
| “Instantly ADA/WCAG compliant” | No automated tool can achieve compliance; 50–70% of WCAG needs human judgment. |
| “AI fixes your accessibility” | Auto-generated alt text is frequently wrong or meaningless; auto-ARIA often makes screen-reader output worse. |
| “Protects you from lawsuits” | Sites running overlays are sued routinely — the widget itself is now a target. |
| “Accessibility, solved” | The toggle widget shifts the burden onto disabled users to fix your site themselves. |
The FTC vs. accessiBe
In 2025 the U.S. Federal Trade Commission ordered accessiBe — the most prominent overlay vendor — to pay $1 million over deceptive claims that its accessWidget product could make any website fully compliant with WCAG. The FTC also took issue with undisclosed paid reviews. The significance isn’t just one company: it’s a federal regulator stating plainly that “install our widget and you’re compliant” is a false claim.
The lesson regulators drew
You cannot buy your way out of accessibility with a script. Compliance comes from accessible source code plus documented, ongoing testing — the exact opposite of a one-line install.
Why overlays fail technically
- They can’t understand context. Meaningful alt text requires knowing what an image communicates on this page. A machine guessing “image” or mislabeling a product photo helps no one. (See how to write alt text.)
- They often conflict with real assistive tech. Screen-reader and overlay users have widely reported that overlays interfere with the tools they already use, sometimes making sites harder to navigate.
- They don’t touch the source. Broken heading structure, keyboard traps, and unlabeled forms live in your code. A runtime patch can’t reliably rewrite your application’s DOM and behavior.
- EU enforcers reject them outright. The European Accessibility Act requires accessible code, not a band-aid.
Overlays attract lawsuits
Far from preventing litigation, overlays have become a signal. Plaintiff firms specifically file against sites running well-known overlay scripts, because the gap between the marketing claim and the lived experience is easy to demonstrate. Hundreds of suits have named overlay-equipped sites. The badge you paid for can become Exhibit A.
What to do instead
- Audit your real code. Run an automated scan, then test with a keyboard and a screen reader.
- Fix the source. Proper semantics, real alt text, labeled forms, sufficient contrast, full keyboard support.
- Monitor continuously so regressions are caught on the next release, not by a plaintiff.
- Document everything. A dated audit trail is the defense an overlay badge can never be.
That’s the entire reason avp.io exists — honest auditing and monitoring instead of a widget that papers over the problem.