Every year, WebAIM analyzes the top one million home pages on the web and scores them against WCAG 2 accessibility standards. This year’s results should alarm anyone who runs a website: accessibility is getting worse, not better. After six consecutive years of modest improvement, the 2026 WebAIM Million report found that errors are up, failures are up, and the average page is now more broken for disabled users than it was a year ago. For WordPress site owners trying to stay on the right side of ADA law, those numbers carry real legal weight.
What the 2026 WebAIM Million Report Found
The headline number: 95.9% of home pages tested had detectable WCAG 2 failures — up from 94.8% the year before. That reversal is significant. From 2019 to 2025, the failure rate had been inching downward each year, suggesting the industry was slowly making progress. The 2026 data erases that narrative entirely.
The average number of distinct accessibility errors per page climbed to 56.1, up from 51 in 2025. That’s a 10% increase in a single year. Page complexity is partly to blame — the average home page now contains 1,437 elements, a 22.5% jump in one year — but complexity alone doesn’t explain why so many sites are failing on the same basic issues year after year.
Perhaps most striking: only 4.1% of the one million pages tested were free of automatically-detectable WCAG errors. That’s not 4.1% of the web being fully accessible — automated tools only catch a fraction of real-world barriers — but it does mean that 95.9% of sites have problems visible enough for a scanner to flag without any human review.
The Six Failures That Account for 96% of All Errors
The report reinforces something accessibility professionals have been saying for years: the same handful of problems keep showing up, over and over, across nearly every site. Six error types account for 96% of all detectable failures:
- Low-contrast text — found on 83.9% of pages (up from 79.1% in 2025). The average page has 34 distinct instances of text that doesn’t meet WCAG AA contrast ratios — up 15% from last year.
- Missing image alt text — 53.1% of pages have at least one image with no alternative text, leaving screen reader users with no way to understand what the image conveys.
- Missing form labels — 51% of pages have unlabeled form inputs. A field without a label is invisible to assistive technology; users may not know what they’re supposed to type.
- Empty links — 46.3% of pages contain links with no discernible text, meaning a screen reader announces “link” with nothing to describe where it goes.
- Empty buttons — 30.6% of pages have buttons with no text or accessible label. A button that says nothing tells a keyboard or screen reader user nothing.
- Missing document language — 13.5% of pages don’t declare a language attribute on the HTML element, which prevents screen readers from using the correct pronunciation rules.
Every one of these failures is fixable. None of them requires advanced development skill. Yet collectively they are present on the overwhelming majority of pages on the web — including, statistically speaking, a large share of WordPress sites.
Why Are Things Getting Worse?
The report doesn’t offer a single explanation, but several factors are widely cited by accessibility researchers.
More third-party content, less control
Modern websites rely heavily on scripts, widgets, and embeds from third-party vendors. Chat widgets, review plugins, marketing tools, social feeds — all of them inject content into your page that you didn’t write and may not be able to directly control. When a third-party widget adds contrast-failing text or unlabeled buttons, that failure shows up in your audit results regardless of how carefully you built the rest of the site.
AI-generated content that skips accessibility basics
As more sites use AI tools to generate or modify page content, the accessibility of that content depends entirely on whether the tool was trained to output accessible markup. In practice, AI-generated code and copy frequently omits alt text, uses poor heading structure, and produces contrast-failing color choices. Faster content production can mean faster error accumulation if accessibility isn’t baked into the workflow.
Overlays create a false sense of security
Accessibility overlay tools — scripts that add a floating widget to a site and claim to “fix” accessibility automatically — have proliferated in recent years. Multiple studies, including testimony from disability organizations, have shown that these tools do not resolve the underlying code issues that automated scans detect. Worse, they may give site owners the impression that they’re covered when they’re not. The rising error counts in the WebAIM report suggest that overlays are not bending the curve in any meaningful direction.
What This Means for Your WordPress Site
The six error categories above aren’t abstract — they map directly to things that happen on WordPress sites every day. A theme that ships with low-contrast buttons. A contact form built without proper label markup. A gallery plugin that doesn’t prompt for alt text. An icon font that renders buttons with no visible label. These aren’t edge cases; they’re defaults in a large share of commercially available WordPress themes and plugins.
From a legal standpoint, the WebAIM data matters because courts and plaintiffs’ attorneys use the same automated criteria to identify targets. ADA website lawsuits topped 3,100 federal filings in 2025, an 8% increase from 2024, and the vast majority involve exactly the kind of detectable errors the WebAIM report measures. A site that fails on low contrast, missing alt text, and unlabeled form fields is a site that’s easy to flag in a pre-litigation screen.
The good news is that the six failure types dominating the WebAIM results are also among the most fixable. You don’t need a complete redesign to address most of them. You need a scanner that can find them accurately, and a workflow for fixing the underlying code — not just styling over them.
Running the Numbers on Your Own Site
Before you can fix anything, you need to know what’s actually broken. A few practical steps:
- Run an automated scan against your home page and a representative sample of inner pages. Focus on the six error types listed above — they’re where the density is highest and where you’ll get the most improvement per fix.
- Check your color contrast on buttons, body text, links, and any text overlaid on images. WCAG AA requires a contrast ratio of 4.5:1 for normal text and 3:1 for large text (18pt+ or 14pt+ bold).
- Audit your images — both in content and in your theme — for missing or generic alt text. Decorative images should have empty alt attributes (
alt=""); informational images need meaningful descriptions. - Check every form field for a visible, programmatically associated label. Placeholder text does not count as a label.
- Test your links and buttons for descriptive text. “Click here,” “read more,” and icon-only elements are common failures.
Keep in mind that automated scans catch roughly 30–40% of real-world accessibility barriers. A clean automated result is a starting point, not a finish line. Manual testing — particularly keyboard-only navigation and a quick pass with a screen reader — will surface issues that no scanner can detect.
Take Action
The 2026 WebAIM Million report makes one thing clear: the accessibility problem is not self-correcting. Errors are increasing, not decreasing, and the same fixable issues dominate year after year. If you run a WordPress site, now is the time to find out where yours stands. LEWCA’s free WordPress plugin includes a WCAG scanner that flags real code-level issues — the same categories WebAIM tracks — and an accessibility toolbar your visitors can use to adjust the experience to their needs. LEWCA Pro adds AI-powered code fixes, scheduled scanning, and compliance reports so you can track progress over time. Unlike overlay tools, LEWCA surfaces the actual errors in your markup so you can fix them properly — which is the only approach that holds up when it counts.