Accessibility overlays are third-party widgets — sold by vendors such as accessiBe, UserWay, AudioEye, and EqualWeb — that promise to make your website ADA compliant by adding a single line of JavaScript. The pitch is irresistible: instant compliance, no developers, no rebuild. The reality is that overlays do not fix the code that makes a site inaccessible, courts have not treated them as a defense, and many people with disabilities find they make browsing worse.

This hub explains, honestly and with sources, what overlays are, why they fall short, and what protects your business instead. Curbcut is deliberately anti-overlay — we do the manual remediation overlays only simulate.

What an overlay actually does

An overlay loads after your page and tries to detect and patch accessibility issues automatically — adjusting some attributes, offering a toolbar to change contrast or text size, and reporting a compliance “score.” Two problems sit underneath the marketing:

  1. It’s automated, and automation has a ceiling. Industry testing consistently finds automated tools catch only about 30–40% of WCAG issues. The barriers that block real users — an unlabeled custom control, a checkout that traps keyboard focus, a meaningless link — almost always need human judgment to fix. An overlay can’t supply it.
  2. It doesn’t change your real code. The inaccessible markup is still there; the overlay just paints over it at runtime. Turn the widget off and every barrier returns, because nothing was actually remediated.

An overlay is a script that describes accessibility work without doing it. That gap is exactly what a plaintiff’s tester walks into.

Read the honest breakdown

Each guide below goes deeper on one part of the overlay question.

Do accessibility overlays actually work?

The headline question, answered with the evidence: what overlays can and can’t do, the vendor claims versus independent testing, and FTC scrutiny of “compliant” marketing.

Do accessibility overlays actually work? →

Why overlays don’t work

The mechanics of failure — why a runtime script can’t resolve structural barriers, why screen-reader users disable overlays, and why the Overlay Fact Sheet signed by hundreds of accessibility professionals recommends against them.

Why overlays don’t work →

Overlay vs. manual remediation

A side-by-side comparison: cost, durability, legal defensibility, user experience, and maintenance. What you’re really buying with each, and why “cheap and instant” turns out to be the expensive option.

Overlay vs. manual remediation →

accessiBe, UserWay & AudioEye alternatives

If you’re on one of the big overlay products and want a path that actually holds up, this covers what to do instead — and how to unwind an overlay without losing ground.

accessiBe, UserWay & AudioEye alternatives →

Overlays and lawsuits: the part vendors don’t lead with

The strongest argument against overlays isn’t theoretical — it’s the docket. Businesses running overlays have been named in thousands of ADA web accessibility cases, and plaintiffs now routinely point to an installed overlay as proof the site still failed real users. Courts have not accepted overlays as a safe harbor, and the FTC has acted against deceptive “compliance” claims. If you’ve already received a demand letter, installing an overlay is one of the worst moves available: it doesn’t fix the cited barriers and can complicate your position.

What protects you instead

Real, durable compliance comes from fixing the actual barriers and verifying the result with assistive technology:

  1. Audit the site against WCAG 2.1 AA with both automated tools and manual screen-reader and keyboard testing — a real accessibility audit.
  2. Remediate the underlying HTML, ARIA, contrast, focus order, and forms by hand — manual remediation that survives in your real code.
  3. Document and monitor with a VPAT, a genuine accessibility statement, and ongoing monitoring.

That’s the work overlays skip. It’s slower than pasting a script — and it’s the only thing that actually makes your site usable and defensible.

See what an overlay can’t fix

If a widget is currently the only thing standing between your site and a lawsuit, you deserve to know what it’s hiding. Start with a free accessibility scan to see the real barriers, learn the full picture in our ADA website compliance guide, and decide based on evidence — not a vendor’s score.

For independent background, see the community Overlay Fact Sheet and the W3C Web Accessibility Initiative.