Why Accessibility Overlays Got Sued (And What Actually Works)

The pitch was simple: install one line of JavaScript, and your website becomes ADA compliant. No code changes. No design overhaul. No expensive audit. Just a widget that fixes everything automatically.

Thousands of organizations bought it. Then many of them got sued anyway. Some got sued specifically because they had an overlay installed.

If you're using an accessibility overlay, or considering one, you need to understand what happened and why the legal landscape has shifted against these tools.

What Happened: The Overlay Promise and the Lawsuit Reality

Accessibility overlay companies emerged in the mid-2010s with a compelling value proposition. Their tools claimed to scan your website, detect accessibility barriers, and fix them in real time using JavaScript. Some charged as little as $50 per month. For organizations worried about ADA lawsuits but lacking the budget for a proper remediation, overlays seemed like a gift.

The problem is that they didn't work as promised. And the legal system noticed.

The Lawsuit Pattern

Starting around 2020, a clear pattern emerged in ADA web accessibility lawsuits. Plaintiff attorneys began filing cases against websites that used accessibility overlays, and winning. The presence of an overlay became less of a defense and more of a red flag.

The pattern looks like this: a plaintiff with a disability visits a website using assistive technology, encounters barriers that prevent them from completing a task (making a donation, finding information, signing up for a service), and files a complaint. When the defendant responds by pointing to their overlay widget, courts have consistently found that the overlay does not constitute compliance.

In some cases, plaintiff attorneys have specifically targeted organizations using overlays. The reasoning is straightforward. If you installed an overlay, you knew your site had accessibility problems. You just chose the cheapest possible response instead of actually fixing them.

Volume and Scale

Web accessibility lawsuits have increased dramatically year over year. In recent years, thousands of ADA-related digital accessibility lawsuits have been filed annually in federal courts, with additional actions in state courts. A significant and growing percentage of these target websites running overlay products.

The overlay companies promised to reduce your legal risk. The data suggests they may have increased it.

Why Overlays Fail Legally

Understanding why overlays don't hold up in court requires understanding what courts actually look at when evaluating web accessibility claims.

Courts Evaluate Actual Accessibility, Not Tools Installed

When a judge evaluates an ADA web accessibility claim, they don't ask, "Did you install an accessibility tool?" They ask, "Can a person with a disability actually use this website?"

An overlay sitting on top of inaccessible code is like putting a ramp sign next to a staircase. The sign acknowledges the problem. It doesn't solve it. Courts have been remarkably consistent on this point: what matters is the actual user experience, not the tools you've purchased.

Overlays Don't Fix Underlying Code

Here's the fundamental technical problem. Overlays work by adding a layer of JavaScript on top of your existing website. They attempt to modify the page in real time to address accessibility issues. But many critical accessibility problems live in the HTML structure, the content itself, and the design decisions that no amount of JavaScript can override.

Missing form labels, incorrect heading hierarchies, inaccessible custom components, keyboard traps, missing alternative text for complex images, and videos without captions are all problems that require changes to the actual source code and content. An overlay cannot write your alt text for you. It cannot restructure your navigation. It cannot make your custom JavaScript widgets keyboard accessible.

For a deeper look at the technical failures, our article on why accessibility overlays don't work covers the specifics.

The DOJ Has Not Endorsed Any Overlay

The Department of Justice, which enforces the ADA, has never endorsed any overlay product as a means of achieving compliance. In fact, the DOJ has intervened in cases to argue that automated tools alone are insufficient.

The DOJ's position has been consistent: compliance requires conformance with a recognized standard (specifically WCAG 2.1 Level AA), and that conformance must be verified through testing, not assumed based on a product installation.

This matters because organizations often install overlays based on the vendor's claim that the product "ensures ADA compliance." When that claim is tested in court, it doesn't hold up, and the DOJ's position reinforces why.

The National Federation of the Blind Position

The NFB, one of the largest organizations representing people who are blind, has taken a strong public position against accessibility overlays. Their members, who rely on screen readers daily, have consistently reported that overlays interfere with assistive technology rather than helping it.

The NFB has described overlays as products that make websites harder, not easier, for blind users to navigate. When the community you're claiming to help says your solution makes things worse, that's a problem no marketing budget can overcome.

The Shift: Why Overlays Became a Target

Something changed in the legal landscape around 2021 and 2022. Plaintiff attorneys stopped treating overlays as a neutral factor and started treating them as evidence.

Overlays as Evidence of Known Problems

The legal argument is elegant in its simplicity. If you installed an accessibility overlay, you were aware that your website had accessibility barriers. You chose to address those barriers with a tool that the disability community, accessibility professionals, and the DOJ have all said doesn't work.

That's not a good-faith effort. That's the minimum possible expenditure to create the appearance of compliance without achieving it. Courts have been receptive to this framing.

