Accessibility

Web Accessibility Statistics 2026: How Bad Is It, and What the Numbers Mean

Web Accessibility Statistics 2026

Short answer, because this is the question everyone is really asking: web accessibility got worse in 2026, not better. According to the WebAIM Million 2026 report, 95.9% of the top one million home pages had detectable WCAG failures, up from 94.8% the year before, reversing six straight years of slow improvement. The average page carried 56.1 distinct errors, and in the United States more than 4,900 web accessibility lawsuits were filed in 2025. If you run a website, the odds that it has meaningful accessibility problems are overwhelming, and the legal pressure to fix them is climbing.

That is the headline. The rest of this article unpacks the numbers behind it: how bad the failures are, which specific errors cause almost all of them, how the lawsuit landscape actually looks, and what these figures mean for a real business trying to decide where to spend its effort. Every number here is linked to its primary source, because stat pages that cannot be traced are worthless.

How bad is web accessibility in 2026?

The definitive dataset is the WebAIM Million, an annual automated scan of the top one million home pages. Its 2026 edition is the one that broke the trend.

According to WebAIM, across the one million home pages analyzed, 56,114,377 distinct accessibility errors were detected, an average of 56.1 errors per page, and the number of detected errors increased 10.1% from the 51 per page found in 2025. The same report states that 95.9% of home pages had detected WCAG 2 failures, up from 94.8% in 2025, reversing a trend of small improvements in each of the previous six years.

One nuance matters for interpreting that 95.9%. According to WebAIM, because only automatically detectable failures were counted, the true rate of full WCAG 2 A/AA conformance was certainly lower than 4.1%. In plain terms, the real picture is worse than the headline, because automated tools catch only a portion of all barriers. A page with zero detected errors is not proven accessible. It is only a page where an automated scan happened to find nothing.

Why are the numbers getting worse instead of better?

The most cited explanation is complexity. According to WebAIM, the home pages tested contained over 1.4 billion page elements, and the average page had 1,437 elements in February 2026, a 22.5% increase in a single year and nearly double the count from seven years earlier. More markup means more places for a barrier to appear, and the report notes that only 3.9% of page elements carried a detected error, which is a small rate multiplied across a rapidly growing surface.

This is the uncomfortable modern dynamic. Pages are being built faster and bigger, often with heavier JavaScript and more components, while the underlying accessibility discipline has not scaled at the same pace. The result is that even a low per-element error rate produces more total barriers each year.

Which accessibility errors are most common?

Here is the most actionable statistic in the entire report, and the reason accessibility is more tractable than the scary top-line suggests. The failures are not exotic, and they are wildly concentrated.

According to WebAIM, 96% of all detected errors fall into just six categories, and those same six have topped the list for seven consecutive years. The 2026 breakdown, by share of home pages affected, is low contrast text at 83.9%, missing alternative text at 53.1%, missing form input labels at 51%, empty links at 46.3%, empty buttons at 30.6%, and missing document language at 13.5%.

Low contrast is the standout. According to WebAIM, low contrast text below the WCAG 2 AA thresholds was found on 83.9% of home pages, up from 79.1% in 2025, making it the most commonly detected issue, and each home page averaged 34 distinct instances of low contrast text, up 15% year over year. This is a design-token problem, not a hard engineering problem. It is a choice about color values, repeated thousands of times across the web.

The direction of travel is mixed but mostly downward. According to WebAIM, the number of pages with missing alternative text and missing document language decreased since 2025, while low contrast text, missing labels, empty links, and empty buttons all increased. The two that improved, alt text and document language, are both single-decision fixes that content management systems can automate, which hints at why they moved while the design-and-code issues did not.

The practical implication is large. According to WebAIM, users with disabilities would, on average, encounter an error on one in every 26 home page elements. Fixing just these six categories would remove the overwhelming majority of detectable barriers on the web, and none of them requires specialist tooling to find.

Are these errors actually hard to fix?

This is where the statistics turn from discouraging to hopeful, and it is a question worth answering directly because the top-line numbers make the problem sound bigger than the fix. Not one of the six dominant failures is a deep engineering challenge. Low contrast text is a color-value decision that any design tool can check before a line of code is written. Missing alternative text requires a human to decide what an image communicates and type a sentence. Missing form labels are a single attribute in the markup. Empty links and empty buttons usually come from an icon with no accessible name, fixable with one label. Missing document language is a single attribute on the html element.

The fact that the same six issues have led the WebAIM report for seven straight years, according to WebAIM, tells you the barrier is not difficulty. It is that accessibility is rarely asked about at the start of a project, at the design stage, and again before launch. The cost of building these fixes in from the beginning is close to zero. The cost of retrofitting them across a large, complex site after a complaint arrives is not.

How many web accessibility lawsuits are there?

