In short
- UsableNet’s year-end count for 2025 is 5,114 ADA digital accessibility lawsuits in the United States, 3,195 in federal court and 1,919 in the state courts of New York and California; 70% targeted e-commerce, 36% of the top 500 online retailers received at least one, and 1,427 suits went to companies sued before. The report’s reading of accessibility overlay widgets is that they did not slow the litigation.
- A buyer who has read that report asks a vendor for an Accessibility Conformance Report, the document a VPAT produces, before signing. The report they accept states what was tested, against which WCAG version and level, by which method, and leaves the criteria a machine cannot judge marked for a person; the report they send back claims full conformance from a template.
- Automation fills in a minority of the WCAG criteria reliably. An honest VPAT built from a real scan carries the automated results in its WCAG table, marks the manual-review criteria as such, and leaves the Section 508 and EN 301 549 tables for a human evaluation, because that is what they are.
About this article
- Format
- Report read: a public report or a regulation read for what it changes in your work.
- Written for
- Accessibility owners · People evaluating or buying tools · Product owners
- Where it applies
- The rules it cites are specific to United States, Ireland, Germany, France and Netherlands. The lawsuit count is United States litigation under the ADA. In the EU the mechanism is the European Accessibility Act and EN 301 549, and one WCAG 2.2 AA audit answers both.
The 2025 count
UsableNet, which publishes a count of ADA digital accessibility litigation twice a year, reviewed 5,114 lawsuits filed in 2025: 3,195 in federal courts (62%) and 1,919 in the state courts of New York and California (38%). E-commerce accounted for 70% of the cases, and 36% of the top 500 online retailers received at least one lawsuit during the year. Repeat defendants are a feature of the data, not an exception: 1,427 suits, 45% of the federal filings, targeted companies that had already been sued. On accessibility overlay widgets, the scripts that promise to fix a site from a single line of code, the report’s conclusion is that they did not slow litigation in 2025, and that widgets typically do not resolve underlying code-level issues.
Outside the United States the mechanism is regulation rather than litigation. The European Accessibility Act has applied since 28 June 2025 to the products and services it lists, e-commerce among them, and public-sector procurement in Europe runs on EN 301 549, whose in-force version, 3.2.1, references WCAG 2.1 AA. WCAG 2.2, the current W3C Recommendation, is the version to build and test to: it keeps every 2.1 AA criterion still in force and adds nine, so one 2.2 AA audit answers a 2.1 AA request.
Why the number arrives as a procurement question
A retailer that has read the count, or has been one of the 1,427, has a reason not to stop at its own storefront. Every vendor whose interface its staff or customers use is part of the exposure, and the question to the vendor is an Accessibility Conformance Report, the document the VPAT template produces. Enterprise and public-sector buyers ask for one routinely, and a buyer facing the exposure above has a reason to read the answer closely.
The VPAT a buyer accepts
- It names the WCAG version and level tested (2.2, A and AA), the product version and the date, and the method: automated audit, manual review, assistive-technology testing, or a combination.
- Its WCAG table says "supports", "partially supports", "does not support" or "not applicable" per criterion with a remark that a person can check, and the criteria that automation cannot judge are evaluated by a person before the report says anything about them, never marked "supports" by default.
- Its Section 508 and EN 301 549 tables are completed by someone who evaluated them, or the edition that carries them is not sent until they are. A table filled by copying the WCAG results is the first thing an experienced reviewer notices.
- It carries a known-gaps list with dates, because a report with no gaps describes a product that was not tested.
The one they send back
A conformance report that claims full support on every criterion from a template, with no method, no date and no gaps, is sent back with a request for the audit behind it. So is a report that marks criteria a machine cannot judge, meaningful alternative text, logical reading order, understandable error messages, as supported on the strength of a scan. Automation judges a minority of the WCAG criteria, an experienced reviewer knows it, and the report that pretends otherwise costs the vendor the credibility of every other claim in the deal.
In the product
What an automated audit can put in the report
Dokimore’s accessibility audits run axe-core in a real browser against WCAG 2.0, 2.1 and 2.2 at Levels A and AA, per page or per recorded flow, and produce findings with the element, the rule, the criterion and a remediation. The VPAT draft is generated from the scan that was actually run: its WCAG table is filled criterion by criterion from the audit results, Level AAA and the judgement criteria are marked for manual review and never auto-passed, and the Section 508 and EN 301 549 tables are left empty for a person to evaluate. A reference table in the product relates the accessibility laws of 66 countries to the WCAG version each cites; findings are not mapped to it automatically, and we say so. Our own site’s accessibility statement is partial, with the gaps named and dated, which is the standard we are asking you to hold your vendors to.
For the manager reading this
If a buyer asks for a VPAT and the answer is a week away, the answer is a scan today and a person tomorrow. Audits are on Solo Pro, Team and Enterprise; the draft takes the time of the scan, the manual-review list takes the time of a person, and the report that comes out says which was which.
What to do next
- Ask every vendor whose interface your staff or customers use for an Accessibility Conformance Report, and read the method line first: automated, manual, assistive technology, or a combination.
- Send back any report that claims full support on every criterion from a template, or that marks judgement criteria as supported on the strength of a scan.
- For your own product, run the audit against WCAG 2.2 A and AA, mark the manual-review criteria for a person, and leave the Section 508 and EN 301 549 tables to someone who evaluated them (accessibility audits and VPAT).
- Keep a dated known-gaps list in the report; a report with no gaps describes a product that was not tested.
- Use VPAT 2.5Rev in the edition that matches the buyer’s market: WCAG, 508, EU or INT.
Questions people ask
How many accessibility lawsuits were filed in 2025?
UsableNet’s year-end report counts 5,114 ADA digital accessibility lawsuits in the United States in 2025: 3,195 in federal courts and 1,919 in the state courts of New York and California. Seventy percent targeted e-commerce, 36% of the top 500 online retailers were sued at least once, and 1,427 suits went to companies that had already been sued.
What is a VPAT?
The Voluntary Product Accessibility Template, published by the Information Technology Industry Council; the document it produces is an Accessibility Conformance Report. It states, criterion by criterion, how a product supports WCAG and, in its other editions, Section 508 and EN 301 549, with a remark per row. Buyers ask for it during procurement.
Can a VPAT be generated automatically?
Its WCAG table can be drafted from a real automated audit, with each criterion the scan can judge filled from the results. The criteria a machine cannot judge must be marked for a person, and the Section 508 and EN 301 549 tables need a human evaluation. Dokimore generates the draft that way and leaves those parts for you to complete.
Do accessibility overlay widgets protect against lawsuits?
UsableNet’s 2025 year-end report concludes that widgets did not slow litigation in 2025 and typically do not resolve the underlying code-level issues. A widget can be a reasonable interim measure for some users; it is not a conformance claim and should not appear in a VPAT as one.
Which WCAG version should a 2026 audit use?
WCAG 2.2, the current W3C Recommendation, at Levels A and AA. It keeps every WCAG 2.1 AA criterion still in force and adds nine, so a product audited against 2.2 AA can answer the 2.1 AA request that EN 301 549 version 3.2.1 makes for European procurement.
Which VPAT version is current?
The Information Technology Industry Council lists VPAT 2.5Rev, from April 2025, in four editions: WCAG, Section 508, EU (EN 301 549) and INT, which combines the three. Use the edition that matches the buyer’s market, and fill only the tables someone has actually evaluated.
How we measured this
- The lawsuit figures are quoted from UsableNet’s own year-end report as read on the date beside the reference; the state-court count covers New York and California only, as the report states, and we have not verified the filings independently.
- The description of the VPAT a buyer accepts is our reading of what reviewers check, not a procurement standard any authority publishes.
- Dokimore’s behaviour is the product on the article date: axe-core audits against WCAG 2.0, 2.1 and 2.2 at A and AA, manual-review criteria never auto-passed, a VPAT draft whose WCAG table comes from the scan and whose Section 508 and EN 301 549 tables are left for a person, and a 66-country reference table that is not applied to findings automatically.
Sources
- UsableNet, 2025 Year-End Digital Accessibility Lawsuit Report (plain-text edition): 5,114 lawsuits, 3,195 federal and 1,919 state, 70% e-commerce, 36% of the top 500 retailers, 1,427 repeat defendants, widgets did not slow litigation read
- W3C WAI, "What’s New in WCAG 2.2": Recommendation of 5 October 2023, nine new success criteria, 4.1.1 removed read
- Information Technology Industry Council, VPAT: VPAT 2.5Rev (April 2025) in WCAG, 508, EU and INT editions; a completed VPAT is an Accessibility Conformance Report read