Sued With an Accessibility Widget Installed? Why It Happened and What to Do Now

Last updated: September 1, 2026

An accessibility widget lawsuit — a suit filed against a business that already has a widget on its site — is not a fluke: based on TestParty's analysis of Court Listener public records, more than 1,000 widget-equipped businesses were named in accessibility lawsuits in 2024 alone. So the letter on your desk does not mean your team did something uniquely wrong. It means the tool you installed never changed the thing plaintiffs test. Here is why, and what to do in the next seven days.

Key numbers: Based on TestParty's analysis of Court Listener public records, 1,000+ businesses with accessibility widgets installed were sued in 2024 — roughly 25% of digital accessibility filings. Federal website accessibility lawsuits rose 27% in 2025, to 3,117 filings, per Seyfarth Shaw's ADA Title III tracking. Roughly 70% of digital accessibility suits target e-commerce companies, according to UsableNet's 2025 year-end report.

This article is general information for business owners, not legal advice. If you have received a demand letter or a complaint, consult an attorney about your specific situation.

Why didn't the widget stop the lawsuit?

Because the widget never changed the code plaintiffs test. Screen readers work from your site's underlying source code, and an overlay widget modifies pages with JavaScript only after they load — so the original violations stay in place, documentable by anyone who looks.

Screen readers like JAWS, NVDA, and VoiceOver navigate the browser's accessibility tree, which is built from the HTML your server delivers (W3C Web Accessibility Initiative). A widget's corrections exist only after its script runs, and only for the elements its automation correctly guesses. A plaintiff's expert does not need your widget's cooperation: they run a screen reader session or an automated scan against your pages and record what fails — unlabeled buttons, missing form labels, images without alt text — with dates and screenshots. In our assessment, widgets can also introduce barriers of their own, such as panels that trap keyboard focus or override a user's configured screen reader settings. Concerns like these are why the Overlay Fact Sheet, an open letter signed by more than 800 accessibility practitioners, recommends against overlays as a compliance strategy.

Why don't plaintiff firms skip sites with widgets?

Because the violations they scan for are still present — and the widget's own script tag makes those sites easy to identify at scale. TestParty's Court Listener review found 456 widget-equipped defendants in the first half of 2025, 22.6% of the digital accessibility filings we examined.

That followed the 1,000+ widget-equipped businesses named in 2024. In TestParty's own audits of Shopify storefronts, stores running overlay widgets have generally scanned at underlying-code violation counts in the same range as stores running nothing at all — which matches what the filings suggest plaintiff firms already know. UsableNet reached a parallel conclusion in its 2025 year-end report: "widgets do not materially reduce legal risk." One honest caveat cuts the other way: hundreds of thousands of sites run widgets and most are never sued in a given year, so a widget is not a lawsuit magnet — it is simply not a shield. The complete year-by-year figures, sources, and methodology caveats are in our 2026 overlay lawsuit dataset.

What should you do in the first week after the letter arrives?

Five moves, in this order: calendar the deadline, preserve evidence, retain experienced counsel, measure your real exposure, and start documented source-code fixes. Each one improves your position; skipping any one weakens it.

1. Mark the deadline — and don't reply yourself. A federal complaint typically gives you about 21 days to respond; demand letters often invent shorter deadlines to create pressure. Either way, no one on your team should contact the plaintiff's firm directly.
2. Preserve the site exactly as it stands. Take date-stamped screenshots and scan reports with the widget active, before changing anything. Do not uninstall the widget or purge records without counsel's sign-off.
3. Retain counsel who actually defends web accessibility cases. Flat-fee ADA website defense exists; a one-hour consult with a specialist beats weeks of guessing.
4. Measure your actual exposure. Run axe, WAVE, or Lighthouse against your key pages. What free scanners catch approximates what the plaintiff's expert will document.
5. Start fixing the source code — and document every fix. Dated remediation evidence changes negotiations. In one public TestParty case study, Dorai Home resolved a $74,999 demand for a $2,000 settlement after source-code remediation was underway.

The expanded version of each step, plus a free response template, is in our ADA demand letter response guide. If you were served with a filed complaint rather than a letter, start with what to do when you get an ADA website lawsuit.

Does having a widget help or hurt your defense?

In our assessment, it can cut either way: a widget is evidence you knew accessibility mattered, and what that evidence proves depends entirely on what you did next.

