Why Accessibility Overlays Don't Work

The pitch is close to irresistible: paste one line of JavaScript, get a compliance badge, make the legal exposure go away. If you've received a demand letter, someone on your team has already found the vendor.

It doesn't work. Here's the specific reasoning, so you can make the argument internally.

What an overlay can and can't reach

Overlay products generally do two things. They add a widget offering visual adjustments — bigger text, higher contrast, a different font. And they attempt automated repairs to the page after it loads, guessing at missing alt text and labels.

The first part is a settings panel. Browsers and operating systems already provide those controls, and people who need them are using tools they've configured over years. The second part is where the claim of compliance lives, and it's the part that fails.

Automated repair can only address a minority of WCAG success criteria — roughly the same subset an automated scanner can detect. Nothing that runs in a page's JavaScript can determine whether your alt text is meaningful, whether focus order preserves meaning, whether an error message explains how to fix the problem, whether a video has audio description, or whether your PDFs are tagged. Those aren't edge cases. They're the bulk of the standard.

The people it's built for mostly reject it

This is the part that tends to change minds internally, so it's worth stating plainly: screen reader users have repeatedly and publicly asked organizations not to use these products. Thousands of accessibility practitioners and disabled users have signed public statements opposing them.

The reason is practical, not ideological. Overlays interfere with the assistive technology people already use. A user with a finely tuned screen reader configuration lands on a page where a script starts rewriting the accessibility tree underneath them. The common outcome isn't improvement — it's a site that's harder to use than before, and a widget the user has to find a way to turn off.

It hasn't worked as a legal shield

Organizations using overlay products have continued to receive demand letters and be named in accessibility suits. There are documented cases where the overlay itself was part of the complaint.

That makes sense once you understand the mechanism. A plaintiff's tester doesn't evaluate whether you installed a product; they evaluate whether they could complete a task. If checkout doesn't work with a screen reader, it doesn't matter what's in your header.

There's a worse version, too: a compliance badge is a public claim. Claiming conformance you can't demonstrate is a weaker position than acknowledging you're mid-remediation with a dated plan.

What the money buys instead

Overlay subscriptions are usually priced per site, per year, indefinitely. Redirected into actual work, a comparable budget typically covers a real audit and a meaningful first phase of remediation — and remediation is permanent. A fixed component stays fixed. A subscription stops working the day you stop paying.

The one honest use

Visual adjustment widgets aren't inherently harmful when they're presented as what they are: a convenience feature, not a conformance measure. The harm comes from the compliance claim attached to them.

If someone on your team is advocating for one, the question to ask isn't whether it helps. It's what you'll be able to say if you're asked to demonstrate conformance — and whether "we installed a widget" is an answer you want on the record.