Targeting Overlay Users Specifically

Some plaintiff law firms have developed processes for identifying websites that use specific overlay products. The overlay code is detectable in a website's source code, making it possible to build lists of potential defendants.

This means that installing an overlay might actually make you more visible to potential plaintiffs, not less. The tool you installed to reduce your risk has become a searchable indicator of vulnerability.

The Class Action Dimension

Several lawsuits have named overlay companies alongside the websites using them. This development puts the overlay vendors themselves on the defensive and creates additional legal exposure for their customers. If you're contractually tied to an overlay vendor that's facing its own legal challenges, your organization inherits some of that uncertainty.

What Actually Works

If overlays don't work, what does? The answer isn't complicated, but it does require genuine effort. There is no shortcut to accessibility, just like there's no shortcut to building a safe building.

Build Accessibility Into Code

Accessibility starts at the code level. Semantic HTML, proper ARIA attributes, keyboard-navigable interfaces, and well-structured forms are the foundation. These aren't things you can bolt on after the fact. They need to be part of how your website is built from the start.

This is why choosing the right developer matters so much. A developer who understands WCAG 2.1 AA standards builds accessibility into every component, every page, and every interaction. It's not extra work when it's part of the process.

Build Accessibility Into Content

Code is only half the equation. Your content needs to be accessible too. That means descriptive alt text on every meaningful image, captions on every video, transcripts for audio content, clear link text (not "click here"), readable font sizes, and sufficient color contrast.

Content accessibility is an ongoing responsibility, not a one-time task. Every new blog post, every new page, every new image needs to meet the same standards.

Build Accessibility Into Design

Accessible design means choosing color palettes with contrast ratios that meet WCAG standards, creating focus indicators that are clearly visible, designing forms with associated labels, and building layouts that work at different zoom levels.

It also means testing with real assistive technology. Screen readers, keyboard-only navigation, voice control, and screen magnification all need to work with your design. If your design only works with a mouse, it doesn't work.

How to Protect Your Organization

Legal protection in the accessibility space comes from genuine effort, not from products. Here's a practical framework for reducing your risk.

Get an Audit

Start with a professional accessibility audit of your current website. This isn't a five-minute automated scan. It's a thorough manual review by someone who understands WCAG criteria, tests with assistive technology, and can identify the specific barriers on your site.

An audit gives you a prioritized list of issues to fix. It also creates documentation that shows you're taking accessibility seriously, which matters if you ever face a complaint.

Fix Real Issues

Take the audit results and fix the problems. Start with the most severe barriers: issues that prevent users from completing critical tasks like donating, finding contact information, or accessing key content.

You don't need to fix everything overnight. What you need is a documented plan and demonstrable progress. Courts have been much more favorable to organizations that can show they're actively working on accessibility than to those that installed an overlay and called it done.

Maintain an Accessibility Statement

Publish an accessibility statement on your website. This should describe your commitment to accessibility, the standards you're working toward (WCAG 2.1 AA), any known limitations, and how users can report barriers or request accommodations.

An accessibility statement isn't just a legal document. It's a signal to your community that you care about including everyone. It also provides a channel for feedback that lets you catch and fix problems before they become complaints.

Document Your Efforts

Keep records of everything: your audit results, your remediation plan, the fixes you've implemented, your testing results, and your ongoing maintenance activities. If a complaint ever arises, this documentation demonstrates good faith.

Good faith matters. ADA Title II compliance and broader accessibility law don't demand perfection. They demand genuine, ongoing effort to make your digital presence accessible to people with disabilities.

The Good-Faith Defense

You don't need a perfect website. You need a demonstrably improving one.

Courts have consistently distinguished between organizations that ignore accessibility entirely, organizations that install a cosmetic fix and call it done, and organizations that invest in genuine remediation and ongoing maintenance. The third group fares dramatically better in litigation.

A good-faith defense looks like this: you commissioned an audit, you fixed the most critical issues, you have a timeline for addressing the rest, you maintain an accessibility statement, you train your content editors on accessible practices, and you conduct periodic re-assessments.

This approach costs more than a $50 monthly overlay subscription. It also actually works. And "it actually works" is the only defense that holds up in court.

Where to Start

If you're currently using an overlay, don't just rip it out tomorrow. Start by getting an audit so you understand the real state of your site's accessibility. Then build a remediation plan with a realistic timeline. Then, once you've made meaningful progress on fixing the actual issues, remove the overlay.

If you're building a new website or planning a nonprofit website redesign, make accessibility a requirement from day one. It's easier, cheaper, and more effective to build it right than to fix it later.

The overlay era promised a shortcut. There isn't one. But the real path, building genuinely accessible websites, protects your organization better than any widget ever could.