Stop Fixing Alt Text First: A Practitioner's Guide to Real Web Accessibility

Here's a number that should reset your priorities: 85.9% of screen reader users say that better websites, not better assistive technology, would make the biggest difference in their online experience (WebAIM). We've been treating accessibility as a checklist of widgets, but the data says the real problem is the web itself. This guide is for developers, designers, and content folks who want to stop guessing and start fixing what actually helps.

Who This Is For

If you've ever run an automated accessibility tool and felt overwhelmed by the red flags, this is for you. If you've argued with a product manager about why alt text matters, this is for you. We're going to walk through the practical steps we use to make websites genuinely usable for people who rely on screen readers, keyboards, and captions.

Step 1: Audit With the Right Lens

Automated tools are a start, but they only catch a fraction of problems. The WebAIM Million analysis of one million home pages found that 95.9% had detectable WCAG failures, averaging 56.1 errors per page. That's the automated baseline—real-world issues are even higher. But here's the kicker: the six most common errors account for 96% of all detected failures. Low contrast text tops the list (83.9% of pages), followed by missing image alt text (53.1%), missing form labels (51%), empty links (46.3%), empty buttons (30.6%), and missing document language (13.5%). So when we audit, we start with those six. Not because they're easy, but because they're the most frequent barriers.

Step 2: Make Headings Your Backbone

Screen reader users navigate by headings more than any other method—71.6% use headings to find information on a lengthy page, and 88.8% find heading levels useful (WebAIM). That means your heading structure isn't just an SEO nicety; it's a primary navigation tool. We make sure headings are logical, hierarchical, and not just styled text. A common mistake is using a <div> with a class instead of an actual <h2>. That's like removing street signs and wondering why people get lost.

Step 3: Fix Forms, Buttons, and Links

Forms are a nightmare for everyone, but especially for screen reader users. The WebAIM Million found that one third of form inputs on the average home page lack proper labels. That's 33.1% of inputs with no label. When a screen reader user encounters an unlabeled field, they hear "edit text" and have to guess what to type. We fix this by ensuring every input has a visible label, not just a placeholder. Placeholders disappear and aren't reliable.

Empty buttons and links are another silent killer. Imagine hearing "button" and not knowing what it does. We audit for any <button> or <a> that has no accessible name. This often happens with icon-only buttons. We add aria-label or visually hidden text. And for links, we never use "click here"—the purpose must be clear from the link text alone.

Step 4: Don't Rely on ARIA—Use Native Elements

ARIA is powerful, but it's not a magic wand. The WebAIM Million found that home pages with ARIA present actually averaged more errors (59.1 per page) than those without (42). That's because ARIA is often misused or added on top of broken code. Our rule: use native HTML elements whenever possible. A <button> is a button; a <div> with a click handler is not. ARIA should be a last resort, not a first instinct.

Step 5: Test With Real Screen Readers

Automated tools can't tell you if a screen reader user can actually complete a task. We test with NVDA, the free and open-source screen reader that's used by 65.6% of WebAIM survey respondents, and JAWS, which is still primary for 40.5% (WebAIM). We also test on mobile, because 91.3% of screen reader users use them on a mobile device (WebAIM). That means we're not just testing with a keyboard on a desktop; we're swiping through VoiceOver on an iPhone and TalkBack on Android.

What Can Go Wrong

You might think you've fixed everything, but then a user hits a CAPTCHA. The WebAIM survey found that CAPTCHA remains the most problematic item for screen reader users, and respondents with disabilities were twice as likely to rank it as a problem. We've seen it derail an otherwise perfect form. The solution? Use a non-visual alternative like a simple checkbox or a math problem, or provide a human verification via email. Don't rely on visual puzzles.

Bottom Line

The single best move you can make is to fix the six most common errors: contrast, alt text, form labels, empty links, empty buttons, and document language. That alone will eliminate 96% of detected issues on your site (WebAIM Million). Then, test with real screen reader users. Remember, they told us: better websites matter more than better tools. So let's build better websites.

Sources

• WebAIM Screen Reader User Survey - https://webaim.org/projects/screenreadersurvey10/
• WebAIM Million - https://webaim.org/projects/million/
• W3C Web Accessibility Initiative (WCAG) - https://www.w3.org/WAI/standards-guidelines/wcag/
• NV Access - https://www.nvaccess.org/about-nv-access/