No. Nothing in the public filing data shows that installing an accessibility overlay is what gets a company sued. It also shows the opposite of what overlay marketing implies: the widget does not keep the claim away. UsableNet's July 2026 analysis of US digital accessibility litigation found that roughly 20% of the companies sued already had an accessibility widget or overlay installed, and states plainly that installing one "does not establish that a website is accessible, nor does it necessarily resolve the underlying barriers alleged in a claim" (UsableNet). Federal website accessibility filings reached 3,117 in 2025, up 27% on the 2,452 filed in 2024 (Seyfarth Shaw).
There is one place an overlay measurably adds exposure, and it is not the script. It is what you publish next to it. The FTC's $1 million order against accessiBe was about compliance claims, not about code (FTC).
Do accessibility overlays cause lawsuits?
There is no evidence that they do, and I want to be careful here because the honest answer is less satisfying than the slogan.
The number people quote is the 20% figure above: one in five sued companies had a widget running. That tells you overlays are common among defendants. It does not tell you the widget attracted the claim. About 80% of these lawsuits involve e-commerce companies, and e-commerce is also where overlay vendors sell hardest (UsableNet). Two populations that overlap heavily will look correlated whatever the causal story is.
Nobody has published a controlled comparison of matched sites with and without a widget, so anyone telling you overlays cause lawsuits is reasoning past the data. What is observable is narrower: the widget loads from a third-party domain and its script tag sits in your page source, visible to anyone who opens developer tools, including a plaintiff's tester. I have not seen filings data showing firms search on that, and I am not going to assert it.
Do overlays reduce the chance of being sued?
The tracking data says no, and the trend has held for several years.
UsableNet's midyear report puts 2026 on pace for about 6,176 federal and state digital accessibility lawsuits, close to 20% above 2025, and its assessment of widgets is blunt: "the presence of a widget has not proven to be a meaningful deterrent, legally or practically" (UsableNet).
The mechanism is ordinary once you look at what a complaint actually claims. A typical web accessibility complaint says a named person, usually a screen reader user, tried to do something on the site and could not finish it. Add something to the cart, then pay for it. The allegation is about a task that failed, not about which scripts were present while it failed.
Now look at what an overlay can reach. It runs in the visitor's browser after your page has loaded, and it changes the rendered DOM. It cannot change the template that produced the DOM. If your checkout has a <div onclick="submitOrder()"> that was never a <button>, the widget can bolt role="button" onto it at runtime and still leave the element unreachable by keyboard. The tester presses Tab, never lands on it, and that is the paragraph that ends up in the complaint.
Here is the opinion I will state once, because it is why we built the product the way we did. An overlay is optimised for the person buying it, not for the person stuck on the payment step. Those are different jobs, and only one of them is what the law asks about.
What did the FTC order actually change?
It moved the risk from the code to the marketing, and that part is worth reading closely if you run a widget today.
The Commission approved the final order against accessiBe on 22 April 2025 by a 3-0 vote, with a $1 million payment. The FTC alleged the company falsely claimed its accessWidget plug-in could make any website comply with WCAG and keep it that way over time. The order bars representations that an automated product can make a website WCAG-conformant or maintain conformance unless the company has evidence to support the claim. It separately bars presenting paid or connected reviews as the independent opinions of ordinary users (FTC).
Read that as a rule about surfaces you control. If you install a widget and then publish a badge or a statement saying your site meets WCAG because of it, you have made a compliance claim in your own name. The order is against the vendor, but the standard it applied, that a claim needs evidence behind it, applies to whoever publishes the claim.
Is there a certification or safe harbour that stops a claim?
No. No US agency approves accessibility tools, and no certificate forecloses a claim.
The Department of Justice says organisations "have flexibility in how they comply with the ADA's general requirements of nondiscrimination and effective communication," and that it "does not have a regulation setting out detailed standards" for private businesses under Title III, applying its longstanding interpretation of the general provisions instead (DOJ). Flexibility on method is not permission to skip the outcome. It also means no vendor can sell you a shield, because there is nothing to sell.
That is a US answer. In the EU the structure is different, since the European Accessibility Act works through market surveillance authorities and a documented conformity claim rather than private litigation, and a widget does not satisfy that either.
What actually changes your risk?
Evidence about your own code, and a record of what you did with it.
Start by scanning your real markup against WCAG 2.2 AA and getting each failure mapped to the success criterion it breaks, with the element and the selector. Fix those in source, so the correction ships with the component and survives the next deploy. Then put a person through your money flows with a keyboard and a screen reader, because automated testing covers roughly 30 to 57% of issues depending on how you count, and stops where judgement starts (Deque). Our scanner will flag an image with no alt attribute. It cannot tell you the alt text you wrote is wrong, or that your error summary makes no sense when read aloud. A tester can.
Keep the artefacts. Dated scan exports, the tickets you closed, the manual test notes, and an honest accessibility statement that says what you tested and what you know is still broken. None of that is a defence in the legal sense, and I would not sell it as one. What it does is let you answer a demand letter with a remediation record instead of a widget subscription, which is a materially better position for ADA purposes than a badge you cannot support.
If you are not sure which criteria you have never checked, the WCAG checklist is a reasonable place to see the shape of the gap before you spend money on anything.
Frequently asked questions
Do accessibility overlays cause lawsuits?
There is no published evidence that they do. Roughly 20% of companies sued in the 2026 US data had a widget installed, but overlay customers and lawsuit defendants are both concentrated in e-commerce, which is about 80% of filings, so the overlap does not establish cause (UsableNet).
Can an overlay be used as a defence if I get sued?
Not as a demonstration of accessibility. The complaint alleges a specific task failed for a specific user, and a runtime script that did not change your source code does not answer that. UsableNet's 2026 assessment is that a widget "has not proven to be a meaningful deterrent, legally or practically" (UsableNet).
Does removing an overlay reduce my risk?
Removing it changes nothing on its own, because the barriers were always in your code. What lowers risk is fixing those barriers in source and keeping the record. If the widget is also the basis of a compliance badge on your site, take the badge down until you can support what it says.
What do accessibility practitioners think of overlays?
In WebAIM's third survey of accessibility practitioners, run in 2021 with 758 valid responses, 67% rated overlays not at all or not very effective. Among respondents who have disabilities themselves that rose to 72%, with 2.4% rating them very effective (WebAIM).
How many web accessibility lawsuits are filed each year?
Federal website accessibility filings were 3,117 in 2025, 27% above 2024 and 36% of all ADA Title III federal cases (Seyfarth Shaw). Counting state courts and mobile apps as well, UsableNet projects about 6,176 for 2026 (UsableNet).
See what your own code says
The argument above only matters if you know what is actually in your markup. Run a free scan and you get the failing elements with selectors and the success criterion each one breaks, on your real pages rather than a home page sample. Fix those in source, then have a person walk your checkout with a screen reader for the criteria a machine cannot decide. That is a slower answer than a script tag, and it is the one that holds up when somebody asks what you did.
Pavel Charkasau, founder, wcagc.com. Last updated 12 September 2026.
Sources
- UsableNet, Digital Accessibility Lawsuits in 2026: Five Trends Companies Should Know — approximately 20% of sued companies had an accessibility widget or overlay installed; approximately 80% of digital accessibility lawsuits involve e-commerce companies; installing a widget "does not establish that a website is accessible, nor does it necessarily resolve the underlying barriers alleged in a claim." Published 31 July 2026; accessed 12 September 2026.
- UsableNet, Inside the 2026 Midyear Numbers: Where Digital Accessibility Litigation Is Going — approximately 6,176 projected US federal and state lawsuits for 2026, close to 20% above 2025; 79% of filings in e-commerce; "the presence of a widget has not proven to be a meaningful deterrent, legally or practically." Published 8 July 2026; accessed 12 September 2026.
- Seyfarth Shaw, Federal Court Website Accessibility Lawsuit Filings Bounce Back in 2025 — 3,117 federal website accessibility filings in 2025 against 2,452 in 2024, a 27% increase; 36% of all ADA Title III federal lawsuits. Published 25 March 2026; accessed 12 September 2026.
- Federal Trade Commission, FTC Approves Final Order Requiring accessiBe to Pay $1 Million — final order approved 22 April 2025 by a 3-0 Commission vote; alleged deceptive claims that accessWidget could make any website comply with WCAG and maintain compliance over time; order bars such representations without supporting evidence and bars presenting connected reviews as independent opinions. Accessed 12 September 2026.
- U.S. Department of Justice, Guidance on Web Accessibility and the ADA — businesses and state and local governments "have flexibility in how they comply with the ADA's general requirements of nondiscrimination and effective communication"; DOJ "does not have a regulation setting out detailed standards" for web content under Title III. Accessed 12 September 2026.
- WebAIM, Survey of Web Accessibility Practitioners #3 Results — 2021 survey, 758 valid responses; 67% rated overlays not at all or not very effective, 72% among respondents with disabilities, 2.4% rating them very effective. Accessed 12 September 2026.
- Deque Systems, Automated Testing Study Identifies 57% of Digital Accessibility Issues — more than 2,000 audits across roughly 13,000 pages; about 57% of issues by volume completely covered by automated testing, lower when counted by success criteria. Accessed 12 September 2026.