Skip to main content
Accessibility Guides

Your Overlay Tool Won't Save You: A Guide to Real Accessibility

Most accessibility overlays fail. Learn how to create genuinely accessible websites by focusing on WCAG, screen reader users, and real user testing.

Accessibility overlays are a waste of money. If you're a web developer or product manager, you've probably seen ads for tools that claim to make your site accessible with a single line of JavaScript. They don't work. The WebAIM Million 2026 analysis found that 95.9% of home pages have detectable WCAG 2 failures, averaging 56.1 errors per page (WebAIM Million). Overlays don't fix underlying issues; they often make things worse. The only reliable path is to build accessibility into your development process from the start.

Imagine you're a developer at a mid-sized e-commerce company. You've just been told to make your site accessible because of a lawsuit. You've heard about overlay widgets that promise quick compliance. But you also know that 85.9% of screen reader users say better websites, not better assistive technology, would have the biggest impact on accessibility (WebAIM Screen Reader User Survey). That's your real goal: a better website. Let's walk through how to do it right.

Step 1: Understand Who You're Building For

Your users aren't a monolith. Among screen reader users, 76.6% are blind, and 19.9% have low vision (WebAIM Screen Reader User Survey). They use a mix of tools: JAWS on Windows (40.5% primary desktop usage), NVDA (37.7%), and VoiceOver on mobile (70.6% of mobile screen reader users) (WebAIM Screen Reader User Survey). That means your site must work across multiple platforms. Don't assume one screen reader is enough. Test with at least NVDA (free) and VoiceOver (built into Apple devices). Remember that 71.6% of users run more than one screen reader, so inconsistencies will be noticed (WebAIM Screen Reader User Survey).

Also consider that 38% of screen reader users use braille output (WebAIM Screen Reader User Survey). That means your content needs to be structured logically for both speech and braille. Headings are critical: 71.6% of users navigate by headings first on long pages (WebAIM Screen Reader User Survey). If your headings are just styled text, you've already failed.

Step 2: Fix the Basics That Break Everything

The WebAIM Million reveals the same errors year after year. Low contrast text affects 83.9% of home pages. Missing image alt text affects 53.1%. Missing form labels affect 51%. Empty links and buttons affect 46.3% and 30.6% respectively. These six categories account for 96% of all detected errors (WebAIM Million). You don't need to be perfect to make a huge difference; you just need to fix these common failures.

Let's apply that to your e-commerce site. Your product images likely lack alt text. But alt text isn't just a description; it should convey the function. If the image is a link to the product page, the alt text should describe the link destination, not the image. WebAIM found that 45% of images missing alt text were linked images (WebAIM Million). That's a direct usability barrier. Similarly, your checkout form probably has unlabeled inputs. One third of form inputs on average are not properly labeled (WebAIM Million). Add elements. It's not hard, and it prevents users from abandoning their cart.

Step 3: Go Beyond Automated Testing

Automated tools catch only a fraction of issues. The WebAIM Million is based on automated detection, and it still finds errors on nearly every page. But automated tools miss things like keyboard traps, poor focus order, and confusing ARIA. In fact, pages with ARIA present average more errors (59.1) than pages without ARIA (42) (WebAIM Million). That's because ARIA is often misused. Don't add ARIA unless you absolutely must. Use native HTML elements first.

You need manual testing. Start by navigating your site with only a keyboard. Can you reach every interactive element? Is the focus visible? Then try a screen reader. NVDA is free and widely used (NV Access). Listen to how your site sounds. You'll quickly hear where labels are missing or headings are misused. Also, test with users with disabilities. They'll find issues you never imagined. This is where overlays fail: they can't simulate real user interaction.

Step 4: Prioritize Based on Impact and Risk

Not all errors are equal. Some are minor annoyances; others are complete blockers. CAPTCHA is the most problematic item for screen reader users, and those with disabilities are twice as likely to rank it as problematic (WebAIM Screen Reader User Survey). If your site uses CAPTCHA, you're shutting out a significant portion of your audience. Replace it with alternative verification methods, like email confirmation or simple logic questions.

Also consider legal risk. US 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). In 2024, the DOJ published a rule adopting WCAG 2.1 Level AA for state and local governments (ADA.gov). While that rule targets government sites, it signals the standard for all. If you're a business, you're not exempt. The European Accessibility Act applies from June 28, 2025, affecting any company doing business in the EU (European Accessibility Act). Compliance isn't optional.

Step 5: Build Accessibility into Your Workflow

Accessibility can't be a one-time project. It must be part of your definition of done. Train your designers to check color contrast. Train your developers to use semantic HTML. Add automated tests to your CI/CD pipeline, but don't rely on them alone. Conduct manual audits regularly. And most importantly, include people with disabilities in your testing. The WHO estimates that over 2.5 billion people need assistive technology, and that number is rising (World Health Organization). Your users are out there. They're not a niche; they're a global population.

Quick tip: Use the WebAIM Million's list of common failures as a checklist. Fix those six categories first, and you'll eliminate 96% of detectable errors.

Step 6: Measure What Matters

Don't just count errors. Measure task success. Can a screen reader user complete a purchase on your site? Can they find information quickly? Track metrics like time on task and error rates for users with disabilities. Compare them to users without disabilities. The goal is parity. Also, monitor your legal exposure. Lawsuits are increasing, and the cost of defense far outweighs the cost of accessibility. The global market for assistive technology is projected to reach $82 billion by 2030 (World Health Organization). That's a market you want to serve, not alienate.

Remember that accessibility benefits everyone. Captions help people in noisy environments. Clear labels help users with cognitive disabilities. Large touch targets help people with motor impairments. The curb-cut effect is real. By making your site accessible, you improve usability for all.

Takeaway: Ditch the overlay. Invest in training, testing, and inclusive design. Start with the six common failures, test with real users, and make accessibility a continuous practice. Your users—and your legal team—will thank you.

Sources

  • WebAIM Million - https://webaim.org/projects/million/
  • WebAIM Screen Reader User Survey - https://webaim.org/projects/screenreadersurvey10/
  • ADA.gov - https://www.ada.gov/resources/web-guidance/
  • NV Access - https://www.nvaccess.org/about-nv-access/
  • World Health Organization - https://www.who.int/news-room/fact-sheets/detail/assistive-technology
  • European Accessibility Act - https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32019L0882

Share this article:

Comments (0)

No comments yet. Be the first to comment!