Do Accessibility Overlays Actually Work?
Accessibility overlays — the widgets sold by accessiBe, UserWay, AudioEye, and others — promise to make any website ADA compliant with a single line of JavaScript. It is a tempting pitch: instant, automatic, no developer required. The problem is that the accessibility community, screen-reader users, plaintiffs' attorneys, and even the Federal Trade Commission have all reached the same conclusion. They don't deliver what they promise.
What an Overlay Actually Does
An overlay is a script you paste into your site. When a page loads, it scans the DOM and tries to do two things: apply automated “fixes” at runtime (guessing at ARIA labels, adjusting some attributes) and show a floating toolbar where visitors can toggle settings like larger text, higher contrast, or a reading guide.
That toolbar is the key sleight of hand. It moves the burden of accessibility onto the disabled user — asking them to find a widget and configure your site themselves — rather than building the site to be accessible in the first place. People who rely on assistive technology already have it configured the way they need at the system level; a website-specific toolbar is, at best, redundant.
Why They Don't Deliver Compliance
- Automation can't catch most issues. Even the best automated tooling reliably detects only about 30–40% of WCAG success criteria. Whether alt text is meaningful, whether reading order makes sense, whether a custom component is truly operable — these need human judgment. An overlay that auto-“fixes” at runtime is guessing.
- Runtime patching is fragile. Overlays apply changes after your page renders, which can conflict with the assistive technology a user is already running. Many screen-reader users report that overlays make sites harder to use, not easier — to the point that some keep a browser extension installed specifically to disable them.
- The disability community opposes them. Hundreds of accessibility professionals and assistive-technology users have publicly urged businesses not to rely on overlays. When the people the law exists to protect are telling you a product doesn't help them, that is the answer.
The Legal Reality: Overlays Don't Stop Lawsuits
This is the part that surprises business owners most. Installing an overlay does not make you lawsuit-proof — and may do the opposite.
Thousands of ADA web accessibility lawsuits have been filed against sites that were actively runningan overlay at the time. Plaintiffs' firms know which widgets leave signatures in the code, and some specifically look for them. Courts have not accepted “we installed a widget” as a defense, because the underlying site is still inaccessible.
The regulators agree. In early 2025, the U.S. Federal Trade Commission finalized an order requiring overlay vendor accessiBe to pay $1 million over deceptive claims that its widget could make any website WCAG-compliant. When the FTC fines a vendor for saying its product does the exact thing you're buying it to do, that is worth pausing on.
What Actually Works Instead
Real accessibility is less glamorous than a one-line script, but it is the only thing that holds up — for users and in court. It comes down to three steps you repeat over time:
- Find the real issues. Scan your pages against WCAG 2.2 to get an honest inventory of what's broken and where. Start with our free WCAG checker or ADA compliance checker.
- Fix the actual code. Correct the alt text, contrast, labels, and keyboard handling in your templates — and pair automated scanning with manual review for the criteria machines can't judge.
- Monitor for regressions. Sites change. A deploy, a plugin update, or a new page can reintroduce barriers, so re-scan on a schedule and keep a documented record of your ongoing efforts — which is also your strongest evidence of good faith.
Why CompliaScan Takes the Opposite Approach
CompliaScan is deliberately not an overlay. We don't inject a widget or hide anything behind a toolbar. We find the real issues, show you the exact element and the specific fix, and re-check your site over time so problems don't creep back. The work happens in your code, where it counts — not in a layer that disappears the moment the script fails to load.
If you're currently weighing a widget, it's worth seeing the contrast directly. We compare approaches head-to-head with accessiBe, UserWay, and AudioEye. The pattern is consistent: overlays sell the feeling of compliance; real remediation delivers it.
See your lawsuit risk in 30 seconds
Over 5,100 ADA website lawsuits were filed in 2025 — a 20% year-over-year increase. Scan your site now and know exactly how exposed you are before a plaintiff's firm runs the same check.
Free scan · No signup required · Results in ~30 seconds
Keep reading
All articles →How Much Does a Website Accessibility Audit Cost in 2026?
Accessibility audit pricing breakdown: manual audits ($3,000–$30,000), VPATs, automated tools, and ongoing monitoring. What's actually required vs what's oversold.
WCAG 2.2 Explained: What Changed and Why It Matters
WCAG 2.2 introduced 9 new success criteria. Learn what changed from WCAG 2.1, which criteria are new, and how these updates affect your website compliance.
WCAG vs ADA: What's the Difference and Which Applies to You?
WCAG and ADA are related but different. Understand the key differences between WCAG technical standards and ADA legal requirements for your website.