The Problem With Accessibility Overlays — Why They Increase Legal Risk

If you received an ADA demand letter, or if you Googled "Shopify accessibility compliance," you likely encountered accessibility overlay vendors. They promise to make your site compliant with a single line of JavaScript, for $49–$490/month. In 2024, they are being named in roughly 25% of US ADA website accessibility lawsuits — more than any category of merchant.

This article explains what overlays actually do, why they fail both technically and legally, and what the FTC ruling means for merchants currently using them.

What accessibility overlays actually do

An accessibility overlay is a JavaScript widget that loads on top of your website and attempts to automatically fix accessibility issues in real-time. When a screen reader or keyboard user visits your site, the overlay intercepts their interaction and tries to fill in missing ARIA labels, add focus indicators, or adjust color contrast on the fly.

The problem is that this approach is fundamentally limited:

• It cannot fix what it cannot see. Many accessibility violations are structural — missing semantic HTML, incorrect heading hierarchy, keyboard traps in custom JavaScript. A JavaScript layer cannot rewrite the DOM structure that causes these failures.
• It creates conflicts with existing accessibility technology. Screen reader users frequently report that overlays interfere with their assistive technology in ways that make the site harder to use, not easier. The overlay "fixes" ARIA attributes that their screen reader was already handling correctly.
• Automated detection is 30–40% accurate at best. axe-core, the gold standard engine, detects approximately 30–40% of WCAG violations automatically. Overlay vendors use similar technology. The majority of violations require human evaluation. An overlay cannot auto-fix what it cannot detect.
• It is visible in your HTML. The overlay script tag is trivially identifiable. Plaintiff firms scan for known overlay vendor signatures specifically to flag sites as overlay users — because overlay users have often made compliance claims that can be challenged.

The lawsuit pattern

The typical lawsuit pattern involving overlays goes like this:

1. Merchant installs overlay, receives "certified accessible" badge or similar
2. Plaintiff's bot crawls the site, finds the overlay script tag, runs axe-core tests anyway
3. Violations are found (because the overlay did not fix the underlying DOM)
4. Demand letter is sent, referencing both the underlying violations and the misleading compliance claim made by the merchant (via the badge)
5. Merchant is now defending both the accessibility violations and a potentially deceptive marketing claim

"Defendants used [overlay vendor]'s accessibility widget on their website, yet the website still had 47 WCAG 2.1 AA violations. The presence of the widget does not demonstrate good faith — it demonstrates that the defendants were aware of their accessibility obligations and chose a tool that failed to meet them."
— Sample complaint language, 2024 (composite)

Why documented audits work better

The alternative to an overlay is an audit-based approach: regularly test your site, document what you find, and show evidence of remediation over time. This works for several reasons.

1. Courts reward documented effort, not perfect compliance

Every accessibility attorney who has commented publicly on litigation trends says the same thing: the question courts ask is not "is this site 100% accessible?" but "is this merchant making good-faith, documented efforts to improve?" A dated audit report showing 47 violations you are working through is a better legal position than a badge claiming zero violations — especially when a scan will immediately find violations anyway.

2. Immutable records create timeline proof

A PDF report with a SHA-256 fingerprint and a timestamp creates cryptographic proof of what your site's accessibility state was on a specific date. You can prove to a court that you were auditing, what you found, and that the report was not altered after the demand letter arrived. Overlays provide no comparable documentation.

3. Published accessibility statements reduce demand letter volume

A storefront footer with a dated accessibility statement, a contact mechanism for users to report barriers, and a commitment to regular audits signals to plaintiff screening bots and human reviewers alike that this merchant is actively engaged. It is not a guarantee — but it reduces the volume of demand letters initiated against merchants who have visibly credible programs.

What to do if you currently use an overlay

• Consult an accessibility attorney before removing or keeping the overlay — the choice depends on your specific situation and any existing demand letters.
• Do not rely on any "certification" or "compliance" badge from the overlay vendor as a legal defense.
• Begin running independent audits using axe-core or a tool built on it — establish a dated audit trail separate from the overlay vendor's claims.
• Review and update your website accessibility statement to accurately reflect current effort rather than making guarantees.