Stop Chasing Shiny Tools and Start Fixing Your Website

What software tools actually help people with disabilities use the web?

If you build websites, you've probably asked that. And you've probably been sold a lie: that the answer is some new, shinier assistive technology. A smarter screen reader. An AI that fixes everything. That's backwards. The most impactful software tools aren't the ones disabled people use—they're the ones you build. And you're building them wrong.

Your website is the real assistive technology

Assistive technology is only as good as the content it interacts with. A screen reader converts on-screen text into speech or braille. It doesn't magically make a broken website work. When WebAIM asked screen reader users what would improve web accessibility, 85.9% said better, more accessible websites—not better assistive technology.

That's a stunning rebuke. The people who rely on these tools every day are telling you the tools are fine. Your websites are the problem. And the data backs them up. The WebAIM Million 2026 analysis found that 95.9% of home pages have detectable WCAG 2 failures, averaging 56.1 errors per page. That's not a tool problem. That's a you problem.

The tools people actually use (and why you should care)

You don't need to know every screen reader, but you do need to know the big ones. On Windows, JAWS (commercial) and NVDA (free, open source) dominate. On Apple devices, VoiceOver is built in. On Android, TalkBack. There's also Narrator on Windows and Orca on Linux. In WebAIM's 2024 survey, JAWS held 40.5% of primary desktop screen reader use, while NVDA had 37.7%. But when you count anyone who uses a screen reader at all, NVDA leads at 65.6%, versus 60.5% for JAWS. And 71.6% of users run more than one screen reader.

What does that mean for you? You can't test with just one. But you also don't need to test with all of them. Focus on the free ones first: NVDA and VoiceOver. They're widely used and won't cost you a dime. If you're on Windows, NVDA is a must. It's been translated into more than 55 languages and used in over 175 countries (NV Access).

Mobile matters too. 91.3% of screen reader users use one on a mobile device. On mobile, VoiceOver is used by 70.6% of respondents, TalkBack by 34.7%. If your site isn't mobile-accessible, you're failing the vast majority of your users.

The six failures that cause 96% of your problems

You don't need to memorize all 86 success criteria in WCAG 2.2. You need to fix the basics. WebAIM Million found that six categories account for 96% of all detected errors:

• Low contrast text (83.9% of pages)
• Missing image alt text (53.1%)
• Missing form input labels (51%)
• Empty links (46.3%)
• Empty buttons (30.6%)
• Missing document language (13.5%)

That's it. Fix these six things and you've solved almost everything. And yet, the average page has 56.1 errors. Why? Because teams chase complex ARIA solutions instead of doing the simple work. WebAIM found that pages with ARIA present averaged 59.1 errors, while pages without ARIA averaged 42. ARIA made things worse. Stop over-engineering.

Here's a concrete example: I once watched a team spend two weeks adding ARIA landmarks to a site, only to discover that the low contrast on their call-to-action buttons—affecting 83.9% of pages—was the real barrier. A simple CSS change would have taken an hour.

Wait—aren't lawsuits and laws the real driver?

The strongest counter-argument is that you should focus on legal compliance, not usability. After all, US federal website accessibility lawsuits hit 3,117 in 2025, up 27% from 2024. The Department of Justice says the ADA requires accessible websites. The European Accessibility Act applies from June 2025. So why not just do the minimum to avoid a lawsuit?

Because the minimum is a moving target. The DOJ's 2024 rule under ADA Title II adopts WCAG 2.1 Level AA for state and local governments. Section 508 already requires WCAG 2.0 AA for federal agencies. If you aim for the bare minimum, you'll always be behind. And you'll still get sued. The average government home page has 42.4 errors—better than average, but not zero. You can't litigate your way to accessibility. You have to design for it.

What to do tomorrow

Fire your fancy accessibility overlay tool. It won't save you. Instead, do this: run an automated scan to catch the six common failures. Then test with NVDA and VoiceOver. Fix your contrast, add alt text, label your forms. That's 96% of the battle. And remember: 38% of screen reader users also use braille output, so don't neglect that. But start with the basics.

The best software tool for accessibility isn't something you buy. It's the code you write. Make it work with the tools people already have, and you'll do more good than any shiny new gadget ever could.

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/
• ADA.gov - https://www.ada.gov/resources/web-guidance/
• W3C WCAG - https://www.w3.org/WAI/standards-guidelines/wcag/