Accessibility Overlays: Are They Legally Safe?

What is an accessibility overlay?

An accessibility overlay is a JavaScript widget — loaded via a third-party script — that sits on top of an existing website and claims to make it more accessible. Most overlays present a small icon (a figure in a circle, or a wheelchair symbol) that opens a panel of controls: adjust font size, toggle high contrast, enable a “screen reader mode,” or apply dyslexia-friendly fonts.

Overlay vendors market their products as a simple, fast, low-cost path to WCAG compliance and ADA legal protection. The pitch is compelling: install one script tag, pay a monthly fee, and your accessibility problem is solved.

The evidence — from academic research, independent testing, user feedback, and the courts — tells a different story.

How overlays work (and why that creates problems)

Overlays operate by intercepting the rendered DOM after the browser has processed the page and applying JavaScript-driven modifications. Some use machine learning to attempt automatic remediation: inferring missing alt text from image file names, guessing at ARIA labels, attempting to reorder keyboard focus.

This approach has a fundamental architectural problem: it attempts to fix inaccessibility at the presentation layer without changing the underlying code. The original inaccessible HTML, CSS, and JavaScript remains. The overlay tries to paper over it at runtime.

The consequences are predictable:

Fixes applied by the overlay can conflict with how assistive technologies interpret the native DOM, producing worse outcomes than the unfixed page
Screen readers interact with the DOM directly — a layer applied on top of it may not affect what the screen reader actually reads
Keyboard navigation problems rooted in missing tabindex or broken focus management are not reliably corrected by JavaScript patches applied after render
Mobile assistive technologies (VoiceOver on iOS, TalkBack on Android) largely bypass overlay modifications
Overlay panels themselves frequently contain accessibility failures — modal dialogs that trap keyboard focus, buttons without accessible names, widgets that are themselves keyboard-inaccessible

What the research shows

Multiple independent studies have tested overlay claims against actual WCAG conformance:

The WebAIM Million (2023) found that home pages of websites using accessibility overlay products had significantly more detectable WCAG failures than those that did not. Overlays did not reduce the failure rate; they correlated with a higher one — likely because organizations relying on overlays as their primary compliance strategy are not doing the underlying remediation work.

AccessiBe and UserWay audits conducted by accessibility researchers have found that even after an overlay is enabled, pages continue to fail a significant proportion of WCAG 2.1 Level AA success criteria — including failures that the overlay specifically claims to address.

User testing with disabled participants conducted by researchers including Karl Groves and Adrian Roselli found that many users with disabilities actively disable or block overlay widgets, because the interventions make their experience worse rather than better. The overlay’s “screen reader mode” in particular is frequently cited as disruptive by screen reader users who have already configured their assistive technology to suit their needs.

The industry body that overlays claim to satisfy — the W3C — has not endorsed overlay technology as a path to WCAG conformance. The W3C’s guidance makes clear that conformance requires the underlying page to meet the success criteria, not a third-party modification layer applied over it.

What the courts say

The legal record on overlays is increasingly unfavorable to organizations that rely on them as their primary compliance strategy.

Lawsuits against overlay users

Organizations using overlay products have continued to face ADA Title III lawsuits. The overlay has not functioned as a legal shield.

Notable cases include:

Lainey Feingold and the NFB — the National Federation of the Blind has been explicit that overlay widgets do not constitute effective accessibility and that NFB does not consider them a reasonable substitute for actual remediation.

Multiple federal court filings — plaintiffs in ADA website accessibility cases have successfully argued that the presence of an overlay does not constitute compliance, because the underlying page continues to present barriers to users of specific assistive technologies. Courts have agreed. In several settlements, defendants using overlay products have been required to remove the overlay and undertake genuine remediation.

Robles v. Domino’s Pizza — though not an overlay case specifically, this landmark Ninth Circuit ruling established that the ADA applies to websites and that the technical standard expected is WCAG. Courts evaluating overlay effectiveness have applied this standard: does the site actually meet WCAG? The overlay is irrelevant if the underlying page does not.

The overlay-as-evidence problem

In some cases, the presence of an overlay has been used against defendants. The argument: by purchasing and installing an overlay, the organization acknowledged that the site had accessibility problems. The overlay’s failure to solve those problems therefore demonstrates continued knowing non-compliance — a more difficult position than an organization that had simply not yet addressed accessibility at all.

