Global Accessibility Awareness Day (GAAD) turns 15 this week. It should feel like a celebration. Fifteen years of designers, developers, and agencies getting better at building the web for everyone.
Instead, we're marking the anniversary with a regression. The 2026 WebAIM Million report found that 95.9% of homepages have WCAG failures, up from 94.8% in 2025. That single percentage point might not sound like much, until you realize it's the first time in six years the number has moved in the wrong direction. Errors per homepage jumped 10.1%, from 51 last year to 56.1 this year. The average homepage is now carrying 22.5% more elements than it did 12 months ago.
It's easy to blame the tools. But tools don't deploy themselves. The 2026 regression isn't a tool problem, it's a 15-year human and agency process problem that AI-assisted development has made faster, louder, and harder to catch.
Key Points
AI coding assistants have taken most of the blame for the 2026 regression, and it's a convenient story. But if those tools were the actual root cause, we'd expect the failures to show up in WebAIM's crawl to be new. They don't. Missing alt text. Low contrast. Empty links. Mislabeled form fields. ARIA applied where it shouldn't be. These are the same failure modes WebAIM has been cataloging every year since the Million report started.
What changed in 2026 isn't the type of error. It's the volume and the rate at which new issues appear. The 22.5% increase in page elements per homepage isn't causing new accessibility problems. It's producing more of the familiar ones, faster than most teams can catch them.
What changed in 2026 isn't the type of error. It's the volume and the rate at which new issues appear.
That distinction matters because it tells us where the fix actually lives. The pattern underneath the numbers is older than any model released in the last 18 months. It has more to do with how agencies have worked for 15 years than with the tools they've adopted in the last two. To understand what happened in 2026, we have to look at what's been happening since 2011.
Fifteen years of GAAD, and the accessibility story at most agencies still sounds the same. It isn't that agencies don't care. It's those three predictable patterns that quietly shape how accessibility work gets scoped, staffed, and sold. Name them, and you can start working around them.
If you don't know where to start, you usually don't.
Accessibility is a deep, technical discipline. WCAG 2.2 alone lists 86 success criteria across four principles, and the guidance shifts as assistive technology evolves. Very few agencies have a dedicated accessibility role, and even fewer designers or developers receive formal training in it. What teams pick up between projects is often outdated by the time it gets applied. The result is predictable: accessibility work happens inconsistently, reactively, and rarely at the depth the discipline actually requires. It's not a willingness problem. It's a capability problem, and building capability takes years.
If you don't see the issue, you don't fix the issue.
Most agency design reviews happen with five people who all navigate the web the same way. They use a mouse. They can see the screen. They don't rely on screen readers, magnifiers, or keyboard-only navigation. When the users your team never meets are the users being left behind, the problem stays out of view. Roughly 1 in 4 US adults lives with a disability. That isn't a niche audience. It's a quarter of your client's customers, shaped every sprint by decisions your team makes without them in the room.
Still framing accessibility as a nice-to-have when the stakes have become legal.
Most agencies still treat accessibility as a nice-to-have. The regulatory landscape hasn't waited for them. ADA digital lawsuits have hit the mid-market in waves. The European Accessibility Act came into effect in June 2025. B2B procurement forms increasingly require WCAG compliance before a deal advances. The stakes are now legal, financial, and contractual. The clients whose websites end up in a demand letter aren't surprised by the law. They're surprised their agency never told them it applied.
Those three barriers explain 15 years of near-stagnation. They don't, on their own, explain 2026. What they do is set the stage. When you add a 22.5% increase in page elements per homepage on top of three barriers nobody's ever fully solved, the math has only one outcome. Which is the one the 2026 WebAIM Million just recorded.
In an ideal world, every agency would have a dedicated accessibility lead. Designers and developers would cycle through WCAG training every year. Accessibility would be a standing line in every proposal, a required pass in every sprint, and a live metric in every QBR. A handful of agencies already operate this way, and their clients benefit.
Most don't, and for understandable reasons.
In an ideal world:
In today's reality:
The distance between those two columns is where accessibility quietly goes backward. Agencies know they should do more. They can't always build the capability fast enough to keep up with the pace of client work, and the 2026 numbers reflect exactly what happens when that happens.
You don't have to build an accessibility team to run an accessibility program.
Training, in-house capability, and making accessibility part of every design review all still matter. None of that goes away. But ownership without expertise and capability often fails to achieve the necessary level of compliance or protection, and the 2026 WebAIM numbers are the latest proof. Agencies that genuinely care about accessibility are still shipping sites with WCAG violations because the work is outpacing what any in-house team can realistically catch on its own.
AudioEye's platform is built to close that gap. Our AI-driven automation runs on your client's site 24/7, monitoring real user sessions and scanning every page on every interaction. It detects up to 2.5x more issues than other solutions (per third-party Adience testing) and fixes many of them automatically, in real time, without a developer touching the code.
Agencies that treat accessibility as a continuous, platform-level practice ship better sites and keep their clients out of demand letters. For agencies building on Duda’s website-building platform, AudioEye is integrated with the platform your team already uses. You keep shipping at the speed Duda enables. Accessibility keeps pace with every site you launch.
GAAD at 15 was supposed to be a celebration of how far we've come. The 2026 numbers turned it into a checkpoint instead. But checkpoints are where momentum gets rebuilt, and the next 12 months will be written by the agencies that decide to lead.
The agencies that bend the curve won't be the ones with the biggest budgets or the cleverest pitches. They'll be the ones who stop treating accessibility as a launch milestone and start treating it as a continuous practice. Every accessible site they ship is one more person who can book the trip, complete the purchase, read the article, or apply for the job. That's what 15 years of GAAD has been pointing at all along.
And if you're building on Duda, you don't have to figure it out alone.
