Skip to main content
Category: Testing and Evaluation

WebAIM Million

Also known as: The WebAIM Million, WebAIM Million report
Simply put

The WebAIM Million is an annual study conducted by WebAIM (Web Accessibility In Mind) that examines the home pages of the top one million websites for accessibility problems. It uses automated testing to detect issues and reports on how common accessibility errors are across the web. Because it relies on automated analysis, it captures only a portion of possible accessibility issues rather than a complete picture.

Formal definition

The WebAIM Million is a recurring, large-scale accessibility evaluation in which WebAIM runs its automated WAVE testing engine against the home pages of the top one million websites and aggregates the results. First published in 2019 and updated in subsequent years including the 2025 and 2026 reports, it quantifies detected WCAG-related errors and the prevalence of pages with such errors. Because the analysis is automated, it detects only the subset of accessibility barriers that automated tools can identify programmatically and does not substitute for manual or assistive technology testing; results should be interpreted as an indicator of common, machine-detectable failures rather than a comprehensive measure of conformance or usability.

Why it matters

The WebAIM Million provides one of the most widely cited data points on the state of web accessibility across a very large sample of high-traffic sites. Because it examines the home pages of the top one million websites using a consistent automated method year over year, it offers a longitudinal view of how common machine-detectable accessibility failures are and whether they are becoming more or less prevalent over time. For accessibility practitioners, legal teams, and business leaders, this kind of aggregate evidence helps establish that accessibility barriers are widespread rather than isolated, which can inform prioritization, budgeting, and awareness efforts.

The report's findings have generally pointed to persistent and, in some editions, worsening trends. The 2026 update reported notable increases in both the number of detected accessibility errors and the number of pages with WCAG-related errors compared to prior analyses, reinforcing that automated accessibility failures remain common on widely used sites. Because these figures are drawn from automated testing, they should be understood as an indicator of common, machine-detectable problems rather than a complete count of all barriers users may encounter.

It is important to interpret the WebAIM Million within its limits. It measures only home pages, only detectable errors, and only through automated analysis, so it does not capture the full accessibility of entire sites, nor does it measure real usability for people using assistive technology. The study is a research and awareness resource, not a conformance certification or legal benchmark, and it should not be treated as legal advice or as a substitute for manual and assistive technology testing.

Who it's relevant to

Accessibility Engineers and Testers
The report offers a benchmark of the most common machine-detectable failures across a large sample of sites, which can help teams anticipate frequent issue types and calibrate their own testing programs. It should complement, not replace, the manual and assistive technology testing needed to evaluate barriers automated tools cannot detect.
Compliance Officers and Business Leaders
Aggregate data from the WebAIM Million can support internal awareness efforts by demonstrating how widespread accessibility errors are on high-traffic sites. It is a research resource for context and prioritization rather than a compliance certification, and it does not establish that any specific site meets or fails a legal or WCAG conformance standard.
Legal Counsel
The study is often referenced to illustrate the prevalence of accessibility barriers, but it is not a legal authority and does not itself define legal requirements. Whether a given site meets obligations under laws such as the ADA depends on applicable statutes, regulations, agency guidance, and case law, which counsel should evaluate independently. This entry is not legal advice.
UX Designers and Developers
The recurring findings highlight that certain error categories remain common across many sites, underscoring the value of building accessibility in from the start. Designers and developers should treat automated findings as a starting point and validate real usability through manual review and testing with assistive technologies.
Researchers and Educators
The WebAIM Million provides a large, consistently gathered dataset useful for studying trends in web accessibility over time. Users should note its scope limitations, home pages only, automated detection only, when drawing conclusions or citing its figures.

Inside WebAIM Million

Annual Accessibility Analysis
The WebAIM Million is a yearly study conducted by WebAIM that evaluates the accessibility of the home pages of the top one million websites, providing a large-scale snapshot of common accessibility issues across the web.
Automated Testing Basis
The analysis is generated using automated accessibility testing tooling, which detects only a portion of possible accessibility barriers. Findings reflect issues that can be programmatically identified rather than a complete manual or assistive technology evaluation.
WCAG-Referenced Failures
Detected errors are commonly categorized against Web Content Accessibility Guidelines (WCAG) success criteria, which are published by the W3C through the Web Accessibility Initiative. The report often highlights recurring categories of detectable failures.
Common Error Categories
The study typically groups detectable issues into frequently occurring categories such as low-contrast text, missing alternative text for images, empty links, missing form labels, and empty buttons, illustrating where automated detection most often flags problems.
Home Page Scope
The evaluation focuses on the home page of each site rather than entire websites, so the results represent a limited entry-point sample rather than a comprehensive audit of each property.
Trend Reporting
Because it is repeated annually, the WebAIM Million allows for year-over-year comparison of detectable accessibility errors, offering a view of whether measurable barriers are increasing or decreasing over time.

