95.9% of Websites Fail ADA Compliance. Here’s What Actually Gets You Sued

95.9% of home pages had at least one detectable WCAG 2 failure, according to WebAIM’s 2026 Million report, which scans the top one million websites every year using the WAVE accessibility engine. That number is up from 94.8% in 2025, reversing six straight years of gradual improvement.

The average home page now carries 56.1 distinct accessibility errors, a 10.1% jump in a single year, and WebAIM’s own analysis points to a specific cause: rising page complexity and increased reliance on AI-assisted, automated coding practices adding new errors faster than teams are catching them.

That statistic explains why so many sites fail an audit. It doesn’t explain why some of those sites get sued and most don’t. That’s a separate, more specific question, and the answer matters more for anyone evaluating ada website compliance services than the overall failure rate does, because fixing everything WCAG covers is a different project than fixing the handful of things that actually trigger litigation.

Real ada website compliance services have to prioritize accordingly.

What Actually Gets a Company Sued, Not Just Flagged

Federal website accessibility lawsuits hit 3,117 in 2025, up 27% from 2,452 the year before, according to Seyfarth Shaw’s ADA Title III tracking, one of the most established legal trackers of this litigation category. Website cases now make up 36% of all federal ADA Title III filings, a share that keeps growing year over year. Once state courts are included alongside federal filings, industry tracking counts well over 5,000 digital accessibility lawsuits filed in 2025 alone.

The concentration is specific, not evenly spread. E-commerce and other transaction-heavy sites, retail, restaurants, hospitality, healthcare booking, account for the large majority of claims, because the barrier directly prevents someone from completing a purchase, a reservation, or a form, not just from reading content comfortably.

Company size matters too: over a third of companies sued in 2025 reported annual revenue above $25 million, and among the largest e-commerce retailers, more than a third had already faced at least one claim.

The repeat-defendant pattern is the detail that should worry any company treating a single settlement as the end of the problem. Roughly 46% of federal accessibility cases in 2025 named a defendant who had already been sued over similar barriers before.

A settlement that fixes the one issue a specific plaintiff’s screen reader hit, without a broader remediation, is a near-invitation for the next claim, since court filings are public record and plaintiff firms track exactly which companies have already shown they’ll settle.

The Failure Types Behind Almost Every Real Complaint

Lawsuit complaints rarely cite an abstract WCAG violation number. They describe a specific, concrete barrier: a screen reader user who couldn’t tell what a product image was, a keyboard user who couldn’t find or activate a form field, a low-vision user who couldn’t read text against its background. Those concrete barriers map almost exactly onto WebAIM’s own top six error categories, which together account for 96% of all detected errors across the million-site sample:

• Low contrast text, found on 83.9% of home pages, the single most common issue every year since WebAIM started tracking
• Missing alternative text for images, on 53.1% of pages, which is precisely the barrier that turns a product photo into nothing at all for a screen reader user
• Missing form input labels, on 51% of pages, directly blocking the checkout and contact forms most transaction-heavy litigation centers on
• Empty links, on 46.3% of pages, links a screen reader announces with no indication of where they go or what they do
• Empty buttons, on 30.6% of pages, interactive elements with no accessible name at all
• Missing document language declarations, on 13.5% of pages, which breaks correct pronunciation for screen reader users relying on the page’s stated language

None of these require exotic engineering knowledge to fix. They require someone to check for them systematically, on every page that matters to a real user’s path through the site, not just the homepage WebAIM’s own sample measures.

Why Automated Scans and Overlay Widgets Don’t Actually Protect You

WebAIM is explicit about the limits of its own methodology: “absence of detected errors does not indicate that a page is accessible or conformant.” An automated scan catches a meaningful subset of WCAG failures, the ones a machine can reliably detect, and misses the rest entirely, things like whether a custom interactive component actually behaves correctly for a keyboard user or whether an ARIA label accurately describes what an element does.

Overlay widgets, the scripts that promise to make an existing site compliant without touching the underlying code, have an even worse track record specifically against litigation. Lawsuit tracking has found accessibility widget-running companies get sued in every single reporting period, month after month, which is direct evidence that a widget’s presence doesn’t meaningfully deter a claim. The FTC has also taken direct enforcement action against at least one major overlay vendor for deceptively claiming its product could make any website compliant. A widget that scans for surface-level issues cannot fix a genuinely broken form or an inaccessible custom dropdown, and plaintiffs’ counsel increasingly know exactly what an overlay can and can’t actually do.

WCAG 2.2 Audit: What Real Compliance Actually Requires

