Sued Despite Having an Overlay: Why 22.6% of ADA Lawsuits Target Sites With Widgets Installed

The Number That Should Concern Every Merchant Using an Overlay

22.6%.

That's the percentage of websites sued for ADA accessibility violations in 2023 that already had accessibility overlay widgets installed at the time of the lawsuit.

Let that sink in: more than one in five websites that received an ADA lawsuit had AccessiBe, UserWay, AudioEye, or another overlay widget running on their site.

The overlay didn't protect them.

How Plaintiff Attorneys Actually Test Websites

To understand why overlays are weak as the only plan, you need to understand how accessibility issues are tested.

Plaintiff attorneys use the same testing tools as accessibility professionals:

• axe-core (the open-source engine used by accessibilityinsights.io)
• NVDA + Firefox and JAWS + Chrome for screen reader testing
• Lighthouse for automated auditing
• Manual keyboard navigation testing

Here's the critical part: these tools test the underlying source code, not the overlaid version.

When axe-core scans a page, it runs against the DOM. Yes, that includes JavaScript modifications from overlays — but with one major caveat: axe-core runs when the page is fully loaded, and it can distinguish between HTML-native accessibility versus JavaScript-patched accessibility. More importantly, actual screen reader users often navigate your page before the overlay's JavaScript has fully executed.

Plaintiff attorneys run two tests:

1. An automated scan (axe-core, WAVE, etc.) to identify violations
2. Manual screen reader testing to demonstrate that the experience is actually broken

Overlays fail both tests in many cases.

What Happens When You Disable JavaScript

Here's a test you can run right now on any site using an overlay:

1. Open your browser's developer tools
2. Disable JavaScript
3. Reload the page
4. Run an accessibility check

Without JavaScript, all of the overlay's "fixes" disappear. Every untagged image becomes inaccessible again. Every button without an ARIA label loses it. Every form without a label association breaks.

Plaintiff attorneys know this test. Courts can see it. And the underlying violations — the ones in your actual HTML — are still there.

The Practical Standard: Source-Code Remediation

The consistent technical lesson from accessibility testing is simple: you need to fix the actual source code where possible.

In practical testing, a page needs usable HTML semantics, accessible names, keyboard behavior, and contrast in the served storefront. The FTC's $1M order against AccessiBe in 2025 targeted unsupported automated-compliance claims, which is why merchants should verify actual output instead of relying on a widget promise.

The Settlement Pattern for Sites With Overlays

Attorneys who represent defendants in ADA cases report a consistent pattern:

When a defendant has no overlay, settlement negotiations center on remediation commitment (fix your violations) plus a monetary settlement.

When a defendant has an overlay, settlement negotiations become more complicated because:

1. The defendant believes (incorrectly) that they've already addressed the problem
2. The plaintiff's attorney has to spend time explaining why the overlay doesn't count
3. Courts are less sympathetic to defendants who paid for a product that claimed compliance but didn't deliver it — because it suggests they knew about the problem and chose a quick fix over genuine remediation

Having an overlay can complicate the conversation because it may create the impression that remediation happened when the theme source is still unchanged.

The Disability Community's View

The disability rights community — the actual community ADA lawsuits are meant to protect — has been unequivocal about overlay widgets.

The Overlay Fact Sheet, signed by hundreds of accessibility professionals including people with disabilities themselves, states:

"We call on the business owners, procurement professionals, and web developers who maintain the sites to seriously consider the impact that overlay products have on the communities they serve."

Disability rights organizations have filed amicus briefs in cases specifically arguing that overlays do not constitute compliance. This matters: courts look to the disability community when interpreting what "accessibility" means.

What Actually Reduces Your Risk

If overlays don't protect you, what does?

1. Source-code fixes that pass actual WCAG tests

Fix the HTML, CSS, and JavaScript violations in your store. When an accessibility audit runs against your source code, it should find no critical violations. This means genuinely fixing alt text, labels, keyboard navigation, contrast, and ARIA roles — not overlaying them.

2. An accessibility statement with a feedback mechanism

Publish an accessibility statement that describes your WCAG target, any known limitations, and a direct contact method for users to report issues. This gives customers a path to get help before frustration escalates.

3. Continuous monitoring

Theme updates, new product pages, and app installations can introduce new violations. Set up regular accessibility scanning to catch and fix regressions before they accumulate.

4. Documentation

Keep records of your accessibility work: scan reports showing violations before and after fixes, timestamps of when fixes were applied, and your remediation history. This documentation is valuable in demonstrating good-faith efforts if you're ever sued.

The Cost-Benefit Calculation

Let's do the math:

• AccessiBe subscription: ~$49/month = ~$588/year

• Source-code remediation from AccessiBe: None

• Average ADA lawsuit settlement for small ecommerce stores: $5,000–$25,000

• AccessComply Starter: $49/month = $588/year

• Source-code remediation from AccessComply: Eligible theme fixes, backups, and re-scans

• If challenged later: Stronger documentation of what changed and what still needs review

The price is similar. The remediation record is completely different.

The Takeaway

If you have an overlay widget on your store:

1. You should not treat it as lawsuit protection
2. You may be paying for a compliance promise that does not change the source
3. You may be in a worse legal position than you realize

If you don't have any accessibility solution:

1. You are at the same risk as the 77.4% of sued sites without overlays
2. The path forward is source-code fixes, not an overlay

Either way, the next step is the same: run a real accessibility audit, find out what violations actually exist in your source code, and fix them.

---

Run your free scan — see exactly what violations exist in your store's actual source code, not the overlaid version.

Further Reading

• Why Accessibility Overlay Widgets Don't Work (And What Actually Does)
• AccessiBe FTC Fine: The $1M Warning Every Shopify Merchant Needs to Hear
• 5 Real Shopify Stores Sued for ADA Accessibility: What They Got Wrong
• ADA Website Accessibility Lawsuit Statistics 2026