Your Website Is Failing Screen Readers: The Heading Fix That Works

Think accessibility is about adding alt text and calling it a day? Wrong. The real killer is something far more basic: your heading structure. Screen reader users don't read your page like sighted users do. They scan it by jumping from heading to heading, using the digital equivalent of a table of contents. If your headings are a mess, they're lost. And the data backs this up: 71.6% of screen reader users first navigate through headings when finding information on a lengthy page, and 88.8% find heading levels very or somewhat useful (WebAIM Screen Reader User Survey). Yet most websites treat headings as an afterthought. Let's fix that.

Imagine You're a Screen Reader User

Imagine you're blind and you land on a typical news article. You pull up your screen reader—maybe NVDA, the free, open-source Windows screen reader used by people in over 175 countries (NV Access). You press the key to jump to the next heading. Instead of a clean outline, you hear a jumble: an H2 that's actually a logo, an H3 for the byline, then an H4 for the first paragraph because someone styled text with a heading tag to make it bold. You're not reading an article; you're decoding a puzzle. So you leave. That's not a hypothetical. In WebAIM's 2024 survey, 85.9% of screen reader users said that better websites, not better assistive technology, would have the bigger impact on improving web accessibility (WebAIM Screen Reader User Survey). The tools work. Your site doesn't.

Why Headings Matter More Than Alt Text

Here's the thing: low contrast text is the most common accessibility error, appearing on 83.9% of home pages (WebAIM Million). But contrast is a visual problem. For a screen reader user, it's irrelevant. What matters is structure. Headings are the primary navigation tool for 71.6% of screen reader users (WebAIM Screen Reader User Survey). That's not a niche feature; that's the main way they interact with your content. Yet most sites get it wrong. The WebAIM Million analysis found that 95.9% of home pages have detectable WCAG 2 failures, averaging 56.1 errors per page (WebAIM Million). And those errors are getting worse—up 10.1% from 2025 (WebAIM Million). You can't just bolt on accessibility at the end; you have to build it into the skeleton of your page.

How to Fix Your Heading Structure in One Afternoon

Let's walk through a concrete scenario. You're a content manager for a mid-sized nonprofit. Your website has dozens of pages, each with a title, a few paragraphs, and a sidebar. You've never thought about headings. Here's your step-by-step fix.

1. Audit your current headings. Use a free browser extension that lists all headings on a page. Look for pages where headings are skipped (H1 to H3) or where headings are used for styling, not structure.
2. Start with one logical H1. Every page should have exactly one H1—the page title. Not your logo, not a tagline. Just the title.
3. Use H2s for main sections. Think of each H2 as a chapter. If your page has an introduction, a history, and a donation section, those are H2s.
4. Use H3s for subsections. If you need to break an H2 into parts, use H3s. Don't skip levels. Going from H2 to H4 is like ripping out a chapter title.
5. Don't use headings for bold text. If you want bold, use a tag. Headings are for structure, not style.

That's it. It's not glamorous, but it's the single highest-impact change you can make. And don't trust your eyes. Even government sites, which average 42.4 errors per page (WebAIM Million), still have more work to do. The good news is that WCAG 2.2, the current standard, has 86 success criteria organized under four principles, and heading structure falls under 'Operable'—it's a fundamental requirement (W3C Web Accessibility Initiative). You don't need to be perfect; you need to be intentional.

The Fix That Pays Off

Why bother? Because the stakes are real. In the U.S., 8.29 million Americans have a vision disability (WebAIM Screen Reader User Survey). Globally, at least 2.2 billion people have a near or distance vision impairment (WHO Blindness and vision impairment). That's a lot of potential readers, customers, or donors. And the legal pressure is mounting: U.S. federal website accessibility lawsuits reached 3,117 in 2025, a 27% increase from 2024 (WebAIM Screen Reader User Survey). The Department of Justice has made it clear that the ADA applies to websites (ADA.gov). You don't want to be a statistic.

But more importantly, fixing your headings is cheap. It doesn't require a redesign. It doesn't require new software. It just requires you to think in outlines. So start today. Pick one page, fix its headings, and test it with a screen reader. You'll hear the difference immediately. And if you're not sure where to start, remember: NVDA is free, and it's the most commonly used screen reader among WebAIM survey respondents at 65.6% (WebAIM Screen Reader User Survey). Download it, turn off your monitor, and try to navigate your own site. You'll learn more in ten minutes than any guide can teach you.

Sources

• WebAIM Screen Reader User Survey - https://webaim.org/projects/screenreadersurvey10/
• WebAIM Million - https://webaim.org/projects/million/
• NV Access - https://www.nvaccess.org/about-nv-access/
• W3C Web Accessibility Initiative - https://www.w3.org/WAI/standards-guidelines/wcag/
• WHO Blindness and vision impairment - https://www.who.int/news-room/fact-sheets/detail/blindness-and-visual-impairment
• ADA.gov - https://www.ada.gov/resources/web-guidance/