Why Accessibility Overlays Don't Protect You From ADA Lawsuits

If a tool promises ADA compliance with one line of code or an automatic scan, walk away. An overlay sits on top of broken code. The broken code is still there. We remove it — by hand.

Updated · By the REAL Accessibility engineering team

Overlays by the numbers

1 in 4

accessibility lawsuits in 2025 hit sites that already had an overlay installed.

$1M

FTC fine against a leading overlay vendor in 2025, for advertising guaranteed compliance.

30%

of WCAG issues is roughly all an automated tool can detect — let alone fix.

The problem

What an overlay actually does

An overlay is a script added to your site — usually a single line of JavaScript. It loads a toolbar with options like larger text or high contrast, and some versions try to "repair" the page automatically as it loads in the visitor's browser.

What it doesn't do is change your site. The theme, the templates, the missing labels, and the images without descriptions are all exactly where they were. When a plaintiff's tester visits with a screen reader, they meet the same barriers — plus a widget.

That's why plaintiffs now point to the widget itself. Overlay tools promise instant compliance with one line of code. Courts disagree, and so does the data.

What a script can't fix

The other 70% needs a human

Automated tools catch only 30% of WCAG issues. The other 70% — keyboard traps, focus order, meaningful alt text, form semantics — are exactly what gets you sued, and only a human can find them.

  • 1.1.1

    Meaningful alt text

    A script can guess a description; it can't know that the photo shows the product in the right color or size.

  • 2.1.2

    Keyboard traps

    A cart drawer or pop-up that traps focus is a coding problem in your theme, not something a toolbar can undo.

  • 2.4.3

    Focus order

    Whether focus moves in a logical order depends on how the page is built — and only a person can judge it.

  • 3.3.1

    Form errors

    Errors must be described in text and tied to their field. That's markup and logic, not a color filter.

  • 4.1.2

    Custom controls

    Menus, tabs, and variant pickers need the right name, role, and state in the code itself.

  • 1.3.1

    Structure

    Headings, lists, and tables have to be real in the markup for assistive technology to understand them.

The defensible alternative

What to do instead of an overlay

The defensible alternative is real remediation — fixing the code and verifying it by hand.

  1. Audit the site manually against WCAG 2.1/2.2 AA, with automated tools, code inspection, and screen readers.
  2. Fix the barriers in the code — on your platform, in your theme and templates.
  3. Remove the overlay once the fixes are live, so it can't interfere with users' own assistive technology.
  4. Document it with a before-and-after report you can hand your attorney.

What we don't do: no overlay widgets, no “one-click compliance,” no automatic-only scans sold as a fix, and no compliance guarantees. Just real, manual, code-level remediation.

See the full ADA website compliance checklist

FAQ

Accessibility overlays: common questions

What is an accessibility overlay?

An accessibility overlay is a third-party script — usually one line of JavaScript — that adds a toolbar or an automatic "fix" layer on top of a website. It tries to change the page in the visitor's browser instead of fixing the site's code.

Do accessibility overlays make my site ADA compliant?

No. Overlays sit on top of broken code without fixing it. Nearly 1 in 4 accessibility lawsuits in 2025 targeted sites that already had one installed, and in 2025 the FTC fined a major overlay vendor $1,000,000. Real remediation fixes the underlying code.

Is WCAG legally required?

The ADA doesn't name a technical standard for business websites, but U.S. courts use WCAG 2.1 Level AA as the benchmark in website cases, and WCAG 2.2 AA is current best practice. An overlay doesn't change whether your site meets those criteria.

Should I remove the accessibility widget from my site?

Plan the removal together with real remediation. Removing the widget alone changes nothing about your code; fixing the code is what matters. We audit the site, fix the barriers, and then remove the overlay so nothing interferes with assistive technology.

Why do people with disabilities dislike overlays?

Many screen-reader users already have their own settings and tools. Overlays can override them, add extra controls to navigate, and change how the page behaves — so real users with disabilities report overlays as making sites harder to use.

Start here

Replace your overlay with a manual audit and real fixes

Real issues, ranked by risk, with a clear remediation plan.

  1. Send your URLTell us your platform and what's going on — a demand letter, a redesign, or just peace of mind.
  2. An engineer reviews your siteWe scope the audit against all 55 WCAG 2.2 AA criteria, ranked by the issues most cited in complaints.
  3. You get a fixed scope and timelineBefore any work starts. No surprises, no widget, no guarantee we can't keep.

Prefer to talk? Call +1 (786) 793-6135 or message us on WhatsApp (opens in a new tab).

Optional. A demand letter, a redesign, a deadline — anything that helps us scope it.

Fields marked with an asterisk are required. Not legal advice.