Why Your Website Is Failing Screen Reader Users: A Field Guide to Fixing It

Here's a number that should stop you cold: 95.9% of home pages have detectable WCAG failures (WebAIM Million). That's nearly every website on the internet, including yours. And it's not just a compliance checkbox; it's a barrier for the 2.5 billion people who need assistive technology (World Health Organization). As practitioners, we see the same mistakes over and over. Let's walk through a real scenario and fix it.

The Scenario: You're Redesigning a Local Government Website

Imagine you're the digital lead for a mid-sized city. Your mayor wants a new website, and you've been asked to ensure it's accessible. You've heard about WCAG, but you're not sure where to start. You know that 1 in 4 US adults has a disability (WebAIM), and that federal lawsuits hit 3,117 in 2025 (WebAIM). But more importantly, you know it's the right thing to do.

You start by testing with a screen reader. You download NVDA, the free, open-source screen reader (NV Access), and listen to your homepage. It's a mess. The screen reader reads "link, link, link" because images lack alt text. You can't find the navigation because there are no headings. This is exactly what 71.6% of screen reader users experience when they try to navigate a lengthy page by headings (WebAIM).

So, here's our field-tested plan, based on the data.

Step 1: Headings Are Your Best Friend

First, fix your heading structure. Screen reader users rely on headings to scan content. In fact, 71.6% of them first navigate through headings (WebAIM). That means your page should have a logical hierarchy: one H1, then H2s for major sections, H3s for sub-sections. Don't skip levels. Don't use headings for styling. If you do this one thing, you'll immediately improve the experience for 7 out of 10 screen reader users.

But headings alone aren't enough. The WebAIM Million found that the most common errors are low contrast text (83.9%), missing alt text (53.1%), and missing form labels (51%) (WebAIM Million). These are easy fixes, but they persist. On your city website, you have forms for permit applications. If those inputs don't have labels, a screen reader user can't know what to type. That's a failure.

Step 2: Captions and Transcripts for Everyone

Now, think about video content. You have videos of city council meetings. Without captions, you're excluding the 1.5 billion people with hearing loss (World Health Organization). But captions aren't just for them; they help everyone. The Telecommunications Act of 1996 required captions on TV, and we should carry that mindset to the web (Annenberg Public Policy Center). Provide transcripts, too. A transcript is a text version of the video, and it's useful for everyone, including search engines.

And don't forget audio description. For users who are blind, visual information in videos is inaccessible without it. The Described and Captioned Media Program, funded by the U.S. Department of Education, creates accessible educational media, and they show that it's possible (Described and Captioned Media Program).

Step 3: Test with Real Users, Not Just Automated Tools

Automated tools are a good start, but they miss a lot. The WebAIM Million found that home pages with ARIA attributes actually had more errors (59.1) than those without (42) (WebAIM Million). That's because ARIA, when used incorrectly, can make things worse. So, get real screen reader users to test your site. Listen to their feedback. It's humbling, but it's the only way to truly understand.

Also, consider the cost of inaction. The global productivity loss from vision impairment alone is $411 billion annually (World Health Organization). That's a huge economic burden, and much of it is avoidable. By making your website accessible, you're not just helping individuals; you're helping the economy.

The Bottom Line: Start Now, Iterate, and Never Stop

We can't fix everything overnight, but we can start. The data shows that government sites have fewer errors (42.4 per page) than the average (56.1) (WebAIM Million). That's because they're under legal pressure. But you don't need a lawsuit to do the right thing. The U.S. Department of Justice has made it clear that the ADA applies to websites (ADA.gov). So, start with a simple audit. Fix the headings, add alt text, label your forms, caption your videos. Then test with a screen reader. You'll be surprised how quickly you can make a difference.

The single most important thing to remember: accessibility is not a one-time project; it's a continuous commitment. And the payoff is enormous: you're opening your digital doors to billions of people.

Sources

• WebAIM Million - https://webaim.org/projects/million/
• World Health Organization - https://www.who.int/news-room/fact-sheets/detail/assistive-technology
• WebAIM Screen Reader User Survey - https://webaim.org/projects/screenreadersurvey10/
• NV Access - https://www.nvaccess.org/about-nv-access/
• ADA.gov - https://www.ada.gov/resources/web-guidance/
• Described and Captioned Media Program - https://www.dcmp.org/