Accessibility overlays get you sued too — here's the real fix
Overlay widgets promise "instant ADA compliance" in one line of JavaScript. They do not fix your website's code, and businesses that install them still receive ADA demand letters. Here is why, and what actually works.
Scan my site freeAn accessibility overlay is a marketing promise, not a legal shield. If you bought one to make a compliance problem go away, it is worth understanding what you actually got.
What an overlay actually is
Accessibility overlays — the category that includes products such as accessiBe, UserWay, and AudioEye — are JavaScript layers you paste onto your site. They add a floating accessibility button and try to patch some issues automatically in the browser after the page loads. They market themselves as automatic ADA and WCAG compliance.
The key point: an overlay sits on top of your website. It does not change the underlying HTML, templates, or components that a court or a screen reader actually evaluates. The barriers are still in your source code — the widget just tries to paper over some of them at runtime.
Why an overlay does not protect you
1. It does not remediate the source code
WCAG conformance is judged on the real content and code delivered to the user. A runtime script that guesses at fixes cannot reliably correct missing form labels, bad reading order, unlabeled controls, or inaccessible custom components. The defects remain in the code.
2. Assistive-technology users often turn them off
Overlays are widely criticized by the accessibility community and by screen-reader users. Many people who rely on assistive technology report that overlays interfere with the tools they already use — so they disable or ignore them. A fix that your intended users switch off is not a fix.
3. An overlay is not a legal defense
Businesses that installed overlays have still received ADA demand letters and been named in website-accessibility lawsuits. Plaintiffs test the actual experience with real assistive technology; the presence of a widget does not stop a claim. An overlay is not immunity, and it is not evidence of conformance.
The real fix: remediate, then prove it
The durable answer is the unglamorous one — fix the actual barriers in your code and keep a record that you did. That is what stands up to a screen-reader test and to scrutiny.
- Scan your live site against WCAG 2.1 / 2.2 AA and get an honest, criterion-level list of what fails.
- Fix the real code — the HTML, templates, components, and documents — so the barriers are actually gone, not hidden.
- Back it with a certified human who tests with a keyboard and a screen reader for the issues automation cannot catch.
- Keep a dated record of what you tested and fixed, so you can show a good-faith remediation effort.
Find your real gaps in 60 seconds
Free scan — a real WCAG 2.1 / 2.2 AA check with an honest risk score. No overlay, no signup.
Scan my site freeThis page describes the overlay category in general terms for information only. It is not legal advice and is not a statement about any specific product or company's compliance in any specific case. See Lawsuit Watch for who is filing website-accessibility claims.