The Department of Justice’s accessibility settlements consistently require actual WCAG conformance, not the installation of compliance tools. None of the DOJ’s published settlements or voluntary compliance agreements have recognized overlay products as satisfying ADA obligations.

What overlay vendors claim vs. what they deliver

Overlay vendors make specific claims that are worth examining individually:

“Instant WCAG 2.1 compliance”

WCAG 2.1 conformance is a property of the page itself, not of a layer applied over it. A page that fails keyboard accessibility, has missing alt text, or lacks proper heading structure does not become WCAG-conformant because a widget has been installed. The W3C’s conformance model requires that the page meets each success criterion — not that a tool claims it does.

“Legally compliant”

Legal compliance under the ADA, PSBAR, EAA, or equivalent frameworks depends on whether a site actually presents barriers to users with disabilities. Courts and regulators assess this by testing the site as users experience it — often with actual assistive technology users. An overlay that does not reliably resolve barriers does not confer legal protection.

“Works with screen readers”

Screen readers interact with the accessibility tree derived from the DOM. An overlay applying JavaScript modifications after render may not be reflected in the accessibility tree that the screen reader reads. This is not a theoretical edge case — it is a common failure mode documented in user testing.

“Used by [large number] of websites”

Market penetration does not confer legal validity. The WebAIM research suggests scale has correlated with worse accessibility outcomes, not better.

“Free yourself from WCAG lawsuits”

No overlay vendor can legally guarantee freedom from lawsuits. The WCAG conformance that courts actually assess is conformance of the underlying page — something an overlay cannot create.

Why organizations buy overlays anyway

Understanding why overlays have found a market helps explain why the pitch is so effective even when the product is not.

Cost and speed. A genuine accessibility remediation program — audit, fix, retest, train, monitor — takes time and money. An overlay costs a few hundred dollars per year and installs in minutes. For organizations facing audit findings or legal pressure with a short timeline, the contrast is stark.

Plausible deniability. Some organizations purchase overlays not because they believe they work, but to create a paper trail. “We purchased an accessibility solution” is a better position than “we did nothing” — even if courts have largely rejected this argument.

Vendor sales tactics. Overlay vendors invest heavily in sales to web agencies, procurement teams, and compliance officers who may not have deep accessibility expertise. Claims of “ADA compliance” and “WCAG certification” are made confidently and are difficult for non-specialists to evaluate quickly.

Misunderstanding of the problem. Digital accessibility is technical, and many decision-makers do not fully understand why fixing the underlying code is necessary. The framing of overlays as a “tool” or “solution” implies equivalence with actual remediation.

What to do instead

If your organization is currently using an overlay and considering whether to continue, the framework is straightforward:

Audit your site independently. Commission an accessibility audit that tests the underlying page — not the overlay-modified version. This gives you an honest picture of your actual conformance. Many auditors will disable the overlay before testing.

Prioritize your most-used flows. The highest-risk barriers are those in core user journeys: login, checkout, account management, application forms, key navigation. These are what plaintiffs test and what regulators investigate. Fix these first.

Remediate the underlying code. The work is in the HTML, CSS, JavaScript, and content — not in a layer applied over them. This requires developer time and, ideally, accessibility expertise embedded in your team or engaged from outside.

Build monitoring into your workflow. Automated accessibility checks in your development pipeline catch regressions before they reach users. Our CI/CD accessibility integration makes this part of every build.

Train your team. Developers who understand WCAG write accessible code. Designers who understand accessibility design accessible interfaces. A one-day accessibility training session pays for itself many times over in avoided remediation costs.

Publish an honest accessibility statement. An accessibility statement that accurately describes your known issues and your remediation plans demonstrates good faith to regulators and to users. It also gives users a direct channel to report barriers before they escalate.

The overlay’s place in a real accessibility program

This is not an argument that overlay technology has zero place in any accessibility program. Some overlay features — user-controlled contrast preferences, font size adjustments, reduced motion — can be genuinely useful enhancements in addition to an accessible underlying site.

The problem is using an overlay instead of accessibility. That substitution does not work technically, it does not satisfy legal standards, and it fails the users the overlay claims to help.

Real accessibility is not a widget. It is a property of the code, content, and design of the site itself — built in, not bolted on.

If your organization is currently relying on an overlay for compliance, a free accessibility scan will show you the barriers that exist beneath it. Our accessibility consulting team can help you build a realistic remediation plan that addresses the underlying issues rather than papering over them.