Why Accessibility Overlays Don't Work: The Coverage Data

A single line of JavaScript, the ads promise, and your site is ADA-compliant by morning. The pitch is everywhere — accessiBe, UserWay, AudioEye — and it is the reason a lot of site owners meet accessibility for the first time through a sales page rather than through a standard.

The evidence does not support the promise. Overlays are third-party scripts that sit on top of your site and try to detect and repair accessibility barriers at runtime, usually adding a small toolbar that adjusts font size, contrast, or spacing. Independent analyses put their realistic coverage at 10-16% of WCAG 2.1 AA success criteria. In research by UsableNet, 22.6% of federal ADA web lawsuits targeted sites that already had an overlay installed. And accessiBe agreed to pay $1 million to settle Federal Trade Commission charges that it misrepresented what its product could do. Here is the evidence in detail, and what to do instead.

What Overlays Promise

The marketing pitch is compelling. Drop a script tag into your site header, and the overlay will automatically scan your pages, identify issues, and fix them using AI. Vendors claim their products achieve full WCAG 2.1 AA compliance, protect you from lawsuits, and save you the cost of hiring accessibility specialists.

For a busy site owner, this sounds like a dream. No code changes. No audits. No ongoing maintenance. Just a monthly subscription and a badge that says “accessible.”

What Overlays Actually Deliver

The reality does not match the sales deck. Independent research consistently shows that overlay widgets fail to deliver meaningful accessibility improvements. Here is what the data tells us.

Overlays address only 10-16% of WCAG criteria

The Web Content Accessibility Guidelines (WCAG) 2.1 AA standard contains 50 success criteria. Overlays, by their nature as client-side JavaScript add-ons, can only attempt to address issues that are detectable and fixable in the browser at runtime. Multiple analyses have found that overlays can realistically address somewhere between 10% and 16% of WCAG success criteria. The remaining 84-90% require changes to source code, content structure, design decisions, and information architecture that no overlay can touch.

That is not a rounding error. That is a product that misses the vast majority of what it claims to fix.

700+ accessibility professionals signed the Overlay Fact Sheet

The Overlay Fact Sheet is a joint statement from over 700 accessibility practitioners, developers, disability advocates, and researchers. It documents the technical shortcomings of overlay products and explicitly recommends against their use. When the people who spend their careers making the web accessible overwhelmingly agree that a product does not work, that consensus is worth paying attention to.

22.6% of ADA lawsuits target sites using overlays

Overlays are marketed as lawsuit shields, but the numbers tell a different story. Research by UsableNet found that 22.6% of accessibility-related lawsuits filed in federal court targeted websites that had an overlay installed at the time. Installing an overlay does not make you less likely to be sued. In some cases, it may make you more likely to be sued, because plaintiffs’ attorneys have learned that the presence of an overlay signals a site with known, unfixed issues. If a letter has already arrived, what to do when an overlay did not stop the demand letter walks through the response.

accessiBe paid $1 million to settle FTC charges

accessiBe agreed to a Federal Trade Commission order requiring it to pay $1 million to settle charges that it made deceptive claims about its product’s effectiveness. When a federal regulator takes action against an accessibility vendor for overpromising, it is worth a buyer’s pause. (Nothing here is legal advice.)

Why Overlays Fail: The Technical Reality

Understanding why overlays cannot work requires a basic grasp of how they operate and where the limitations lie.

They depend entirely on JavaScript

Overlays are JavaScript widgets. If JavaScript fails to load, loads slowly, or is blocked by a browser extension, the overlay does nothing. Assistive technology users are more likely than average to use configurations where JavaScript behaves unpredictably. Building your accessibility strategy on a foundation that can silently disappear is not a strategy at all.

They cannot fix source code

Most accessibility barriers live in the HTML, the structure of your content, your navigation patterns, and your design choices. An image without alt text needs a human to write a meaningful description. A form without proper labels needs its markup restructured. A color contrast failure needs a design change. Overlays can attempt to guess at fixes, but guessing at what an image contains or what a form field means produces results that range from unhelpful to actively misleading.

Consider a chart image on a financial services site. An overlay might label it “image” or attempt an AI-generated description. Neither gives a screen reader user the actual data they need. Only a human who understands the content can provide that.

They interfere with assistive technology

This is perhaps the most damaging problem. Many screen reader and voice control users report that overlays actively break their browsing experience. The overlay toolbar can trap keyboard focus, inject unexpected announcements, override user preferences, and conflict with the assistive technology’s own interpretation of the page. Multiple users have documented having to specifically block overlay scripts just to use websites that were partially accessible before the overlay was installed.

When a product marketed as an accessibility solution makes the experience worse for the people it claims to help, something has gone fundamentally wrong.

They create a false sense of security

Organizations that install overlays often stop there. The overlay becomes the entire accessibility program. This means real issues — broken keyboard navigation, missing document structure, inaccessible custom components — go unaddressed because the overlay badge suggests everything is fine. The result is a site that is both inaccessible and believed to be accessible, which is arguably worse than a site whose owners know it needs work.

What to Do Instead

If overlays are not the answer, what is? Genuine accessibility requires more effort than a single script tag, but the path forward is well-established and more straightforward than vendors want you to believe.

1. Run an automated audit as a starting point

Tools like axe-core, WAVE, and Lighthouse can scan your pages and identify a significant portion of detectable issues. These tools do not fix problems for you, but they give you a concrete list of what needs attention. Use them as a starting point, not an endpoint. Automated tools catch roughly 30-40% of accessibility issues, which is already more useful than what overlays attempt to repair — but a high score is not a clean bill of health, as a Lighthouse 95 that still got sued shows.

2. Fix issues in your actual code

There is no substitute for fixing your HTML, CSS, and JavaScript at the source. Add alt text to images. Use semantic HTML elements. Ensure proper heading hierarchy. Label your form fields. Make interactive elements keyboard-accessible. These are concrete, well-documented changes that produce permanent improvements. If you use a CMS like WordPress, many of these fixes can be applied through theme and plugin updates.

3. Test with real assistive technology

Install NVDA (free on Windows) or use VoiceOver (built into macOS and iOS). Navigate your site using only a keyboard. These tests will reveal issues that no automated tool catches. You do not need to become an expert screen reader user. Even 15 minutes of testing will surface problems you did not know existed.

4. Prioritize and iterate

You do not need to fix everything at once. Start with your highest-traffic pages and your most critical user flows — checkout, signup, contact forms. Fix the biggest barriers first and work through the rest over time. A steady, genuine effort to improve will always outperform a one-time overlay installation, both in actual accessibility and in legal defensibility.

A Better Way Forward

Our accessibility report takes the opposite approach from an overlay. Instead of papering over problems at runtime, it scans your pages, identifies the specific WCAG failures, and gives you the exact code change for each one. No badge. No script tag that has to keep running for your site to stay usable. Just a clear list of what is broken and how to repair it.

The work itself is not exotic. If you would rather scope it before you spend anything, what website accessibility actually costs breaks down the realistic ranges, and how to hire an accessibility consultant covers what to ask before you sign.

Accessibility is not a widget you install. It is a practice you adopt. The sooner organizations stop looking for shortcuts and start doing the real work, the better the web gets for everyone.

Want to know what is actually broken on your site? Get an accessibility report.