WebAIM Million Report 2026 on the state of Web Accessibility

The WebAIM Million report has become a key barometer for the state of web accessibility. For the eighth year in a row, WebAIM has automatically analysed the home pages of the one million most popular websites worldwide using the WAVE engine. The 2026 edition offers a clear—sometimes worrying—snapshot of digital accessibility, while also highlighting simple, concrete actions that teams can take.

WebAIM Million: A Thermometer for Accessibility

WebAIM (Web Accessibility In Mind) is a non-profit organization based at Utah State University. Since 1999, it has provided services, tools, and training to improve web accessibility. The WebAIM Million Page Report is one of its flagship initiatives: every year, an automated test is run on the home pages of one million of the most-visited websites, providing a robust picture of the true state of accessibility on the web.

This approach is not meant to capture everything: it only records errors that can be detected automatically, but those are precisely the ones that tend to have a significant impact on users and a high likelihood of violating WCAG 2.2 criteria (A and AA levels). In other words, if the report finds a lot of issues, the full reality—including non-detectable issues—is even worse.

Accessibility Backsliding After Years of Progress

One finding that particularly stood out for our team is the overall backsliding observed in 2026. Between 2019 and 2025, the results showed gradual improvement: each year, the average number of errors dropped slightly, and accessibility seemed to be trending in the right direction. In 2026, that trend reverses.

On average, each home page analysed now has 56.1 detectable accessibility errors, up from 51 the previous year. That’s an increase of just over 10% in a single year. At the same time, 95.9% of pages have at least one error that violates WCAG 2, up from 2025. This is especially surprising given that accessibility rules and standards are gaining visibility and importance worldwide.

This is all the more concerning because the sites analysed are among the most popular and heavily used on the web. When accessibility regresses on these major platforms, the impact on people with disabilities is substantial.

A Bright Spot for Canada and France

Amid this fairly dark picture, one positive trend is worth highlighting: websites using the .ca and .fr top-level domains have, on average, fewer errors than the rest of the sample. In other words, Canadian and French sites generally perform better than the global average in accessibility terms.

This is by no means a guarantee of compliance, but it is an encouraging signal. It likely reflects the combined effect of stronger regulatory frameworks, rising accessibility expectations in the public sector, and the work of teams who are gradually integrating accessibility into their digital projects. Even so, there is still a long way to go, including in countries that are slightly ahead of the curve.

Growing Complexity and the “Black Box” Effect of Technology

A recurring theme in the report—and in our discussion—is the growing complexity of web pages. The home pages analysed now contain an average of 1,437 HTML elements, a jump of over 22% in a single year and nearly double the number from seven years ago. The more elements, integrations, scripts, and components a page has, the harder it becomes to maintain a clear view of what’s happening and to keep accessibility under control.

This complexity is closely tied to the heavy use of third-party platforms and services: content management systems (CMS), e‑commerce platforms, JavaScript frameworks, UI libraries, analytics tools, ad networks, and more. On top of that, a newer trend has taken off in the past few years: AI-assisted coding, sometimes called “vibe coding.” Generating code from prompts can speed up development, but if quality and accessibility aren’t systematically checked, it can easily introduce new errors.

The report shows a clear correlation: the more complex a page is, the more accessibility errors it tends to have. This doesn’t mean CMSs or frameworks should be avoided—used well, they can actually make accessibility easier—but it is a reminder that stacking technology on top of technology without a clear strategy comes with a real accessibility cost.

E‑Commerce: 33% More Errors Than Average

Among the data points we discussed in our meeting, one statistic was especially striking: e‑commerce platforms have about 33% more errors than the overall site average. In practical terms, shopping online is significantly less accessible than many other types of web content.

This is troubling at a time when online shopping is a central part of daily life. If e‑commerce sites remain technically sophisticated and visually polished but structurally inaccessible, the consequences are very concrete: carts that can’t be completed by keyboard, forms that don’t make sense to a screen reader, checkout steps that are impossible to reach, and so on. In this context, accessibility is not a “nice-to-have”—it defines whether people can access goods and services at all.