Common questions

Answers to the questions practitioners most commonly ask about WebAIM Million.

Does a passing or improving WebAIM Million result mean a website is legally compliant with the ADA?
No. The WebAIM Million is an annual analysis of automated accessibility test results across a large sample of home pages; it measures certain detectable errors, not legal compliance. The ADA is a US civil rights law, and its application to web accessibility has developed through regulation, agency guidance, and case law rather than through any single metric. Automated testing detects only a portion of accessibility issues, so favorable results in this kind of analysis do not guarantee conformance with WCAG, an accessible experience for all users, or immunity from legal claims. Organizations should treat the WebAIM Million as an industry benchmark and consult qualified legal counsel regarding compliance obligations.
Does the WebAIM Million measure the full accessibility of the pages it evaluates?
No. The WebAIM Million reflects what automated testing can detect on home pages, and automated tools identify only a subset of potential accessibility barriers. Many WCAG success criteria require manual review and testing with assistive technologies to evaluate accurately, such as whether alternative text is meaningful, whether keyboard navigation is logical, or whether content is understandable. A page can pass automated checks and still present significant barriers to users, so the analysis is best understood as a broad indicator of common, machine-detectable problems rather than a comprehensive accessibility assessment.
How can teams use the WebAIM Million findings to prioritize their own accessibility work?
Teams can use the analysis to understand which categories of automatically detectable errors are most common across the web and check whether those same categories appear on their own pages. Because the study focuses on home pages and automated detection, teams should treat its findings as a starting point, then extend testing to key user flows, templates, and interactive components using both automated tools and manual, assistive-technology-based evaluation. Prioritization generally weighs the severity of a barrier and how many users it affects rather than relying solely on error counts.
Can the WebAIM Million be used as a target or goal for an accessibility program?
It is generally more appropriate to set goals against a defined technical standard, such as a specific WCAG version and conformance level, than against a benchmarking study. WCAG 2.1 or 2.2 Level AA is the level most commonly cited as a target for websites. The WebAIM Million can provide useful context on how common certain issues are, but because it is limited to automated detection on home pages, it does not represent a conformance target on its own. Programs typically combine a WCAG conformance goal with ongoing manual and automated testing.
What kinds of accessibility issues is the WebAIM Million most likely to surface?
The analysis reflects errors that automated tools can reliably detect on home pages, which commonly include categories such as missing alternative text, low-contrast text, empty links or buttons, missing form labels, and missing document language. These are frequently among the most prevalent detectable issues across large samples. It is less able to surface issues that require human judgment or assistive-technology testing, so teams should not assume that absence of these detectable errors means the page is free of barriers.
Should the WebAIM Million replace an organization's own testing?
No. It is an external, aggregate benchmark of automated results and does not evaluate an individual organization's specific pages, templates, or user journeys beyond what such studies sample. Organizations should conduct their own testing that combines automated scanning with manual review and testing using assistive technologies. This guidance is informational and not legal advice; requirements evolve through regulation and case law, and legal questions should be directed to qualified counsel.

Common misconceptions

A site not flagged in WebAIM Million findings is fully accessible or legally compliant.
The study relies on automated testing, which detects only a portion of accessibility issues. Manual testing and assistive technology testing are required to assess real accessibility, and the absence of detectable errors does not guarantee an accessible experience or immunity from legal claims.
The WebAIM Million measures the full accessibility of each website.
The analysis generally evaluates only home pages using automated tooling. It does not audit entire sites or capture usability barriers that require human judgment, so it is best understood as a large-scale indicator rather than a complete assessment.
The reported error categories represent every type of accessibility barrier that matters.
The categories reflect issues that automated tools can reliably detect, such as contrast, missing alternative text, and form labeling. Many barriers, including keyboard operability nuances, logical reading order, and assistive technology behavior, may require manual evaluation and are not fully captured.

Best practices

Use WebAIM Million findings as a benchmark for common, detectable issues, not as a substitute for a full accessibility audit of your own site.
Supplement automated testing with manual testing and assistive technology testing, since automated tools detect only a portion of accessibility barriers.
Prioritize remediation of frequently occurring detectable errors, such as low-contrast text, missing alternative text, empty links, missing form labels, and empty buttons, while recognizing these are only part of the picture.
Evaluate pages beyond the home page, since the WebAIM Million's home-page focus does not represent the full user journey across a site.
Track accessibility progress over time using consistent testing methods, in the spirit of the study's annual trend reporting.
Consult qualified legal counsel and current agency guidance for compliance questions, as meeting WCAG success criteria or passing automated checks does not guarantee legal compliance.