Overlay Installed, Still Sued: 2024-2026 Pattern Analysis
TABLE OF CONTENTS
- What's the Frequency of Overlay-Installed Lawsuits?
- What's the Plaintiffs' Legal Rationale?
- What's the Settlement Pattern in Overlay-Installed Cases?
- What Are the Repeat-Defendant Patterns?
- What's the Recommended Path After a First Demand Letter?
- What Does TestParty's Approach Look Like?
- Frequently Asked Questions
The question we hear most often from Shopify merchants who installed overlay widgets is "we have AccessiBe โ why are we getting demand letters?" The answer lives in Court Listener's public-record database and recent Seyfarth Shaw litigation tracking: about 1,000+ lawsuits per year are filed against businesses that already had overlay widgets installed at the time of filing. Roughly 25% of accessibility-related digital filings target overlay-installed sites specifically. This article walks through the pattern, the plaintiffs' legal rationale, and what merchants should take from it.
What's the Frequency of Overlay-Installed Lawsuits?
Per Court Listener public-record analysis through 2024-2026, Shopify ADA filings totaled approximately 4,000-5,000 per year across the period. Of those, ~25% involved sites with one of the major overlay widgets installed at the time of complaint (AccessiBe, UserWay, EqualWeb, EcomBack, or similar). Overlay-installed defendants spanned all revenue tiers from sub-$1M up through Plus enterprise; the overlay didn't exempt any tier.
The growth in the overlay-installed segment of filings has been roughly proportional to growth in overlay installations across Shopify. As overlay adoption increased through 2022-2024, overlay-installed lawsuits increased proportionally. The structural pattern: plaintiffs' firms can identify overlay-installed sites quickly via JavaScript fingerprinting, and these sites have a known regulatory-target pattern that makes them attractive defendants. For broader litigation context, see our accessibility overlays lawsuits truth and shopify accessibility statistics 2025.
What's the Plaintiffs' Legal Rationale?
Three repeated arguments in overlay-installed cases. The overlay didn't actually fix the violations alleged. Plaintiffs' counsel typically runs an automated WCAG scan and a manual screen-reader review showing the specific failures (missing form labels, keyboard traps, color contrast, etc.) โ failures that exist at the source-code level and that the overlay structurally cannot reach. The overlay's marketing claims constitute false advertising or unfair business practices. Some plaintiffs add UCL (California Unfair Competition Law) or similar consumer-protection claims, citing the gap between overlay marketing and what the overlay actually delivers. Continuing presence of the overlay after demand letter constitutes ongoing violation. If a merchant retains the overlay after being notified of the issues, plaintiffs cite the failure to remediate as evidence of inadequate good-faith effort.
The FTC's April 2025 enforcement against accessiBe specifically โ for "false, misleading, or unsubstantiated" claims โ has been cited in subsequent private litigation as supporting evidence for the false-advertising arguments above. For overlay-failure technical breakdown, see why AI overlays fail technical breakdown and overlays band-aid.
What's the Settlement Pattern in Overlay-Installed Cases?
Higher than non-overlay-installed cases on average. Per Seyfarth Shaw and public settlement data through 2024-2025: average settlement for non-overlay-installed Shopify defendants approximately $25K-$45K; average settlement for overlay-installed Shopify defendants approximately $45K-$75K. The differential reflects two factors. First, plaintiffs see overlay-installed defendants as more clearly liable because the marketing-promise gap creates additional UCL/unfair-business-practice exposure. Second, settlement negotiations typically include a "remove the overlay" condition, plus a remediation timeline and ongoing accessibility-monitoring obligations.
Settlement structures we've observed: monetary settlement (typical $25K-$75K), remediation timeline (typically 90-180 days to reach WCAG 2.2 AA), continuous-monitoring requirement (annual third-party audit or platform-based monitoring), accessibility-statement publication, and overlay removal. The ongoing monitoring obligations alone produce $5K-$25K/year in continuing cost โ a meaningful tail beyond the lump-sum settlement.
What Are the Repeat-Defendant Patterns?
Overlay-installed defendants are ~2x more likely to be sued again within 24 months than non-overlay defendants. Court Listener tracking shows ~12-15% of overlay-installed defendants face a second filing within 24 months of the first; ~6-8% for non-overlay defendants. The repeat-defendant pattern reflects two factors. First, settlement remediation timelines often expire before the merchant has actually completed remediation, exposing the merchant to second filings. Second, plaintiffs' firms maintain target lists; merchants who appeared in one filing remain on those lists for subsequent monitoring.
Practical implication: settling a first lawsuit by retaining the overlay and committing to a 180-day remediation timeline is structurally insufficient if the merchant doesn't actually achieve source-code remediation in that window. Second lawsuits target the same site with documentation that the first lawsuit's remediation was incomplete. For lawsuit-pattern context, see Sub-$10M stores sued data.
What's the Recommended Path After a First Demand Letter?
A specific four-step pattern we've seen work. First, immediately engage source-code remediation. Do not retain the overlay as the primary remediation strategy; the overlay being present has been adverse to settlement negotiations. Second, document remediation actions taken with timestamps. Date-stamped issue lists pre-remediation and post-remediation; re-scan results; manual audit confirmations. Third, publish an accessibility statement. Not optional โ accessibility statement publication is standard expected practice and absence of a statement is cited as evidence of inadequate good-faith effort. Fourth, engage continuous monitoring. Daily automated scans plus monthly expert manual audits โ both for compliance posture and as a settlement-favorable factor in the current case.
For specific demand-letter response, see our got a demand letter 30-day plan. For broader source-code-vs-overlay context, see accessibility overlays vs source code remediation Shopify.
What Does TestParty's Approach Look Like?
TestParty has supported many merchants through this exact pattern: overlay installed, demand letter received, source-code remediation engaged, settlement reached on favorable terms with the overlay removed. Our approach: emergency-pace audit and remediation roadmap (week 1), source-code remediation execution starting immediately (weeks 1-12), date-stamped compliance reports for legal counsel (continuous), accessibility statement and feedback channel publication (week 1-2), ongoing daily automated scans plus monthly expert manual audits (continuous after launch). Compliance scope spans ADA, WCAG 2.2, EAA, CIPA, and GDPR; TestParty was named to the Forbes Accessibility 100 in 2025.
In our experience working with 100+ brands, source-code remediation produces fewer than 1% lawsuit rates. We've remediated 1,575,000+ WCAG issues across the customer base. For the broader picture, see death of overlays.
Frequently Asked Questions
If we already settled a case with an overlay still installed, are we vulnerable to a second lawsuit? Higher than average. Per Court Listener tracking, ~12-15% of overlay-installed defendants face second filings within 24 months. Settling without removing the overlay leaves the underlying source-code issues unaddressed; subsequent plaintiffs' firms can target the same site with a fresh complaint. Source-code remediation post-first-settlement reduces second-filing probability.
Can we use the FTC accessiBe order as evidence in our case? Possibly โ work with your accessibility-litigation counsel. The April 2025 FTC order is public record and has been cited in subsequent private litigation. Whether it's admissible and material in your specific case depends on jurisdiction, the overlay vendor involved, and the specific claims. Counsel familiar with accessibility litigation will know how to position it.
Will plaintiffs accept a settlement that retains the overlay? Some will. The pattern we observe: smaller settlements ($25K-$50K) often allow overlay retention; larger settlements ($50K+) typically require removal as a condition. The structural concern from plaintiffs' perspective is the public posture of the merchant; settlement without overlay removal allows the merchant to claim accessibility-compliance status that plaintiffs' counsel finds objectionable.
How quickly can we reach WCAG 2.2 AA after a demand letter? Standard Shopify themes: 30-90 days with source-code remediation platform support. Plus and customized themes: 60-180 days. Headless: 90-180 days. The first 30 days produce the largest issue-count reductions; the long tail is structural and edge-case. Settlement timelines typically allow 90-180 days, which aligns with achievable remediation timelines in most cases.
Are demand letters always followed by lawsuits if we don't settle? No. Many demand letters resolve through pre-litigation negotiation; some demand letters are dropped if the merchant demonstrates serious remediation effort. Per Court Listener, approximately 60-70% of demand letters become formal complaints if unaddressed; the other 30-40% resolve pre-suit. Active engagement with the demand letter (response within 30 days, remediation plan, statement publication) reduces formal-complaint conversion rate substantially.
Should we keep our overlay installed during the remediation period? In our assessment, no. The overlay has been adversely cited in settlement negotiations and produces no remediation value. The user-facing features (font sizing, contrast toggles) can be replaced by a lightweight no-conformance-claim widget. Removing the overlay during remediation is the favorable structural posture per the patterns we've observed.
Does the overlay-installed lawsuit pattern affect non-overlay sites with similar accessibility issues? Yes โ non-overlay sites with comparable issue volumes face similar lawsuit risk, just at lower per-site rates. The structural rule: WCAG violations create lawsuit risk regardless of whether an overlay is installed. The overlay-installed delta is the FTC-supported false-advertising layer; the underlying ADA Title III exposure is comparable. For broader risk assessment, see percentage of ecommerce WCAG compliant.
What's the role of an accessibility statement in defending against second lawsuits? Material. An accessibility statement that documents conformance level, known limitations, remediation timeline, and feedback channel is cited by counsel as evidence of good-faith remediation effort. Absence of a statement is cited adversely. Templates exist; publication is straightforward via Shopify's /pages/ system. Reference: Shopify accessibility statement template generator 2026.
Built with TestParty's cyborg approach โ AI-powered research combined with human accessibility expertise. This article contains TestParty's editorial analysis based on publicly available information. We're an accessibility vendor with opinions informed by working with 100+ brands, and we encourage readers to do their own due diligence when evaluating any solution.
Stay informed
Accessibility insights delivered
straight to your inbox.


Automate the software work for accessibility compliance, end-to-end.
Empowering businesses with seamless digital accessibility solutionsโsimple, inclusive, effective.
Book a Demo