Why Accessibility Overlays Don't Work (And Why Courts Agree)

The Promise Overlays Make

Accessibility overlay vendors sell a straightforward story: install a JavaScript widget on your website, pay a monthly fee (typically $49–$490/month), and your site becomes ADA compliant. No developer required. No code changes. Done in 20 minutes.

The pitch works because the alternative — actual accessibility remediation — sounds expensive, complicated, and slow. A demand letter arrives threatening a lawsuit. Panic sets in. The overlay is there, on the first page of Google results, promising instant compliance for the price of a business lunch.

Hundreds of thousands of businesses have bought it. The overlay market has grown to hundreds of millions of dollars in annual revenue.

The problem is that the core claim is false. Overlays don't make websites accessible. They can't — for reasons baked into what they actually are.

What Overlays Actually Do (And Why It Fails)

An accessibility overlay is a JavaScript file loaded on top of your existing webpage. At runtime — after your page has already rendered — the overlay script attempts to patch accessibility problems by modifying what's visible in the browser.

Specifically, overlays typically try to:

• Add alt text to images using AI (generating descriptions that are often generic or wrong)
• Adjust color contrast by overlaying a CSS filter on the page
• Add a toolbar that lets users toggle high contrast, larger text, or reading guides
• Attempt to repair keyboard navigation conflicts by injecting focus management scripts
• Modify ARIA attributes on certain elements

This sounds like it should work. It doesn't, for one fundamental reason: the tools that disabled users actually use don't interact with overlays at all.

Screen Readers Read the DOM, Not the Overlay

The vast majority of blind users navigate with screen readers — JAWS, NVDA, VoiceOver, TalkBack. These tools communicate directly with your page's HTML structure. They don't go through the overlay's visual layer. They don't use the toolbar.

When an overlay "fixes" an image by adding AI-generated alt text, it does so at the visual rendering level. The screen reader still reads the original HTML — which has no alt text. The fix never reaches the user who needed it.

When an overlay "fixes" color contrast by applying a CSS filter, it changes what a sighted user sees in the browser. It does nothing for the screen magnification tools that low-vision users actually rely on, which work below the browser's rendering layer.

The Toolbar Only Helps People Who Don't Need It

Overlay toolbars let users toggle accessibility features — bigger text, high contrast mode, simplified navigation. The population that uses these toggles is predominantly sighted users without assistive technology who want slightly different visual preferences.

Users with serious disabilities — the ones most likely to bring ADA claims — have already configured their devices and assistive technology to their needs. They don't need your overlay's toolbar. They need your underlying HTML to be correct.

Overlays Can Break Sites for Disabled Users

Screen reader users have deeply customized configurations built up over years. They trust their tools. Overlay scripts that inject focus management code, modify ARIA roles, or intercept keyboard events frequently conflict with how these tools work — creating new barriers that weren't there before.

The National Federation of the Blind, the largest organization of blind Americans, has formally condemned overlays. Their position: overlays are a product sold to businesses, not to disabled users. No disabled user asked for them, and many are actively harmed by them.

The Legal Record

The courts have seen enough overlay cases to have a clear position. The legal record is not ambiguous.

The FTC's $1 Million Fine (January 2025)

In January 2025, the Federal Trade Commission reached a settlement with the largest accessibility overlay company, imposing a $1 million fine for deceptive marketing practices. The FTC's finding: the company's claims that its product made websites "ADA compliant" and "WCAG certified" were false and misleading.

This isn't a fringe legal opinion. The federal consumer protection regulator reviewed the evidence and concluded that the company's core marketing claim — the one used to sell the product to hundreds of thousands of businesses — was a lie.

456 Overlay-Using Sites Sued in H1 2025

Accessibility lawsuits don't decline when you install an overlay. The data from the first half of 2025 shows 456 websites that had overlay products installed received ADA lawsuit filings. In many cases, plaintiffs' attorneys specifically identified the overlay in their complaints — arguing it demonstrated the defendant was aware of accessibility obligations but chose an inadequate solution.

The overlay became evidence of willful neglect, not good faith compliance effort.

Courts Rule Overlays Don't Satisfy WCAG

WCAG (Web Content Accessibility Guidelines) is the technical standard that courts use to evaluate whether a website is accessible. The assessment is done at the code level — does the HTML, the DOM, the underlying structure meet the guidelines?

Courts have consistently found that overlays don't satisfy this test. A JavaScript layer that attempts to patch a non-compliant page at runtime does not make the underlying page WCAG compliant. The overlay isn't part of the page — it's a bandage over a wound.

In case after case, defendants who argued "we had an overlay installed" received the same response: that doesn't constitute compliance. The underlying code must be correct.

The NFB's Formal Statement

The National Federation of the Blind has published a formal fact sheet on overlays. Key positions:

• Overlays do not make websites accessible to blind users
• Overlay toolbars frequently conflict with screen reader software
• Overlays have not been requested by the blind community and are not endorsed by it
• Businesses relying on overlays for ADA compliance are misinformed

