Accessibility Audits Miss the Real Barrier: Screen Reader Users Speak

One in Four Adults Has a Disability—Yet Most Websites Fail Them

In the United States, about 1 in 4 adults reports having a disability (WebAIM). That is not a niche audience; it is a quarter of your potential customers, readers, or users. But look at the WebAIM Million's latest automated scan of one million home pages: 95.9% have detectable WCAG 2 failures, averaging 56.1 errors per page (WebAIM Million). Automated tools are not perfect—they miss many real-world barriers—but even by their own limited lens, the web is almost universally broken for people with disabilities. We can and must do better.

The Over-Reliance on Automated Audits Is Our Blind Spot

As practitioners, we love automated checkers. They are fast, cheap, and produce tidy reports. But they only catch a fraction of what makes a site usable with assistive tech. The most common errors—low contrast (83.9% of home pages), missing alt text (53.1%), unlabeled form inputs (51%)—are easy to spot automatically (WebAIM Million). Yet these are just the tip of the iceberg. Screen reader users consistently cite CAPTCHA as the most problematic item, and those with disabilities were twice as likely to rank it as a top problem (WebAIM Screen Reader User Survey). No automated tool can tell you if your CAPTCHA is truly accessible; it takes human testing. The WebAIM Million found that pages with ARIA attributes actually had more errors on average (59.1) than pages without them (42)—a clear sign that sloppy ARIA, often added to “fix” accessibility, makes things worse (WebAIM Million). We need to stop treating automated scores as the finish line and start treating them as a starting point for real user testing.

What Screen Reader Users Actually Want: Simpler, Not Fancier

When asked what would improve their web experience the most, 85.9% of screen reader users said better websites, not better assistive technology (WebAIM Screen Reader User Survey). This is a wake-up call. We don't need to invent new gadgets; we need to make our existing content work with the tools people already have. The vast majority—91.3%—use a screen reader on a mobile device (WebAIM Screen Reader User Survey), yet many sites still have desktop-only navigation that breaks on mobile. And 71.6% of screen reader users first navigate by headings to find information on a long page (WebAIM Screen Reader User Survey). That means your heading structure is your primary navigation. If it's a mess, users are lost. The fix is not more complex ARIA or a fancy widget; it's semantic HTML and clean, descriptive headings. As one practitioner put it, “If you can't navigate by headings, you can't navigate.” That's the real-world impact of accessibility.

Countering the “We Don't Have the Budget” Excuse

You might think, “We're a small team; we can't afford full user testing with screen readers.” But consider the cost of doing nothing. Web accessibility lawsuits in the U.S. reached 3,117 in 2025, up 27% from the previous year (WebAIM Screen Reader User Survey). Legal fees alone dwarf the cost of proactive fixes. More importantly, the World Health Organization estimates that over 2.5 billion people need assistive technology, a number projected to rise to 3.5 billion by 2050 (WHO). That's a massive audience you're shutting out. And the WHO notes that about 90% of people who need assistive tech don't have access to it (WHO)—but that's a global figure; in wealthy countries, access is higher, meaning your users probably do have screen readers. They just can't use your site. There are free tools like NVDA, an open-source screen reader available in over 55 languages and used in more than 175 countries (NV Access). You can download it today and start testing. No excuses.

Practical Steps: Start with Headings and Alt Text

Here's a quick tip: Turn off your monitor, and try to navigate your homepage using only a screen reader and your keyboard. If you can't find the main content within 30 seconds, your headings are failing.

To make real progress, follow these three steps:

• Fix the low-hanging fruit: add alt text to images, label form inputs, and ensure sufficient color contrast. These six error types account for 96% of all detected errors (WebAIM Million).
• Structure every page with a logical heading hierarchy (h1, h2, h3) that mirrors the visual hierarchy. Test it with a screen reader.
• Include people with disabilities in your usability testing. The WebAIM survey found that 86.1% of screen reader users run their primary desktop screen reader on Windows (WebAIM Screen Reader User Survey)—so test on Windows with NVDA or JAWS, not just on Mac with VoiceOver.

Remember, WCAG 2.2 provides the technical standards, but it's not a substitute for human judgment (W3C). Automated tools are a safety net, not a solution. The most important thing to remember: accessibility is not a checklist; it's a practice of empathy and iteration. Start small, but start now.

Sources

• WebAIM Screen Reader User Survey - https://webaim.org/projects/screenreadersurvey10/
• WebAIM Million - https://webaim.org/projects/million/
• World Health Organization - https://www.who.int/news-room/fact-sheets/detail/assistive-technology
• NV Access - https://www.nvaccess.org/about-nv-access/
• W3C Web Accessibility Initiative - https://www.w3.org/WAI/standards-guidelines/wcag/