Why I Stopped Chasing WCAG Perfection and Started Fixing the Basics

Here's a confession that might get me uninvited from the next a11y meetup: I don't care about WCAG AAA compliance. I never have, and I'm starting to think you shouldn't either. The web is drowning in inaccessible code, and the industry's obsession with ticking every box is a distraction from the work that actually moves the needle. The data is clear: the most common accessibility failures are boring, repetitive, and fixable without a PhD in assistive tech. So let's stop chasing the perfect score and start fixing the basics that affect real people every single day.

Isn't WCAG the gold standard? Why not just follow it to the letter?

WCAG is a useful framework, sure, but it's not the finish line. The WebAIM Million 2026 analysis found that 95.9% of home pages have detectable WCAG 2 failures, averaging 56.1 errors per page. That's not because developers are lazy or evil; it's because the guidelines are massive and often abstract. WCAG 2.2 alone defines 86 success criteria across four principles, with 31 at Level A, 24 at Level AA, and 31 at Level AAA. If you're a small team, where do you even start? The answer isn't to aim for AAA—it's to fix the six categories that account for 96% of all detected errors. Low contrast text, missing alt text, unlabeled form inputs, empty links, empty buttons, and missing document language. That's where the pain is. That's where you'll get the biggest bang for your buck.

Do I really need to buy expensive screen readers to test my site?

This is the myth that won't die: that accessibility testing requires a budget for JAWS and a lab full of assistive tech. In reality, the most widely used screen reader among WebAIM survey respondents is NVDA, a free, open-source tool for Windows that's been translated into over 55 languages and used in more than 175 countries. Meanwhile, Apple's VoiceOver is built into every iPhone, iPad, and Mac at no extra cost. You don't need a $1,000 license to understand how a blind user experiences your site. Download NVDA, turn on VoiceOver, and spend an hour navigating your own homepage. You'll learn more than any automated audit will tell you. And if you're on Windows, don't overlook Narrator—it's free and already there. Sure, JAWS holds a 40.5% share of primary desktop screen reader use, but NVDA is right behind at 37.7%, and the gap is closing. The tools are accessible; your mindset is the barrier.

If I add ARIA attributes, does that make my site accessible?

No, and this is a dangerous misconception. ARIA is not a magic wand. The WebAIM Million found that home pages with ARIA present averaged more errors (59.1) than pages without ARIA (42). That's stunning. Adding ARIA incorrectly can actually make things worse, because screen readers will announce nonsense that confuses users. The reality is that most ARIA is unnecessary if you use native HTML elements correctly. The fact that the million home pages had over 133 ARIA attributes on average, up 27% in one year, suggests we're overusing it as a band-aid. Before you sprinkle role="button" on a div, ask yourself: why isn't it a ? Fix the semantics first, and you'll find you need far less ARIA than you think.

Why do screen reader users still complain about CAPTCHA? Isn't there a better way?

CAPTCHA remains the most problematic item for screen reader users, and respondents with disabilities were twice as likely to rank it as problematic. We've known this for years, yet it persists. The irony is that CAPTCHA is supposed to keep bots out, but it locks humans out too. I'm not saying kill all CAPTCHAs tomorrow, but if you're using a visual puzzle, you're discriminating against 91.3% of screen reader users who use a mobile device. There are accessible alternatives—honeypots, logic questions, or even just a simple checkbox with proper labeling. But if you must use CAPTCHA, at least ensure it has an audio alternative that actually works. The fact that 85.9% of screen reader users say better websites would have a bigger impact than better assistive technology tells you the burden is on us, not on them.

Is accessibility only for people with permanent disabilities?

This is the biggest myth of all. Accessibility is for everyone. The WHO estimates that over 2.5 billion people currently need assistive technology, and that number is projected to rise to 3.5 billion by 2050. That includes older people, people with temporary injuries, and people in noisy environments where captions are a lifesaver. Consider this: about 1 in 4 US adults report having a disability, and 8.29 million Americans had a vision disability in 2023. But think about the 1 billion young adults at risk of permanent hearing loss due to unsafe listening practices. Accessibility isn't a niche; it's a spectrum that touches all of us at some point. When you build with accessibility in mind, you're not just checking a box—you're future-proofing your content for yourself, your parents, and your future self.

So here's my takeaway: stop chasing the perfect WCAG score and start fixing the glaring errors that plague 96% of home pages. The WebAIM Million shows that low contrast text alone appears on 83.9% of home pages, missing alt text on 53.1%, and missing form labels on 51%. These are easy wins. Download a free screen reader, test your site, and fix the basics. And for the love of all that is accessible, stop using CAPTCHA without an accessible alternative. The web will be a better place for it.

Sources

• WebAIM Million - https://webaim.org/projects/million/
• WebAIM Screen Reader User Survey - https://webaim.org/projects/screenreadersurvey10/
• World Health Organization - https://www.who.int/news-room/fact-sheets/detail/assistive-technology
• NV Access - https://www.nvaccess.org/about-nv-access/
• Apple Accessibility - https://www.apple.com/accessibility/vision/