When the largest organization representing your supposed beneficiaries formally condemns your product, the "this helps disabled users" claim is gone.

Why Overlays Can't Fix Code-Level Problems

The failure isn't a matter of overlay vendors not trying hard enough. It's structural. Accessibility is a code-level property. Overlays operate at the presentation layer. The gap between those two things cannot be bridged by JavaScript.

Accessibility Problem	What's Required to Fix It	Can an Overlay Fix It?
Missing alt text on images	Add descriptive alt attribute to <img> in HTML	✗ No — overlay alt text doesn't reach screen readers
Unlabeled form fields	Add <label> elements or aria-label attributes to inputs	✗ No — DOM must contain the label
Keyboard traps	Fix focus management in JavaScript; ensure tab order is logical	✗ No — overlay scripts often create new keyboard conflicts
Missing page language	Add lang="en" to <html> element	✗ No — requires HTML change
Color contrast failures	Change foreground/background color values in CSS	✗ No — CSS filter doesn't fix the underlying contrast ratio
Missing skip navigation	Add <a href="#main">Skip to main content</a> in HTML	✗ No — requires code change
Non-descriptive link text	Replace "click here" with descriptive text in HTML	✗ No — screen reader reads original link text

Every accessibility violation that drives ADA lawsuits is a code-level problem. The HTML is wrong, the ARIA attributes are missing, the keyboard behavior is broken. No runtime JavaScript script can retroactively fix what was wrong when the page was written.

What the Disability Community's Verdict Means

The WebAIM survey finding — 70% of screen reader users say overlays make sites harder — is damning not just as a data point but as a signal about what's happening structurally.

Overlays are fighting with the tools disabled users actually trust. A blind user who has spent months configuring NVDA to work exactly the way they need it to work does not want a JavaScript overlay injecting competing focus management code. They want clean HTML that their tool can navigate.

The overlay industry is built on a misunderstanding of how disabled users actually use the web. Most of them don't use browsers the same way sighted users do. They use custom tools, custom configurations, custom workflows. An overlay toolbar is solving for a problem the user doesn't have, while simultaneously creating new problems for tools they rely on.

What Actually Works

The solution to ADA compliance is the same as the solution to any technical debt problem: find the actual issues, prioritize them by impact, and fix the code.

Step 1: Find Your Actual Violations

Run an automated accessibility scan to identify the specific WCAG failures on your site. Most sites have 5–20 critical violations that represent the majority of their legal exposure. You need the specific list before you can fix anything. ADAflags scans your site free and returns violations ranked by lawsuit risk.

Step 2: Prioritize by Lawsuit Risk

Not all WCAG violations create equal legal exposure. Missing alt text on product images is higher risk than a minor color contrast failure on footer text. Fix the critical-path violations first — the ones that make your site completely unusable for specific categories of users.

Step 3: Fix the Code

Give your developer a specific list of WCAG violations with line numbers and references. Most critical violations — missing alt text, unlabeled form fields, keyboard navigation issues, poor color contrast — are fixable in one to three developer-days. This is not an enormous project. The scary part is knowing where to start. The actual fixes are usually small.

Step 4: Monitor Continuously

Code-level fixes break over time. New content, CMS updates, and feature additions introduce new violations regularly. Continuous monitoring catches regressions before they accumulate into the kind of violation list that attracts plaintiff attorneys.

Step 5: Publish an Accessibility Statement

A publicly available accessibility statement at /accessibility documents your commitment and the specific standards you're working to meet. It won't prevent a demand letter, but it demonstrates good faith and provides a stronger litigation position than "we installed an overlay."

If You Already Have an Overlay Installed

Remove it. The overlay is costing you money while providing no legal protection and likely degrading the experience for disabled users who visit your site.

The budget you're spending on an overlay — typically $490–$2,000/year — would cover a significant portion of real remediation. A developer-day of accessibility work is more valuable than 12 months of overlay subscription payments.

Before removing, take a screenshot and save the invoice — some attorneys have argued this demonstrates the business was at least aware of accessibility obligations, which can be useful context even though the overlay itself isn't a defense.

Then scan your site to find the actual violations, fix the highest-risk ones, and set up monitoring to catch regressions. That's the whole playbook.

Further Reading

• ADA Website Lawsuits in 2025: What Your Business Needs to Know →
• The Complete ADA Website Compliance Checklist for Small Businesses →
• Best AccessiBe Alternatives in 2025 (Comparison) →
• Top 9 UserWay Alternatives for SMBs (2025) →
• Top 9 AudioEye Alternatives for SMBs (2025) →
• Accessibility Overlay Widgets Are Making Things Worse →
• How to Run an ADA Compliance Check Step-by-Step →
• Top Industries With the Most ADA Violations in 2025 →
• DOJ Title II Deadline: Is Your Site Ready? →