Stop Blaming Screen Readers: Fix Your Headings First

Imagine you're using a screen reader to browse the web. You land on a page, and instead of a clear structure, you get a wall of text—no headings, no landmarks, just a confusing jumble. That's the reality for millions of people. The problem isn't the screen reader; it's the website. And you can fix it.

The Real Barrier Is Your Code, Not the User's Tech

Screen readers are remarkably capable. In WebAIM's 2024 survey, 91.3% of respondents use a screen reader on a mobile device, and 71.6% use more than one. They're not struggling because the technology is weak. The problem is that 95.9% of home pages have detectable WCAG 2 failures, averaging 56.1 errors per page (WebAIM Million). That's not a tool problem; it's a design problem. And the biggest bang for your buck is fixing headings.

Headings Are Your Best Friend—Use Them

When screen reader users land on a lengthy page, 71.6% first navigate through headings to find information, and 88.8% find heading levels useful (WebAIM). That's a clear signal: if your headings are missing or mislabeled, you're making the web unusable for almost three-quarters of screen reader users. So, roll up your sleeves and make sure every page has a logical heading hierarchy—H1 for the title, H2 for sections, H3 for subsections. Don't skip levels. Don't use headings for styling. It's that simple.

But here's the kicker: even when you do the basics, you can still trip up. The WebAIM Million found that missing image alt text (53.1% of pages) and missing form labels (51%) are widespread. Those are easy wins, too. Yet headings are the gateway—they let users skip around and get the gist. So start there.

Objection: "But We Have a Design System"

You might think, "We have a component library; accessibility is handled." But the data says otherwise. The WebAIM Million found that pages with ARIA attributes actually had more errors (59.1 average) than pages without ARIA (42). ARIA is a powerful tool, but it's often misused. The problem is that design systems can give a false sense of security. They standardize components, but they don't guarantee that every instance is coded correctly. So, even with a design system, you need to audit your pages. And headings are the first thing to check.

Take These Steps Today

Here's a blunt action plan:

• Run an automated audit on your top 10 pages using a tool like WAVE or axe.
• Check heading order: every page should have exactly one H1, and H2s should follow in order.
• Add descriptive alt text to images—16.2% of images are missing it (WebAIM Million).
• Label your form inputs—33.1% of inputs are unlabeled (WebAIM Million).

This isn't just about avoiding lawsuits (though US federal website accessibility lawsuits hit 3,117 in 2025, up 27% from 2024). It's about reaching 1.3 billion people with disabilities (WHO). And it's about doing the right thing.

Bottom Line

Stop blaming screen readers. The single best move you can make today is to fix your heading structure on every page. It's the highest-impact, lowest-effort change that will immediately improve the experience for screen reader users. Do it now.

Sources

• WebAIM Screen Reader User Survey - https://webaim.org/projects/screenreadersurvey10/
• WebAIM Million - https://webaim.org/projects/million/
• World Health Organization (Disability and health) - https://www.who.int/news-room/fact-sheets/detail/disability-and-health
• ADA.gov Web Accessibility Guidance - https://www.ada.gov/resources/web-guidance/