Accessibility overlay

An accessibility overlay is a third-party JavaScript widget that injects itself into a host site and claims to make the site WCAG-compliant automatically. Overlays typically present as a small floating “person” icon in a corner of the page; clicking it opens a sidebar with profile presets (high contrast, larger text, dyslexia-friendly font, screen-reader mode, and so on).

The overlay industry includes vendors like accessiBe, UserWay, EqualWeb, AudioEye, and others. They market themselves to businesses worried about ADA lawsuits as a one-line-of-code compliance solution.

What the evidence says

A consistent finding across independent technical audits — by accessibility consultancies, academic researchers, and disabled-user testers — is that overlays:

• Do not deliver WCAG compliance. Automated tooling can detect at most 30–40 % of WCAG issues. Overlay vendors’ own marketing claims to “fix” or “comply” routinely exceed what their tooling can do.
• Override hand-written accessibility work. A common failure mode: the host site has hand-written alt text for an image; the overlay’s AI generates new alt text and replaces it. The hand-written context-aware version is gone; the generic AI version stays.
• Add new bugs. Overlays inject thousands of lines of JavaScript, ARIA attributes, and DOM modifications. These frequently conflict with the host site’s own structure — breaking landmarks, hijacking focus, inserting unannounced live regions.
• Break with screen readers. The disability community has consistently asked overlay vendors to stop labelling their products as “screen-reader compatible” because they routinely make screen-reader use worse, not better.

The most-cited consolidated reference is the Overlay Fact Sheet (overlayfactsheet.com), signed by hundreds of accessibility practitioners. It has been updated since 2020 as new evidence accumulates.

The litigation record

Despite overlay marketing claims that their products reduce legal exposure, the empirical pattern in US federal court is the opposite:

• More than 1,000 companies using overlay tools were sued under ADA Title III in 2024.
• Settlement records in those cases frequently require the defendant to remove the overlay as part of the remediation.
• A handful of cases have named the overlay vendor directly, alleging fraud or false advertising; those are ongoing.

For procurement and risk teams the practical posture is clear: an overlay is not a defence. Courts and plaintiffs treat the underlying site’s accessibility as the operative fact, regardless of any overlay running on top.

What actually works

There is no one-line shortcut. The work that does deliver accessibility:

1. Audit the underlying site against WCAG 2.x AA with credentialed reviewers and real assistive-technology testing.
2. Fix the underlying issues at the HTML/CSS/JS layer where they live.
3. Maintain — design and engineering reviews on every new feature, automated CI checks, periodic external audits.

Money spent on an overlay subscription is, in every documented case the accessibility community has examined, money that would have been better spent on the audit-and-fix loop.