Errors That Keep Showing Up—and Could Be Avoided

Despite the diversity of technologies and sectors, the 2026 report confirms that most problems are concentrated in a small set of recurring issues. A handful of error types account for the vast majority of detected problems. Three of them were highlighted in our meeting as “quick wins” that any team can tackle:

1. Alt text for images
   A large share of the issues identified involve images without alt text or with poor-quality alt text (generic terms, file names, copy‑pasted content, and so on). Yet, most CMSs and authoring tools already provide a field for alt text. Supplying meaningful text alternatives is a simple, low-cost fix that significantly improves the experience for people using screen readers—and it helps with search engine optimization as well.
2. Ambiguous or empty links
   The report notes how frequent ambiguous links (“click here,” “read more,” “more”) and empty links (for example, a link that only contains an icon or an image with no alt text) are. Again, this is easy to address: use descriptive link text that explains the destination, and make sure links are never empty. This is good practice both for accessibility and SEO.
3. Insufficient text contrast
   The most widespread problem—and one of the easiest to fix—is insufficient colour contrast for text. Light text on light backgrounds, or brand-driven colour combinations that look stylish but are hard to read, show up everywhere. Even though simple tools exist to check and tweak contrast, many sites still prioritize aesthetics over legibility. This is especially critical on mobile devices, where screen size and ambient light add extra challenges.

By focusing on these three areas—alt text, explicit links, and sufficient contrast—organizations can already remove a large number of barriers across many different platforms.

ARIA and Advanced Code: When Tools Outrun Skills

The 2026 report also highlights a sharp increase in the use of ARIA (attributes that add semantic information for assistive technologies). On average, pages now include more than 133 ARIA attributes, a number that has grown more than sixfold since 2019. Used well, this toolkit could dramatically improve how complex interfaces are understood. But the data show the opposite: pages that use ARIA tend to have many more errors than those that don’t.

This mirrors what we often see in real projects: adding ARIA everywhere without a deep understanding of how it works often creates interfaces that are more fragile, harder to maintain, and more likely to break the experience for people using screen readers. Menus declared with role="menu" but not behaving like real menus, misplaced aria-hidden="true" attributes, or an overuse of tabindex can all make navigation more confusing instead of improving it.

The lesson here is straightforward: before layering advanced attributes on top of everything, teams need to get the HTML fundamentals right (structured headings, properly labelled forms, clear landmarks) and only add ARIA where it’s really needed and well understood.

Turning Findings into Concrete Action

By the end of the report presentation and our discussion, three action areas emerged as powerful levers for improving the accessibility of digital platforms:

• Provide meaningful, consistent alt text for images.
• Ensure link text is explicit, understandable out of context, and never empty.
• Check and fix text contrast so content is readable on all screens.

These actions are simple, low-cost, and highly effective. They can be integrated quickly into design and development workflows, whether for existing platforms or new projects.

The goal is clear: to help shift the trends we see in the WebAIM Million in the right direction and to ensure that the sites we build and maintain today contribute to a web that is truly accessible to everyone.

The 2026 report sends a strong message: technical complexity is growing faster than accessibility quality. To reverse that trend, it’s not enough to add more code layers or rely on “magic” tools. We need to get back to basics, build accessibility in from the start, and treat these “small” fixes—alt text, clear links, sufficient contrast—as essential requirements, not optional extras.

Taking Action

To support teams in this work, we developed a practical guide to accessibility across the entire project life cycle. The guide provides concrete checkpoints for each stage—from strategy and content to design and development—so that accessibility is not pushed to the end of the process or treated as an afterthought.

We also offer digital accessibility support services in Québec, Ontario, and France, including audits, training, project coaching, and guidance on selecting and configuring technologies. Tell us about your project!