What The Main Sources Measure
WebAIM's Million project is a technical prevalence study. In 2026, it reported automatically detectable WCAG failures on 95.9 percent of tested home pages, with an average of 56.1 detectable errors per page. That does not equal a lawsuit count, but it shows why public websites often contain issues that can be discovered quickly.
Seyfarth's ADA Title III filing analysis is a federal-court litigation count. Its 2025 website-accessibility filing update reported 3,117 federal website accessibility lawsuits and described a 27 percent rebound after the prior year's decline. That is narrower than all demand letters or all state-court activity.
UsableNet's 2025 trend report looks at a broader digital-accessibility lawsuit universe that includes federal and key state-court activity. It says its team reviewed more than 5,000 digital accessibility lawsuits and found ecommerce accounted for nearly 70 percent of ADA web lawsuits in its dataset. Its methodology and incentives differ from WebAIM and Seyfarth, so it should be read as directional market evidence rather than a court-system census.
How PACER And NOS 446 Fit In
PACER Case Locator is a search layer for federal case information, not a marketing list. NOS 446 generally means Americans With Disabilities - Other, and the civil cover sheet category can include public-accommodation ADA claims.
The NOS code alone does not prove that a case is about a website, does not identify the alleged barriers, and should not be used to publish names, docket numbers, or case captions on public landing pages.
For lead segmentation, PACER/NOS 446 can signal urgency. For the visitor experience, the public page should remain counsel-first, private, and focused on technical remediation options.
What The Research Supports
It supports early technical triage. A public-page snapshot can identify obvious HTML-level signals such as missing language, heading issues, image alternative problems, unlabeled forms, weak link names, iframe title gaps, and viewport setup.
It supports manual review for important workflows. Lawsuits and demand letters often focus on real user paths: product discovery, forms, cart, checkout handoff, documents, account access, booking, and support.
It supports maintenance. Web pages change through themes, plugins, apps, product launches, campaigns, PDFs, and scripts. A one-time fix can decay unless the business keeps review, remediation, and evidence habits.
What The Research Does Not Prove
It does not prove that any single website is legally noncompliant. Legal exposure depends on the complaint, jurisdiction, website facts, business context, user experience, and counsel's analysis.
It does not prove that an automated scan, widget, plugin, audit, accessibility statement, or VPAT will end a lawsuit. Those can be parts of a responsible technical workstream, but they should not be described as guaranteed legal fixes.
It does not make public shaming acceptable. PACER-derived names, case captions, docket numbers, and personal details should not be turned into public marketing proof.
Practical Takeaway For Sued Businesses
Talk to counsel first, preserve the complaint and current site evidence, avoid broad public compliance promises, and organize a technical packet that developers and providers can act on.
The strongest technical packet usually includes the public URL, cited paths, platform, current accessibility statement, scan output, manual-review notes, confirmed barriers, remediation owners, target dates, and evidence of follow-up review.
When appropriate and with consent, provider options may include audit, monitoring, remediation workflow, accessWidget, accessFlow, accessServices, VPAT/ACR support, file/PDF accessibility, user testing, and litigation-support resources described by accessiBe's public materials.
Frequently asked questions
Is this legal advice?
No. This is a research and technical-remediation synthesis. A business named in a lawsuit or demand letter should speak with qualified counsel.
Why compare WebAIM, Seyfarth, UsableNet, PACER, and NOS 446 together?
They answer different questions: technical prevalence, federal filings, broader market lawsuit trends, case search context, and civil cover-sheet classification. The useful insight comes from comparing their limits.
Does this prove a website needs accessiBe?
No. It explains why technical triage matters. accessiBe may be one provider option when the visitor separately consents to partner follow-up.