This is a lie. And courts have confirmed it repeatedly.

Here's what overlays actually do, why they fail legally, and what actually fixes the problem.

What Is an Accessibility Overlay?

An overlay is a third-party JavaScript widget that injects a toolbar onto your website. Users can click it to increase font size, change contrast, or enable a "screen reader mode."

Companies like accessiBe, AudioEye, and UserWay sell these as compliance solutions. Their pitch: you don't need to touch your code. The overlay fixes everything automatically.

The accessibility community calls this snake oil. Courts are starting to agree.

Why Overlays Don't Work Technically

Overlays operate on top of your existing HTML. They don't change the underlying markup — they patch over it at render time using JavaScript. This creates three fundamental problems:

They can't fix what they can't read.

An overlay can't reliably detect the purpose of every element on your page. An unlabeled

used as a button looks identical to a decorative

to JavaScript running after page load. The overlay guesses — and guesses wrong constantly.

They break screen readers.

Screen readers parse the DOM directly. An overlay adds a second layer of JavaScript that conflicts with assistive technology. Multiple studies and screen reader user surveys have found that overlays make pages harder to use, not easier.

The National Federation of the Blind, Disability Rights Advocates, and hundreds of blind users have signed open letters against overlay products specifically because overlays interfere with their actual tools.

The widget itself is often inaccessible.

In a particularly ironic finding, accessiBe's own widget has been cited in accessibility audits as having keyboard navigation failures and focus management issues. The tool sold to fix accessibility problems has accessibility problems.

What Happened in Court

Eyebobs v. accessiBe (2022) Eyebobs used accessiBe on their website. They were still sued for ADA non-compliance. The overlay did not prevent the lawsuit and was not accepted as a compliance defense.

Murphy v. Eyeglass World The defendant argued their overlay constituted a good-faith compliance effort. The court rejected this argument — WCAG conformance requires actual code compliance, not a JavaScript patch applied after load.

FTC action (2024) The FTC fined accessiBe for deceptive marketing claims — specifically for claiming their product provided full ADA compliance when it demonstrably did not. This is the clearest official signal yet that overlay marketing is legally misleading.

Plaintiffs' law firms now specifically scan for overlay presence because it signals an inaccessible codebase underneath — and an easy target.

What the Numbers Say

We scanned 846 websites through WCAGsafe and found the most common violations across all sites:

58% fail color contrast 46.6% have non-descriptive link text 24.5% have images with no alt text 12.9% have unnamed buttons

Every single one of these is a code problem. An overlay cannot reliably detect and fix color contrast ratios applied via CSS variables, dynamically generated image tags with no alt attribute, or icon buttons rendered as SVGs with no accessible name.

The only fix is fixing the code.

What Actually Works

1. Alt text on every image

2. Accessible buttons

3. Color contrast

4. Form labels

5. Enable browser zoom

The irony is that the violations in most ADA demand letters — missing alt text, color contrast, unnamed buttons — take an afternoon to fix. The overlay companies have built a $300M industry on the fear that accessibility is too hard to do properly.

It isn't.

Where to Start

Run a free scan on your site at WCAGsafe. You'll get a full breakdown of violations, a legal risk score, and exact fix instructions — no account required, results in under 60 seconds.

Fix the violations the scan surfaces. That's it. No widget needed.

Originally published at wcagsafe.com/blog/accessibility-overlays-dont-work