Most people think a screen reader is the problem. It's not.
According to WebAIM's 2024 Screen Reader User Survey, 85.9% of screen reader users say that better, more accessible websites—not better assistive technology—would have the bigger impact on improving web accessibility. That's the group you're building for. So stop blaming the tool. Your code is the bottleneck.
This guide is for anyone who owns or manages a website—marketers, developers, business owners. You don't need a degree in accessibility. You need to fix six recurring mistakes that account for 96% of all detected errors on home pages (WebAIM Million). Do that, and you'll go from failing to passable.
I'll walk you through each fix, in order of frequency, with concrete steps. No fluff.
1. Start with Low Contrast Text
The most common WCAG failure is low contrast text—it appears on 83.9% of home pages (WebAIM Million). That's not just a screen reader issue. It's a readability issue for everyone, especially the 2.2 billion people worldwide with vision impairment (WHO).
Fix it: Ensure your text has a contrast ratio of at least 4.5:1 against its background. Use a contrast checker like WebAIM's. If your brand colors fail, adjust the text color—not the background. This one fix alone removes the largest barrier.
What can go wrong: You think a gray text on white looks classy. It fails. The fix is simple: darken it.
2. Add Missing Alt Text
53.1% of home pages have missing alt text (WebAIM Million). Screen reader users rely on alt text to understand images. Without it, they hear nothing—or worse, the file name.
Fix it: For every meaningful image, add a concise, descriptive alt attribute. For decorative images, use alt="" so screen readers skip them. Don't stuff keywords. Just describe the image's purpose.
One-third of images missing alt text are linked images—that's a navigation dead end. If an image is a link, the alt text must describe where the link goes (WebAIM Million).
3. Label Your Form Inputs
33.1% of form inputs on the average home page lack proper labels (WebAIM Million). Screen reader users can't guess what a field is for. Without a label, they're stuck.
Fix it: Use explicit <label> elements associated with each input. Placeholder text is not a substitute—it disappears when typing. Also ensure the label is programmatically linked, not just visually placed.
Forms are critical for transactions. If a screen reader user can't fill out your contact form, you've lost a customer.
4. Fix Empty Links and Buttons
Empty links (46.3%) and empty buttons (30.6%) are common. These are elements that have no accessible name. Screen reader users tab through links and buttons to navigate. An unlabeled link is a dead end.
Fix it: Every link and button must have an accessible name—either text content, an aria-label, or an aria-labelledby. If an icon button has no text, add an aria-label like "Search" or "Close."
Check your navigation. If you have a hamburger menu icon, it needs an aria-label.
5. Declare the Document Language
13.5% of home pages don't declare a language (WebAIM Million). Screen readers use the lang attribute to determine pronunciation. Without it, English text might be read with Spanish or French phonetics—garbled.
Fix it: Add lang="en" to the <html> element. For mixed-language content, set the language on inner elements.
This is a one-line fix. Do it.
6. Use Headings Correctly
Screen reader users navigate by headings. In fact, 71.6% first navigate through headings when finding information on a lengthy page (WebAIM). Headings give structure.
Fix it: Use real heading tags (<h1> through <h6>) in a logical order. Don't skip levels. Don't use headings for styling—use CSS. Visual bold text isn't a heading.
After you fix these six, test with a screen reader. Download NVDA, the free, open-source screen reader (NV Access). Listen to your page. You'll hear errors you never imagined.
Why This Matters Now
Web accessibility isn't optional. The U.S. Department of Justice states that inaccessible web content denies equal access and that the ADA requires businesses open to the public to make their websites accessible (ADA.gov). Federal lawsuits hit 3,117 in 2025—a 27% increase from 2024 (WebAIM).
Yet 95.9% of home pages still have detectable WCAG failures (WebAIM Million). That's a legal and ethical failure.
Don't wait for a demand letter. Fix the six errors. You'll serve more people and reduce risk.
Sources
- WebAIM Screen Reader User Survey - https://webaim.org/projects/screenreadersurvey10/
- WebAIM Million - https://webaim.org/projects/million/
- World Health Organization (Blindness and vision impairment) - https://www.who.int/news-room/fact-sheets/detail/blindness-and-visual-impairment
- ADA.gov Web Accessibility Guidance - https://www.ada.gov/resources/web-guidance/
- NV Access - https://www.nvaccess.org/about-nv-access/
Comments (0)
Please sign in to post a comment.
Don't have an account? Create one
No comments yet. Be the first to comment!