Why Accessibility Overlays Are Not Compliance.

What an Overlay Actually Is

An accessibility overlay is a JavaScript bundle, typically loaded from a third-party CDN, that runs on every page of your site after the HTML has finished rendering. The script analyzes the DOM at runtime, attempts to detect accessibility issues, and tries to patch them with JavaScript: injecting ARIA attributes, modifying focus order, adding alt text generated from filenames, and presenting a sidebar widget that lets users adjust contrast, text size, and animation settings.

The pitch is seductive: install one line of code, achieve WCAG compliance. The reality is that none of those runtime modifications change the underlying HTML. They exist only as long as the JavaScript runs, only in the browsers it supports, and only for the visitors whose accessibility tools recognize them — which is far fewer than overlay vendors imply.

Why Screen Readers Don't Cooperate

Modern screen readers like JAWS, NVDA, and VoiceOver are built to consume the HTML document, not a runtime-modified version of it. They read the page source the browser receives. By the time a JavaScript overlay finishes its DOM manipulation, many screen reader users have already received and processed the original, unaltered page.

Even worse, overlays sometimes override settings the user has already configured in their assistive technology — turning off the very accommodations the user spent years tuning. The National Federation of the Blind passed a 2021 resolution formally opposing overlays on these grounds, calling them "ineffective, deceptive, and a threat to the rights of blind people."

The accessiBe Litigation

accessiBe is the largest overlay vendor and has become the de facto target for the broader anti-overlay movement. In Murphy v. Eyebobs (2021), the plaintiff sued a retailer that had installed accessiBe and argued that the overlay had failed to make the site accessible. The case settled, but the legal theory it advanced — that overlay installation can be evidence of awareness without compliance — has been adopted by plaintiff attorneys across the country.

Industry data tracked by accessibility law firm Levenfeld Pearlstein found accessiBe specifically named in 258 ADA web accessibility cases in 2024. That is not a random sample of all sites; it is a disproportionate concentration of suits on sites that thought they were protected.

The FTC Settlement

In January 2025, the U.S. Federal Trade Commission ordered accessiBe to pay $1 million for making deceptive claims that its AI product could make websites ADA compliant. The order is significant for two reasons. First, it is a federal regulator — not a plaintiff's attorney with an obvious financial interest — explicitly finding that the marketing claims around overlay products misrepresent what they do. Second, the order is now part of the public record any defense counsel can cite when an overlay-installed site is sued: the vendor itself has been federally enforced against for the very claims that led the buyer to install the product.

The practical reading: when a site that installed an overlay because of vendor compliance claims is later named in an ADA lawsuit, the FTC order is now Exhibit A for why the overlay was never the protection it was sold as.

The 22.6% Statistic

The most striking number in the current data: in the first half of 2025, 22.6% of all U.S. ADA web accessibility lawsuits were filed against sites with overlay widgets installed. That is roughly one in four lawsuits hitting a site that had paid for what was marketed as legal protection.

There are two explanations, and both are bad for overlay buyers. Either overlay sites are no more or less likely to be sued than non-overlay sites (which means the overlay provides no protection), or overlay sites are more likely to be sued because plaintiff attorneys specifically target them as easy wins (which means the overlay is worse than nothing).

The 2024 DOJ Title II Rule

In April 2024, the U.S. Department of Justice finalized its Title II web accessibility rule, requiring state and local government websites and mobile apps to conform to WCAG 2.1 Level AA. While the rule technically applies to public entities, its definition of conformance — and the explicit absence of any "overlay safe harbor" — has been read by plaintiff firms as a signal that DOJ views runtime JavaScript modifications as insufficient.

On April 20, 2026, DOJ issued an interim final rule extending the Title II compliance dates by one year: entities serving populations of 50,000 or more now have until April 26, 2027, and smaller entities and special district governments until April 26, 2028. The extension moved the dates. It did not change the technical standard, and it does not apply to private businesses, which were never covered by this rule in the first place.

The rule does not say "installing a widget counts as conformance." It says the underlying site must meet the technical standard. That is a legal posture that aligns naturally with code-level remediation and naturally against overlay vendors.

The Rise of AI-Generated Demand Letters

A newer dynamic worth understanding: self-represented plaintiffs filed roughly 40% more federal ADA cases in 2025 than in 2024 — a surge Seyfarth Shaw attributes largely to AI-assisted drafting. Many of these plaintiffs use AI-powered scanners to identify potentially non-compliant sites and generate filings at scale. These scanners look at the actual HTML the browser receives, not the runtime-modified DOM. An overlay does nothing to defeat an AI scanner, which means the very lawsuits driving the explosion in case volume are largely immune to overlay protection.

What "Real Compliance" Actually Looks Like

The defensible posture in 2026 has three components:

1. Source-level remediation. The HTML the browser receives must already meet WCAG 2.1 AA requirements. Skip-nav links, ARIA landmarks, image alt attributes, form labels, lang declarations, autocomplete attributes — all baked into the served HTML, not added at runtime.
2. Continuous scanning and remediation. Compliance is not a one-time project. Content changes, new pages get published, themes get updated. Scheduled scans catch regressions before plaintiffs do.
3. Documented audit trail. A VPAT, a remediation report, a scan history, an accessibility statement, and a remediation log. Courts evaluating ADA cases look for evidence of good-faith effort — documentation is how that effort gets proven.

This is the posture our platform was built to provide. Not because we are anti-overlay as a marketing position, but because the architecture of source-level remediation is the only architecture that survives legal scrutiny in 2026.

What to Do If You Already Have an Overlay

If you have an overlay installed today, the right move is not to panic and not to leave it in place. The middle path:

1. Run a free scan of your site to establish a baseline.
2. Install real code-level remediation alongside the overlay so the underlying HTML actually conforms.
3. Once the source-level fixes are stable, remove the overlay. Keep the preference widget if your users like it — but disclose explicitly (as we do) that the widget is an enhancement, not the compliance mechanism.
4. Generate the VPAT and accessibility statement. Make the documentation public. The paper trail is what evidences the work.