The statistics that get a business's attention are the legal ones, and 2025 was a rebound year after two years of decline.

Two respected trackers count slightly differently, so it is worth citing both. According to the UsableNet lawsuit tracker, plaintiffs filed 4,928 web accessibility lawsuits by the end of 2025, and from 2018 to 2025 plaintiffs filed more than 25,000 lawsuits with digital accessibility complaints. For the federal-court subset specifically, according to the law firm Seyfarth Shaw, plaintiffs filed 3,117 website accessibility lawsuits in federal court in 2025, a 27% increase from the 2,452 filed in 2024, and website cases made up 36% of all federal ADA Title III lawsuits, up from 28% the year before.

The difference between those figures is not a contradiction. UsableNet counts federal plus key state courts, while the Seyfarth number is federal only, which is why any honest stat page keeps the two datasets separate rather than blending them.

Who is actually getting sued?

The pattern matters more than the raw count. According to Seyfarth Shaw, website cases climbed to represent 36% of the 8,667 total federal ADA Title III lawsuits filed in 2025, showing that digital claims are taking a growing share of all disability-access litigation.

Two facts should reshape how a business thinks about its risk. First, being sued once makes you a target again. According to the UsableNet trends analysis, of the more than 5,000 digital accessibility lawsuits filed in 2025, 1,427 targeted companies that had already faced an ADA web accessibility claim. Second, physical presence is irrelevant. According to the same UsableNet analysis, if users in a given state can access your website, courts are allowing cases to proceed, with New York and Florida especially active. A single accessible-looking storefront in one state does not shield a site that anyone, anywhere, can reach.

Do small businesses actually get sued?

Yes, and this is one of the most common misconceptions worth correcting. The mental image of accessibility litigation is a plaintiff going after a giant retailer, but the data shows the pressure spread across company sizes. According to the UsableNet lawsuit tracker, in the first half of 2025, 36% of sued companies had annual revenue exceeding $25 million, up from 33% in 2024, which means the clear majority of defendants were below that threshold. Large companies are increasingly targeted, but small and mid-sized businesses still make up the bulk of the caseload.

There is also a much larger layer of pressure that never reaches a courtroom. Formal lawsuits are the visible tip of the activity. Many businesses first hear about their accessibility exposure through a demand letter, a pre-litigation notice asking for a settlement, and those vastly outnumber filed cases. A business that assumes it is too small to be noticed is working from a picture the numbers do not support.

What these numbers mean for your website

Put the three datasets together and a clear, non-alarmist conclusion emerges. Accessibility failures are nearly universal, they are concentrated in a handful of fixable issues, and the cost of ignoring them is rising in court. That combination is unusual, because it means the highest-impact work is also the most achievable.

There is one more statistic that should shape strategy, and it is about what does not work. A popular shortcut is to install an accessibility overlay, a runtime script that promises instant compliance. The lawsuit data is blunt about the result. According to the UsableNet trends analysis, lawsuits against companies already using accessibility widgets continued to rise month over month in 2025, meaning overlays did not reduce litigation. If you want the full argument on why masking problems at runtime fails both legally and for real users, our sourced position on overlays lays it out, and our plain-English overlay guide covers what they can and cannot do.

The durable path is the opposite of a shortcut: find the real barriers in your own code and fix them at the source, starting with the six categories that cause almost everything. That is exactly what an honest scan is for. You can scan your site with Sitejar for free, up to five pages, no signup, and see which of the common failures actually appear on your pages, each mapped to the WCAG criterion it fails, so you are working from your own numbers rather than the industry average. For the wider context on how these checks read a page and where automation stops, the Sitejar blog goes into the detail.

The bottom line

The web accessibility statistics for 2026 tell a coherent story. According to WebAIM, 95.9% of the top million home pages fail WCAG checks, the average page has 56.1 errors, complexity jumped 22.5% in a year, and six long-standing issues cause 96% of all failures. According to UsableNet and Seyfarth Shaw, US lawsuits reached nearly 5,000 in 2025 with federal filings up 27%, repeat defendants are common, and accessibility overlays did nothing to slow the litigation. The encouraging part hides inside the grim part: because the failures are so concentrated and so fixable, most sites can eliminate the majority of their detectable barriers by addressing a short, well-understood list. The worst move is to paper over the problem. The best move is to measure your own site honestly and fix the source.

Sources

WebAIM, The WebAIM Million 2026

UsableNet, ADA Website Compliance Lawsuit Tracker

UsableNet, ADA Web Lawsuit Trends for 2026

Seyfarth Shaw, Federal Court Website Accessibility Lawsuit Filings Bounce Back in 2025

This article is educational and reflects Sitejar's point of view. It is not legal advice. For your specific situation, consult a qualified attorney.