The Overlay Trap: Sued After "Fixing" A11y

The pitch is irresistible. One line of JavaScript. Full WCAG compliance. ADA lawsuits, gone. Starting at a few bucks a month.

For a lot of companies, that pitch has been too good to pass up. And for a lot of those same companies, it has ended in legal fees, FTC investigations, and settlements that dwarfed what they would have spent fixing their websites properly.

I've been following the accessibility overlay industry closely, and what's happened over the past few years is a case study in how "compliance theater" backfires. Let me walk you through the record.

An Online Retailer Paid for the Solution, Then Got Sued Anyway

An online retailer installed one of the most heavily marketed accessibility overlay products on the market. The vendor promises to make sites accessible automatically, using AI. The retailer presumably breathed a sigh of relief and moved on.

Then came the lawsuit.

The plaintiff, a blind user relying on a screen reader, alleged the site was still inaccessible despite the overlay. This is not unusual. Disability rights advocates and researchers have documented repeatedly that overlays frequently interfere with screen readers rather than helping them. The JavaScript layer that's supposed to "fix" your site can actively break the assistive technology that users depend on.

Paying for the overlay didn't protect the retailer. It may have actually made things worse.

A Leading Vendor: A $1 Million FTC Settlement

If that retailer is a cautionary tale, the leading overlay vendor is the whole cautionary novel.

In 2024, the Federal Trade Commission reached a settlement with a leading overlay vendor requiring the company to pay $1 million and prohibiting it from making misleading accessibility claims. The FTC found that the vendor had been telling customers its product would make their sites fully WCAG compliant and legally protected, when the evidence showed it often didn't.

The FTC settlement documents are worth reading if you want to understand just how aggressive the marketing claims were. The company was essentially selling legal immunity. Customers bought that promise. The promise didn't hold up.

A Significant Share of ADA Lawsuits Cited Overlays as Barriers

Here's the data point that should make any business owner rethink the overlay strategy: according to industry reports, a significant share of ADA web accessibility lawsuits have specifically mentioned an overlay widget as a barrier to access.

Read that again. Products sold as lawsuit prevention were showing up in lawsuits as part of the problem.

This happens for a few reasons. Overlays often inject controls that keyboard users can't reach or dismiss. They sometimes trigger on page load in ways that trap screen reader focus. They can conflict with browser extensions that users already rely on. And their "AI fixes" frequently misidentify what needs fixing and apply the wrong remediation.

600+ Accessibility Professionals Signed a Statement

In 2021, over 600 accessibility practitioners, researchers, and advocates signed an open statement titled "Overlay Fact Sheet." The statement was blunt: overlays do not and cannot deliver on the promises made by vendors. It documented specific technical failures, explained why AI cannot automatically fix complex accessibility issues, and called on the industry to stop misleading customers.

The signatures came from blind users, screen reader developers, WCAG authors, and practitioners with decades of experience. This wasn't a fringe position. It was the accessibility community's professional consensus, documented and publicly available at overlayfactsheet.com (an independent community resource).

The vendors largely ignored it and kept running ads.

Why Overlays Fail Technically

The core problem is architectural. Accessibility isn't a layer you add on top of inaccessible HTML. It's a property of the HTML itself. A screen reader reads the DOM. If your DOM has an icon button with no label, an overlay can theoretically inject an aria-label after the page loads, but by then the screen reader may have already announced the button, and the injected label may conflict with what the user heard.

Real accessibility requires semantic HTML: proper heading hierarchy, meaningful link text, correctly associated form labels, focus management, keyboard navigation patterns. None of those things can be reliably retrofitted by an external script. They require access to the source code and a developer who understands WCAG at the implementation level.

What Actually Works

Testing. Auditing. Fixing the code.

This is less exciting than a one-line JavaScript solution, but it's what delivers actual compliance and, more importantly, a site that disabled users can actually use. The ADA doesn't require a specific technology. It requires equal access. An overlay that makes a site harder to use for screen reader users is the opposite of equal access, regardless of how many compliance badges the vendor puts on their landing page.

Start with an automated audit to find the low-hanging fruit. Tools like SCOUTb2 can surface contrast failures, missing alt text, unlabeled form fields, and other common violations in seconds. However, automated tools typically catch only an estimated 30-40% of WCAG issues. They are a useful starting point, not a substitute for proper remediation. For the remaining issues, you need human testing, ideally including users of assistive technology.

That process costs more than a monthly overlay subscription. It also doesn't end with your company in an FTC settlement. Proper remediation, combining automated scanning with expert manual testing and code fixes, is an investment in actual accessibility.

The overlay industry sold a dream: legal protection without engineering work. The dream has been tested in court, in regulatory proceedings, and in the lived experience of disabled users trying to navigate sites that were supposed to be fixed. The verdict, across all three venues, is pretty consistent.

It doesn't work.

If you're currently running an overlay and feeling protected, I'd genuinely encourage you to have a disabled user try to navigate your site with their actual assistive technology. What they experience will tell you more than any compliance badge.

Disclaimer: This article is for informational purposes only and does not constitute legal, professional, or compliance advice. SCOUTb2 is an automated scanning tool that helps identify common issues but does not guarantee full compliance with any standard or regulation.