Why accessibility overlays don't protect you

If you run a website and you've searched for "ADA compliance," you've seen the pitch: add one line of JavaScript, and an AI widget makes your site accessible and lawsuit-proof.

It doesn't. Here's what the record actually shows, with sources you can check yourself.

The web's accessibility problem is real

Every year, WebAIM analyzes the home pages of the top one million websites. Every year, the overwhelming majority — roughly 95% — have detectable WCAG 2 failures: low-contrast text, missing alternative text, unlabeled form fields, empty links (The WebAIM Million).

These are real barriers for real users, and most of them live in your markup, your styles, and your JavaScript. Which is exactly why an overlay can't fix them.

What overlays actually do

An overlay is a script that loads on top of your existing site and tries to modify it in the visitor's browser — injecting ARIA attributes, adjusting contrast, adding a settings panel. The underlying failures remain in your code. At best, some of them are papered over for some users in some browsers.

The Overlay Fact Sheet, signed by hundreds of accessibility practitioners — including many who use assistive technology daily — documents the practical problems: overlays frequently interfere with screen readers and keyboard navigation that users have already configured, and the "fixes" they apply are partial and brittle.

The legal record

Two things are worth knowing:

1. Sites with overlays still get sued. Digital-accessibility lawsuits routinely name sites that have an overlay installed. Installing a widget has not stopped plaintiffs' firms; in some complaints, the overlay itself is cited as a barrier.
2. Regulators have acted on overlay marketing. In 2025, the US Federal Trade Commission ordered an overlay vendor to pay $1 million over claims that its AI could make websites fully WCAG-compliant (FTC newsroom).

Meanwhile, the ADA.gov web guidance points to WCAG as the reference for web accessibility — and WCAG conformance is a property of your actual pages, not of a widget loaded on top of them.

What actually reduces risk

There's no shortcut, but the honest path is well understood:

• Find the real failures. Automated scanning against WCAG 2.1 catches a large share of issues reliably — contrast, labels, alt text, structure.
• Fix them at the source. In your templates, components, and content — the fixes are usually small once they're findable and assigned to the right person.
• Keep the record. A history of scans, fixes, and re-scans is genuine evidence of a remediation program, which matters if a complaint ever arrives.

That's the workflow BugPort is built around: scans mapped to WCAG success criteria, findings that become bug reports with element-level evidence, and re-scans that show the count going down. If you want to see where your site stands, start with a free WCAG audit — no widget included.