Why I'm Done Apologizing for Screen Readers: A Field Report on Accessible Design

Here's a number that should haunt every developer, designer, and product manager: 2.5 billion people currently need assistive technology, and that number is projected to hit 3.5 billion by 2050 (World Health Organization). That's not a fringe population—that's roughly one in three humans on the planet. Yet the latest WebAIM Million analysis found that 95.9% of home pages have detectable WCAG 2 failures, averaging 56.1 errors per page (WebAIM Million). We are failing on a planetary scale, and it's not because we lack the tools or the guidelines. It's because we treat accessibility as an afterthought, a checkbox, a legal compliance issue—not as a fundamental part of good design.

I've been writing about assistive technology for years, and I've come to a blunt conclusion: if you're not testing with screen readers, you're not doing your job. Screen readers are the most common assistive technology for people who are blind or have low vision, and they're not some obscure tool used by a handful of tech-savvy users. In WebAIM's 2024 Screen Reader User Survey, 91.3% of respondents use a screen reader on a mobile device (WebAIM). That's not a desktop-only phenomenon. And 71.6% use more than one screen reader (WebAIM). So when you design for one, you're not covering the bases.

Imagine You're a Product Manager at a SaaS Company

Let's make this concrete. Imagine you're a product manager at a mid-sized SaaS company, and you've just been handed a legal notice: a user with a visual impairment has filed a complaint that your app is inaccessible. You've got a week to respond, and you have no idea where to start. You pull up your analytics and see that 1 in 4 U.S. adults reports having some disability (WebAIM). You realize that you've been ignoring a massive segment of your potential user base. You also see that U.S. federal website accessibility lawsuits hit 3,117 in 2025, a 27% increase from the prior year (WebAIM). The writing is on the wall.

So you do what most people do: you run an automated accessibility checker. It spits out a report showing 200 errors on your homepage. You're overwhelmed, but you think, "I'll fix the alt text and the contrast, and we'll be fine." That's the checkbox mentality, and it's precisely why 83.9% of home pages still fail on low contrast text, and 53.1% on missing alt text (WebAIM Million). These are the easiest fixes, yet they persist. Why? Because automated tools can't tell you if your page actually makes sense when read aloud by a screen reader.

The Screen Reader Reality Check

I remember the first time I watched a user navigate a website with a screen reader. It was a revelation. The user didn't move a mouse; they used keyboard shortcuts and listened to a synthesized voice read the page top to bottom. They tabbed through links, forms, and buttons. They didn't see the visual layout—they experienced the content linearly. And when they hit a missing form label, the screen reader announced "Edit text, blank"—and they had no idea what to type. That's not a minor inconvenience; it's a barrier that prevents someone from completing a purchase, signing up for a service, or getting information.

Screen readers are not a niche tool. On mobile, 70.6% of WebAIM survey respondents use VoiceOver, Apple's built-in screen reader, and 34.7% use TalkBack on Android (WebAIM). And it's not just about vision: 5.3% of respondents are both deaf and blind (WebAIM). They might use a braille display—38% of respondents use braille output (WebAIM). So when you design with a screen reader in mind, you're not just helping a small group; you're enabling a diverse range of users to access your product.

Why the Guidelines Aren't Enough

Now, you might be thinking, "I'll just follow WCAG and be done." The Web Content Accessibility Guidelines are a solid foundation—they're the international standard, and the U.S. Department of Justice has explicitly adopted WCAG 2.1 Level AA for state and local government web content (ADA.gov). But here's the thing: WCAG is a set of principles, not a script. It tells you what success criteria to meet, but it doesn't tell you how to design an experience that actually works for screen reader users.

For example, WCAG requires that all images have alternative text. But what should that alt text say? If an image is purely decorative, it should have empty alt text so the screen reader skips it. If it's a chart, the alt text should convey the data, not just describe the colors. This is a judgment call that automated tools can't make. And that's why I recommend that every team, no matter how small, do a manual screen reader test at least once a month. It's not as hard as you think—you can start with a free tool like NVDA, which is open source and used by people in over 175 countries (NV Access).

The Business Case for Accessibility

Some people still argue that accessibility is a cost, not an investment. That's shortsighted. The global assistive technology market is projected to reach about $82 billion by 2030 (World Health Organization). Vision impairment alone costs the global economy an estimated $411 billion annually in lost productivity (World Health Organization). And hearing loss adds another $980 billion (World Health Organization). These are not small numbers. When you make your product accessible, you're tapping into a market that most of your competitors are ignoring.

And the legal landscape is shifting. The European Accessibility Act applies from 28 June 2025, requiring many products and services to meet accessibility standards (European Accessibility Act). In the U.S., Section 508 has required federal agencies to make their ICT accessible since 2017 (Section 508). The ADA has been interpreted to apply to websites, and the Department of Justice has made it clear that inaccessible web content denies equal access (ADA.gov). So the risk of ignoring accessibility is not just losing customers—it's facing lawsuits.

What I Actually Recommend

If you take away one thing from this article, let it be this: start testing with a real screen reader today. Not next month, not when you "have time"—today. Download NVDA for free (NV Access), or open VoiceOver on your Mac, and try to use your own product without a mouse. Listen to how it sounds. I guarantee you'll find something that makes you cringe. That's the first step toward fixing it.

And when you do, remember that you're not just checking a box. You're building a product that works for 2.5 billion people who need assistive technology—and that number is only going to grow. Let's make sure we're ready.

Sources

• World Health Organization - https://www.who.int/news-room/fact-sheets/detail/assistive-technology
• WebAIM Screen Reader User Survey - https://webaim.org/projects/screenreadersurvey10/
• WebAIM Million - https://webaim.org/projects/million/
• ADA.gov Web Accessibility Guidance - https://www.ada.gov/resources/web-guidance/
• NV Access - https://www.nvaccess.org/about-nv-access/
• European Accessibility Act - https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32019L0882