The favorable reading is good faith — you spent money on accessibility rather than ignoring it, and some defendants present the widget exactly that way. The unfavorable reading is that you were aware of your obligations and chose a tool that left your code unchanged. That framing has gotten easier for plaintiffs since April 2025, when the FTC approved a final order requiring accessiBe to pay $1 million under a 20-year consent order over marketing claims the agency alleged were deceptive — an action against accessiBe specifically, not overlay vendors generally, but one that undercuts "the vendor said we'd be compliant" as a comfortable position. What we can say from experience is narrower: settlement posture improves when a defendant can show dated proof of real code changes. Which way your widget cuts is a judgment for your counsel.

Should you keep the widget or replace it after the dust settles?

Either path is defensible only if the underlying code gets fixed. Removing a widget by itself changes nothing a plaintiff tests; keeping one while remediating the source code is a decision about user-facing features, not about compliance.

The repeat-filing data is the reason this decision matters: UsableNet counted 1,427 suits against previously sued companies in 2025 — 45% of federal digital accessibility cases — and a settlement resolves one plaintiff's claim, not the next one's. The case for keeping the widget is honest but narrow: some visitors use its display controls, and there is no rule requiring removal. The case for replacing it, in our assessment, is operational — one source of truth in your code, no script conflicts, and scan results that mean what they say. We compare the options in our guide to accessibility overlay alternatives. For context on the source-code route: TestParty's standard initial remediation runs 14 days, and in the history of the company, fewer than 1% of TestParty customers have been named in accessibility lawsuits while on the platform. No approach — ours included — can guarantee no one ever files.

What should you ask any vendor before you sign again?

Six questions separate marketing from mechanism, and a vendor's willingness to answer them tells you as much as the answers do.

• Does your product modify my site's source code, or layer JavaScript on top of it?
• Will you show me before-and-after scans of the underlying code — axe, WAVE, Lighthouse — not just the rendered page with your tool switched on?
• How many of your customers have been named in accessibility lawsuits while using your product?
• Are your reports date-stamped and formatted so my defense counsel can actually use them?
• What happens to my fixes when my theme or platform updates?
• Who performs manual testing with real assistive technology, and how often?

The third question is the one most vendors dodge — and the one this entire experience has taught you to insist on. For the background on why widget marketing and lawsuit outcomes diverge, see our analysis of whether a widget can keep you from getting sued.

Frequently Asked Questions

Will removing the accessibility widget make the lawsuit go away? No. The claim is about barriers in your website, not about the widget, so uninstalling it changes nothing in the complaint. Removing it mid-dispute without legal guidance can also complicate evidence preservation. Talk to counsel before altering the site, then focus on fixing and documenting the underlying code — that is what affects the outcome.

Is my widget vendor liable for the lawsuit? The complaint names your business, and ADA obligations rest on the business that operates the site — courts have not shifted that duty to tool vendors. Whatever remedies your vendor contract may offer, the defense and any settlement are yours to manage. Review your agreement with counsel, and notify the vendor in writing so the record is clean.

What do accessibility widget lawsuits typically settle for? Commonly cited industry ranges run $5,000–$20,000 for typical small-business matters, with demand letters sometimes resolving for $1,500–$5,000 (settlement ranges tracked by defense firms such as Seyfarth Shaw). Documented remediation moves cases toward the low end: in TestParty's public Dorai Home case study, a $74,999 demand settled for $2,000. Your facts, venue, and counsel drive the actual number.

Can I be sued again after I settle? Yes — repeat filings are common. UsableNet's 2025 year-end report counted 1,427 suits against previously sued companies, 45% of federal digital accessibility cases that year. Your settlement binds one plaintiff; it does not stop a different plaintiff from filing over barriers that remain. Fixing and monitoring the source code is what shrinks the target, not the settlement itself.

Does a widget make my site ADA compliant? No tool can certify ADA compliance, because the ADA is measured by effective access rather than by any product's presence. Courts and the Department of Justice consistently reference WCAG as the practical benchmark for websites. Compliance is a property of your site's code and content as assistive technology experiences it — which is exactly what a widget leaves largely unchanged.

How long does it take to fix the underlying code? It depends on scope, but weeks — not days or years — is the realistic band for most e-commerce sites. TestParty's initial source-code remediation runs 14 days for Shopify stores, followed by daily automated scans and monthly manual audits, because themes and apps keep changing. Whatever vendor you use, ask for a dated timeline; that documentation matters if another claim arrives.

This article was produced using TestParty's cyborg approach — AI-assisted research and drafting, validated and refined by our accessibility team. The analysis above represents TestParty's editorial opinions based on publicly available data. As a competitor in the accessibility market, we have a point of view — but we've cited our sources so you can verify every claim independently.