The 2025 WebAIM Million Report: Why Web Accessibility Isn’t Getting Better Fast Enough
After seven years of tracking the web’s accessibility health, the 2025 WebAIM Million report delivers a troubling message: we’re improving, but nowhere near fast enough to meet the needs of the 1.3 billion people worldwide living with disabilities.
Key Findings at a Glance
Before diving deep, here’s what every web professional needs to know:
- 94.8% of the top one million websites fail basic accessibility standards
- 51 detectable accessibility errors per homepage on average (down from 56.8 in 2024)
- 79.1% of sites have low contrast text that people with visual impairments cannot read
- Web pages grew 7.1% more complex in one year, adding elements faster than accessibility improves
- ARIA usage exploded 18.5% in one year, but sites with ARIA averaged 57 errors versus 27 without it
The bottom line: While we’re seeing modest improvements in error rates, the web is simultaneously becoming more complex, more reliant on JavaScript frameworks, and harder for people with disabilities to navigate. For the 61 million Americans with disabilities and billions more worldwide, the digital world remains unnecessarily difficult to access.
Why This Report Matters
The WebAIM Million report isn’t just another accessibility study—it’s the most comprehensive annual snapshot of web accessibility we have. Since 2019, WebAIM has analyzed the homepage of the top one million websites using automated testing via the WAVE accessibility evaluation engine.
These aren’t obscure websites. This is the internet that matters: government services, healthcare portals, e-commerce platforms, news sites, educational resources, and business services that people depend on daily. When 94.8% of these critical sites fail accessibility standards, we’re not talking about edge cases—we’re talking about systemic exclusion.
Who WebAIM Is and Why Their Research Is Authoritative
WebAIM (Web Accessibility In Mind) is a non-profit organization based at Utah State University’s Center for Persons with Disabilities. For over two decades, they’ve been at the forefront of web accessibility research, training, and tool development.
What makes their methodology trustworthy:
- Automated but sophisticated: Uses the WAVE engine to analyze rendered DOM after JavaScript and styles are applied—testing what users actually experience, not just raw HTML
- Comprehensive scale: One million homepages provide statistically significant insights into web accessibility trends
- Consistent methodology: Seven consecutive years of identical testing enables reliable trend analysis
- Transparent limitations: WebAIM openly acknowledges that automated testing catches only a subset of accessibility issues—the real numbers are likely worse
Their annual survey of screen reader users provides complementary qualitative data that helps interpret these quantitative findings. When WebAIM reports trends, the accessibility community listens.
The Critical Findings: What the Data Reveals
The Six Issues Dominating Web Accessibility Failures
96% of all detected errors fall into just six categories. Fix these, and you’d dramatically improve the web for millions of people:
- Low Contrast Text (79.1% of sites): Text that blends into backgrounds, making content unreadable for people with low vision, color blindness, or anyone viewing screens in bright sunlight. Average of 29.6 instances per page.
- Missing Alternative Text (55.5% of sites): Images without text descriptions leave blind and low-vision users unable to understand visual content. With 58.6 images per homepage on average, and 18.5% missing alt text, that’s 11 inaccessible images per page.
- Missing Form Labels (48.2% of sites): Forms without proper labels prevent screen reader users from completing essential tasks like registration, login, checkout, or contact.
- Empty Links (45.4% of sites): Links with no text content create dead ends for keyboard and screen reader navigation.
- Empty Buttons (29.6% of sites): Buttons without accessible names are invisible to assistive technology—users can’t click what they can’t identify.
- Missing Document Language (15.8% of sites): Pages without language declarations prevent screen readers from using correct pronunciation rules.
These aren’t esoteric technical requirements. These are fundamental building blocks of usable websites, and the majority of top sites are still getting them wrong.
The Complexity Crisis
Here’s where things get concerning for web agencies and development teams: web pages are growing more complex faster than accessibility is improving.
Home page complexity increased 7.1% in just one year (1,173 elements in 2024 to 1,257 in 2025). Over six years, that’s a 61% increase. Meanwhile, error rates dropped only 10.3% year-over-year.
Do the math: we’re adding features and functionality at a pace that far outstrips our ability to make them accessible. For users with disabilities, this means encountering errors on 1 in every 24 page elements.
The Technology Problem
The report reveals troubling correlations between popular technologies and accessibility errors:
JavaScript Libraries: Nearly every popular JavaScript library corresponded with increased errors. jQuery sites averaged 61.1 errors (19.8% above baseline). Sites using Slick carousel: 78 errors. FancyBox: 82.9 errors. OWL Carousel: 81.3 errors.
Frameworks: Bootstrap sites averaged 63.2 errors (23.9% above baseline). Even modern frameworks showed mixed results—React sites averaged 42.4 errors while Vue.js sites hit 58.7 errors.
E-commerce Platforms: Shopify sites averaged 69.6 errors, WooCommerce 75.6, and Magento 85.4—all significantly above the 51-error baseline.
The ARIA Explosion: This deserves special attention. ARIA (Accessible Rich Internet Applications) attributes increased 18.5% in one year and are now nearly 5 times higher than 2019. Pages averaged 106 ARIA attributes in 2025.
Here’s the problem: sites with ARIA present averaged 57 errors versus only 27 errors for sites without ARIA. The more ARIA attributes present, the more errors detected.
ARIA isn’t inherently bad—it’s essential for complex web applications. But the data suggests most developers are using it incorrectly, adding complexity without improving accessibility.
What This Means for Different Stakeholders
For People with Disabilities
The hard truth: despite seven years of awareness and advocacy, the digital world remains predominantly inaccessible. While 5.2% of sites now pass basic automated checks (up from 2.2% in 2019), 94.8% still fail.
For someone using a screen reader, navigating with keyboard only, or managing visual impairments, this means:
- Abandoning online purchases because checkout forms lack labels
- Missing critical information in images without alt text
- Struggling with low-contrast text that’s physically painful to read
- Encountering broken navigation due to empty links and buttons
- Facing increasing complexity as sites add features that aren’t accessible
The legal landscape is changing with the 2026 federal accessibility mandate, but enforcement may not translate to actual user experience improvements if organizations treat accessibility as compliance theater rather than genuine inclusion.
For Web Agencies and Development Shops
This report should serve as a wake-up call. If you’re building WordPress sites (or any sites), you’re likely producing inaccessible work unless you’re actively testing for and fixing these issues.
The WordPress-specific finding: WordPress sites (241,401 in the sample) averaged 50 errors—1.9% better than the baseline. That sounds good until you realize it’s still 50 barriers per page. WordPress CMS performed middle-of-the-pack among platforms.
More concerning: Elementor sites averaged 51.1 errors (essentially at baseline), while wpBakery sites hit 63.5 errors (24.6% worse than baseline). Page builders—the tools promising easy website creation—are producing less accessible results.
- Your standard workflows are likely producing inaccessible sites
- Popular plugins and themes may be introducing accessibility issues
- Client sites face growing legal risk as enforcement increases
- You need systematic testing, not just hoping for the best
The competitive opportunity: agencies that master accessibility can differentiate themselves in a market where 94.8% of sites fail basic standards. That’s a massive market inefficiency.
For Website Owners and Decision Makers
If you own or manage a website, here’s what you need to understand:
Your site is probably inaccessible. Unless you’ve specifically invested in accessibility testing and remediation, statistical likelihood says you’re among the 94.8% failing basic standards.
Complexity is your enemy. Every plugin, widget, carousel, modal, interactive element, and JavaScript library increases the probability of accessibility issues. The report shows clear correlation between technological complexity and accessibility failures.
“Accessibility overlays” aren’t the answer. While the report doesn’t directly test overlay effectiveness, the accessibility community overwhelmingly rejects these automated “fix it with one line of code” solutions as ineffective and potentially harmful. The fact that 94.8% of sites still fail after years of overlay marketing should tell you something.
Compliance is coming. The 2026 federal deadline for Title II entities means government agencies, public universities, and related organizations must meet WCAG 2.1 Level AA standards. State and local laws are expanding. ADA Title III litigation continues rising.
Testing is essential. You cannot know your site’s accessibility status without testing. Manual audits by experts catch issues automated tools miss, but automated tools like WAVE (used in this study) provide the systematic, repeatable testing needed for ongoing monitoring.
For Accessibility Professionals: The Technical Deep Dive
Now let’s get technical for those working directly in accessibility.
The ARIA Problem Deserves Deeper Analysis
The 18.5% year-over-year increase in ARIA usage combined with higher error rates on ARIA-heavy pages suggests several issues:
- Developers treating ARIA as an accessibility silver bullet rather than a nuanced tool requiring deep understanding
- Framework-generated ARIA that may be incorrect or redundant with native HTML semantics
- ARIA menus introducing barriers (35% of ARIA menus had accessibility issues)
- Overuse of aria-hidden=”true” (18 instances per page average, up 16% from 2024)
The report found 4.5% of sites using role=”menu”, but 35% of those implementations had accessibility barriers. This aligns with the known issue of developers using ARIA menu roles for navigation instead of application-style menus requiring specific keyboard interactions.
With aria-label, aria-labelledby, and aria-describedby averaging 25 instances per page (up 28% in one year), we’re seeing ARIA label proliferation that may indicate:
- Overcompensation for missing native HTML semantics
- Automated injection by JavaScript frameworks
- Misunderstanding of when ARIA labels are appropriate versus native labeling
Heading Structure Continues Declining
While 90.2% of pages now have headings (up from 88.7% in 2024), heading quality remains poor:
- 39% of pages have skipped heading levels (jumping from H2 to H4)
- 16.3% have multiple H1 elements (improved from 16.8%, but still problematic)
- One in every 23 headings represents a skipped level
Given that headings are the primary navigation mechanism for screen reader users (per WebAIM’s Screen Reader User Survey), this represents a fundamental failure in content structure.
The Form Label Crisis
Form inputs average 6.3 per page, with 34.2% unlabeled. That’s 2.1 unlabeled form fields per page on average. For a checkout flow with multiple pages, this compounds into a completely inaccessible experience.
The fact that 48.2% of sites have this issue in 2025—after decades of form labeling being fundamental HTML—indicates this isn’t a knowledge problem. It’s a process problem. Sites are launching without accessibility testing that would immediately catch unlabeled forms.
Low Contrast: The Most Prevalent Issue
79.1% of sites failing contrast requirements, with 29.6 distinct instances per page, points to several root causes:
- Design tools not integrating contrast checking into designer workflows
- Brand guidelines specifying inaccessible color combinations
- Dynamic content (user-generated, CMS-managed) not being tested for contrast
- Overlays of text on images without sufficient background controls
The WCAG 2.2 Level AA requirements (4.5:1 for normal text, 3:1 for large text) are well-established, and tools for checking contrast are ubiquitous. Yet this remains the #1 failure mode.
Alternative Text: A Persistent Problem
With 18.5% of images missing alt text (11 per page) and 13.4% having questionable alt text, nearly one-third of images provide poor accessibility. The report notes 44% of images missing alt text were linked images—creating links with no discernible purpose for screen reader users.
This is particularly concerning because:
- Alt text has been a web standard since HTML 2.0 (1995)
- Every CMS prompts for alt text during image upload
- Every accessibility audit flags missing alt text
Yet here we are, 30 years later, with the majority of sites still failing this basic requirement.
Technology-Specific Insights
Content Management Systems: The spread in average errors by CMS is revealing:
- Divi: 27.6 errors (45.9% better than baseline)
- Webflow: 28.4 errors (44.3% better)
- WordPress: 50.0 errors (1.9% better)
- Elementor: 51.1 errors (0.2% worse)
- wpBakery: 63.5 errors (24.6% worse)
- 1C-Bitrix: 97.0 errors (90.3% worse)
This suggests that platform architecture and default implementations matter significantly. Divi and Webflow’s better performance may reflect more opinionated, controlled design systems.
JavaScript Frameworks: Modern frameworks show mixed results:
- AngularJS: 37.7 errors (26% better)
- Next.js: 38.6 errors (24.2% better)
- React: 42.4 errors (16.8% better)
- Vue.js: 58.7 errors (15.3% worse)
- Angular: 70.7 errors (38.8% worse)
This contradicts the common assumption that React’s component model inherently produces better accessibility. The reality is that framework choice matters less than developer knowledge and testing practices.
Geographic and Linguistic Patterns
The report reveals significant differences by language and TLD:
Best performers:
- .gov sites: 19.6 errors (61.6% better than baseline)
- .edu sites: 23.6 errors (53.7% better)
- English-language sites: 39.8 errors (22% better)
Worst performers:
- Russian-language sites: 84.6 errors (66.1% worse)
- Korean-language sites: 86.4 errors (69.6% worse)
- .ua (Ukraine) domains: 89.1 errors (74.8% worse)
- .cz (Czech Republic) domains: 74.7 errors (46.6% worse)
This suggests cultural differences in accessibility awareness, potentially different regulatory environments, and possibly less mature accessibility tooling for non-Western languages.
The Case for Systematic Accessibility Testing
This report makes an overwhelming case that accessibility testing tools are more critical than ever.
Here’s why:
1. Complexity Is Outpacing Human Review Capacity
With pages averaging 1,257 elements, manual testing alone cannot catch all issues. Accessibility requires systematic, repeatable testing that scales with site complexity.
The 7.1% annual increase in page complexity means sites launched last year have grown measurably more complex. Without automated testing integrated into development workflows, accessibility inevitably degrades between audits.
2. Technology Stacks Introduce Predictable Patterns
The report’s technology correlations reveal that specific libraries, frameworks, and platforms introduce characteristic accessibility issues. Automated testing can catch these patterns:
- ARIA misuse patterns from specific frameworks
- Contrast issues from design system components
- Form labeling gaps from certain plugins
- Carousel implementations that lack keyboard navigation
3. Most Issues Are Detectable and Preventable
The six issue types representing 96% of all errors are all automatically detectable:
- Low contrast: Mathematical calculation
- Missing alt text: Attribute presence check
- Missing form labels: Label association validation
- Empty links/buttons: Content presence verification
- Missing language: Document attribute check
If these issues were caught before deployment, we’d eliminate most accessibility barriers on the web.
4. Manual Testing Alone Has Failed
Seven years of data prove that current practices aren’t working. 94.8% failure rate means:
- Sites launching without any accessibility testing
- Sites launching after manual audits that miss issues
- Sites degrading post-launch without monitoring
- Organizations treating accessibility as one-time rather than ongoing
Manual testing by experts remains essential for nuanced accessibility issues automated tools can’t catch. But manual testing without automated coverage means issues slip through constantly.
5. The Business Case Is Stronger Than Ever
The 2026 federal accessibility mandate creates urgent need for:
- Initial compliance assessment
- Systematic issue identification and prioritization
- Ongoing monitoring to maintain compliance
- Evidence of good faith efforts for legal protection
Organizations need tools that provide:
- Continuous monitoring: Catching issues as they’re introduced
- Prioritized remediation: Focusing on high-impact issues first
- Developer feedback loops: Teaching teams to prevent future issues
- Documentation: Demonstrating compliance efforts
The WordPress-Specific Opportunity
For WordPress professionals, this report highlights both challenges and opportunities.
The Challenge: WordPress sites performed essentially at baseline (50 errors vs. 51 average). That’s not good enough when you’re powering 43% of the web. With page builders like Elementor at baseline and wpBakery 24.6% worse, we’re building accessibility problems into millions of sites.
The Opportunity: The accessibility crisis creates demand for:
- WordPress-native testing tools integrated into admin workflows
- Continuous monitoring as content and plugins change
- Solutions positioned between ineffective overlays ($600-2.4K annually) and unaffordable enterprise tools ($10K-50K+)
- Testing that understands WordPress architecture and common patterns
The fact that .gov and .edu sites perform significantly better (61.6% and 53.7% fewer errors) shows accessibility is achievable when it’s prioritized. These organizations face mandates, allocate resources, and implement systematic processes.
WordPress agencies and site owners need tools that make systematic accessibility testing as routine as SEO or security monitoring.
What Accessibility Professionals Should Tell Stakeholders
If you’re advising organizations on accessibility, here’s how to frame these findings:
For Leadership:
“94.8% of major websites fail basic accessibility standards. Given legal risk from the 2026 mandate and the market opportunity of serving 61 million Americans with disabilities, accessibility must move from ‘nice to have’ to systematic operational requirement. We need testing tools integrated into our development workflow, not just periodic audits.”
For Development Teams:
“Popular technologies correlate with increased accessibility issues. The libraries, frameworks, and platforms we’re using introduce predictable patterns of errors. We need automated testing catching these issues before code review, not discovering them after launch.”
For Content Teams:
“With 18.5% of images missing alt text and 34.2% of form inputs unlabeled, content creation workflows must include accessibility validation. Tools should catch these issues at creation time, not publication time.”
For Procurement:
“Solutions exist across price ranges, but beware ‘automated fixes’ from overlay vendors. The data shows manual expertise remains essential, but automated testing provides the scale needed for continuous monitoring. Look for solutions combining automated detection with expert remediation guidance.”
Where We Go From Here
The 2025 WebAIM Million report delivers a clear message: the web accessibility crisis continues because we’re treating accessibility as an afterthought rather than a systematic requirement.
The encouraging news: Error rates are declining. We’re making progress.
The concerning news: Web complexity is increasing faster than accessibility improvements. For every step forward in error reduction, we take a step back in complexity that introduces new barriers.
The path forward requires:
- Automated testing integrated into development workflows: Catching issues before deployment
- Continuous monitoring of production sites: Identifying issues as they’re introduced
- Developer education on accessible patterns: Preventing issues rather than remediating them
- Technology vendors prioritizing accessibility: Frameworks, CMSs, and platforms must produce accessible output by default
- Cultural shift from compliance to inclusion: Understanding accessibility as user experience, not just legal requirement
The accessibility community has spent decades building standards, creating guidelines, and developing best practices. The technology exists to build accessible websites. The knowledge exists to do it right.
What’s missing is the systematic application of that knowledge through tools and processes that make accessibility the default rather than the exception.
For web professionals, the opportunity is clear: master accessibility now, because the 94.8% failure rate won’t persist forever. Organizations that develop accessibility expertise and systematic processes today will have significant competitive advantages as enforcement increases and market expectations shift.
The question isn’t whether the web will become accessible. The question is whether you’ll be part of creating that future or scrambling to catch up.
About the WebAIM Million Report: The annual WebAIM Million report analyzes the homepage accessibility of the top one million websites using the WAVE accessibility evaluation engine. The 2025 report represents the seventh consecutive year of this research. Read the full report at WebAIM.org
