Accessibility Overlays Don't Work: Here's What to Do Instead

The Promise Sounds Perfect

You've probably seen the pitch: add one line of JavaScript to your website and instantly become ADA compliant. No code changes. No redesign. No effort. Companies like accessiBe, UserWay, and AudioEye have raised hundreds of millions of dollars selling this promise.

There's just one problem: it doesn't work. And it might actually make things worse.

What Overlays Actually Do

Accessibility overlays are JavaScript widgets that sit on top of your website and attempt to modify the user experience in real time. They typically add a toolbar icon that lets users adjust font size, toggle high contrast, or enable a screen reader mode.

On the surface, this sounds helpful. In practice, here's what actually happens:

• They conflict with real assistive technology. Screen reader users already have their own software (JAWS, NVDA, VoiceOver) configured exactly how they need it. An overlay that tries to "help" often interferes with these tools, making the experience worse, not better.
• They can't fix structural problems. If your HTML has no heading hierarchy, broken form labels, or missing landmark regions, a JavaScript overlay can't rewrite your page structure in a meaningful way. It's painting over rust.
• They create new bugs. Overlays modify the DOM at runtime, which can break existing functionality, slow page loads, and introduce new accessibility issues that didn't exist before.
• They don't satisfy legal requirements. Courts have consistently ruled that overlays alone do not constitute compliance with the ADA. Several companies using major overlay products have been sued - and lost.

What the Disability Community Says

In 2024, over 700 accessibility professionals and disability advocates signed an open letter at overlayfactsheet.com calling for the industry to stop using accessibility overlays. The letter details specific technical failures and user harms caused by these products.

Blind users regularly report that overlay widgets make websites harder to use, not easier. Some have gone so far as to create browser extensions specifically to block overlay scripts from loading.

When your target users are actively trying to disable your accessibility solution, something has gone very wrong.

The Legal Reality

Over 1,000 ADA lawsuits have been filed against companies using accessibility overlays. Having an overlay installed on your site does not protect you from legal action. In some cases, plaintiffs have specifically cited the overlay as evidence that the defendant was aware of accessibility issues but chose a superficial fix instead of addressing the root causes.

The Department of Justice has also weighed in. In a 2022 statement, the DOJ affirmed that web accessibility obligations under the ADA exist and that automated tools alone cannot ensure compliance.

Why Overlays Are So Popular Despite All This

Three reasons:

1. They're easy. One script tag versus months of remediation work. Business owners want a quick fix, and overlays offer exactly that - even if the fix doesn't actually fix anything.
2. They're cheap (upfront). $500/year sounds better than $10,000+ for a proper audit and remediation. But that $500 doesn't protect you from the $50,000 lawsuit.
3. They're marketed aggressively. Overlay companies spend heavily on ads targeting the exact fear business owners have about ADA lawsuits. The sales pitch is designed to short-circuit critical thinking.

What Actually Works

Real accessibility isn't a product you install - it's a practice you adopt. Here's the approach that actually reduces your legal risk and serves your users:

1. Scan and identify issues

Use an automated scanner to find the violations on your site. This gives you a concrete list of what's broken and how severe each issue is. You can't fix what you don't know about.

2. Fix the critical issues first

Not all issues are equal. Missing alt text on a hero image matters more than a minor contrast issue in your footer copyright text. Prioritize by severity: critical and serious issues first, moderate and minor issues after. See our guide to the 5 issues most likely to trigger a lawsuit.

3. Use platform-specific guidance

If you're on WordPress, you fix issues differently than on Shopify or Squarespace. Generic advice like "add ARIA attributes" isn't helpful if you don't know where to find them in your CMS. We have specific guides for WordPress and Shopify.

4. Test with real assistive technology

After making fixes, test with a keyboard (tab through the site) and with VoiceOver (Mac) or NVDA (Windows). Five minutes of real testing catches issues that automated scanners miss.

5. Make it ongoing

Accessibility isn't a one-time project. Every new page, blog post, product listing, and content update can introduce new issues. Regular scanning catches regressions before they become legal exposure.

The Bottom Line

Accessibility overlays are a band-aid on a broken bone. They look like they're doing something, but they don't fix the underlying problems - and they can create new ones. Courts don't accept them as compliance. Users actively disable them. Accessibility experts unanimously oppose them.

The alternative isn't harder than you think. Most accessibility issues are fixable through your existing CMS without hiring a developer. It just takes knowing what's broken and following clear instructions to fix it. That's the approach that actually protects your business and serves every user who visits your site. Start with our WCAG guide for small businesses if you're new to this.