A genuine WCAG 2.2 audit, the foundation any credible ada website compliance services engagement should start with, combines automated scanning, which is fast and catches the low-hanging fruit, with manual testing that automated tools structurally cannot perform: actual keyboard-only navigation through every critical user flow, screen reader testing with real assistive technology, and a review of custom interactive components against the specific WCAG success criteria that apply to them.

• Automated scanning across every page in a critical checkout or account flow, not just the homepage, since litigation risk concentrates on checkout, booking, and account flows specifically, exactly where ada website compliance services should focus first
• Manual keyboard navigation testing through those same flows, since a large share of real barriers only surface when someone tries to complete a task without a mouse
• Screen reader testing with actual assistive technology, since automated tools cannot verify whether an ARIA label or alt text description is actually accurate and useful, only whether one exists
• A prioritized remediation plan ranked by both WCAG severity and litigation exposure, since not every violation carries equal real-world risk
• Documentation of the audit process itself, since a documented, good-faith remediation effort is meaningfully different from an unaudited site in how a claim typically resolves

ADA Compliant Website Development: Building It In vs. Bolting It On

The most expensive way to achieve ADA-compliant website development is remediating a site after launch, one lawsuit or audit finding at a time. This is the gap most ada website compliance services engagements exist to close. The cheapest way is treating accessible web design as a default requirement from the first wireframe, the same way security or performance gets treated on a well-run engineering team, not a separate workstream added at the end.

That means color contrast checked at the design stage, before a single line of CSS gets written. It means every interactive component- buttons, forms, custom dropdowns- built with a real accessible name and correct keyboard behavior from the start, not patched in during QA. It means treating accessibility testing as part of the same review process that catches other regressions before they ship, not a periodic external audit that finds problems months after they went live.

The Real Choice Isn’t Compliant or Non-Compliant. It’s Proactive or Reactive

WebAIM’s own data shows the honest baseline: nearly every site on the web has real accessibility gaps, and the gap widened in 2026 rather than closing. Seyfarth Shaw’s litigation data shows what happens to a meaningful share of the sites in that 95.9%: over 3,000 federal lawsuits in a single year, concentrated on transaction-heavy sites, with nearly half naming a company that had already been sued once before. Ada website compliance services that focus narrowly on passing an automated scan are solving the wrong problem. The sites that actually reduce their web accessibility lawsuit risk are the ones treating the six most common, well-documented failure types as a baseline requirement, verified by real manual testing, not a checkbox an overlay widget claims to handle automatically.

Frequently asked questions

What do ada website compliance services actually need to reduce lawsuit risk, versus just improving a WCAG score?

Services that combine automated scanning with manual keyboard and screen reader testing on the specific pages tied to real user transactions, checkout, booking, account creation, reduce risk more directly than a general site-wide scan. The best ada website compliance services prioritize by both severity and actual user impact rather than treating every finding as equally urgent.

Does an accessibility overlay widget actually protect a company from an ADA lawsuit?

The evidence says no reliably. Lawsuit tracking has found companies running overlay widgets getting sued consistently across every recent reporting period, and the FTC has taken enforcement action against at least one major overlay vendor for deceptive compliance claims. A widget can flag some surface-level issues but cannot fix a genuinely broken form or a custom component with no accessible name.

What is a WCAG 2.2 audit, and how is it different from an automated scan?

An automated scan, the kind WebAIM’s own Million report uses, catches a meaningful subset of detectable errors quickly but explicitly cannot confirm full conformance. A genuine WCAG 2.2 audit adds manual testing, actual keyboard navigation and screen reader use through real user flows, which is the only way to catch barriers that require human judgment to identify, such as whether an image description is actually accurate rather than merely present.

Which specific accessibility issues show up most often in actual lawsuits?

Complaints typically describe concrete barriers that map to WebAIM’s most common detected failure types: low contrast text, missing alt text on images, unlabeled form fields, and interactive elements like empty links or buttons with no accessible name. These six categories account for 96% of all errors WebAIM detects across a million home pages, and they’re also the barriers most directly described in real litigation complaints.

Is accessible web design more expensive than fixing accessibility after launch?

Considerably less expensive in most cases. Color contrast, proper labels, and correct keyboard behavior are inexpensive to implement during design and development, when they’re simply part of the build. The same fixes become significantly more costly after launch, when they require reworking shipped code, and considerably more costly again once a lawsuit or settlement is involved on top of the remediation itself.

Manali Kabrawala

Project Manager – Full Stack