Screen Reader Compatibility: What Websites Must Do
TL;DR
Screen readers are software that blind users use to read websites aloud. Your site must provide semantic HTML and ARIA labels so screen readers can understand and announce content correctly.
What This Violation Means
Screen readers convert digital text into speech or refreshable Braille displays, allowing blind and visually impaired users to navigate websites. Popular screen readers include JAWS (Job Access With Speech), NVDA (NonVisual Desktop Access), and VoiceOver (built into Apple devices). They rely on proper HTML structure, ARIA attributes, and alt text to understand page content and functionality.
Why Demand Letters Cite This Violation
- Blind users literally cannot use incompatible sites - it's not inconvenient, it's impossible
- Common issues: unlabeled buttons that announce only 'button', missing landmarks that make navigation impossible, improper heading structure that breaks screen reader navigation
- Easily demonstrated in court - plaintiff can show the judge/jury exactly what they hear
- Multiple WCAG success criteria relate to screen reader access
- This is often the most impactful violation from a user perspective
Real-World Example from Actual Demand Letters
A typical demand letter states: "The website contains numerous unlabeled buttons and form controls that provide no information to screen reader users. For example, the search button in the header contains only an icon with no text alternative, announcing merely as 'button' without indicating its purpose. The product filter controls announce no state information, making it impossible to determine whether filters are selected or deselected. These issues violate WCAG Success Criteria 1.3.1 (Info and Relationships), 2.4.4 (Link Purpose), and 4.1.2 (Name, Role, Value)."
What the Law Says
- Proper heading structure for navigation (1.3.1 - Info and Relationships)
- Landmark regions to identify page sections (1.3.1)
- Labels and accessible names for all controls (4.1.2 - Name, Role, Value)
- Meaningful link text that makes sense out of context (2.4.4 - Link Purpose)
- Alt text for images (1.1.1 - Non-text Content)
- Proper form labels (3.3.2 - Labels or Instructions)
The underlying principle: assistive technology must be able to programmatically determine the purpose, state, and value of all interface components.
Code Examples: Incorrect vs. Correct
❌ Incorrect Implementation
<button><img src="icon.png"></button>
(Screen reader announces: "button" - no indication what it does)
<div onclick="toggleMenu()">Menu</div>
(Screen reader doesn't recognize this as interactive)
<h1>Page Title</h1>
<h3>Section</h3>
(Skips heading level 2, breaks navigation)✓ Correct Implementation
<button aria-label="Submit form"><img src="icon.png" alt=""></button>
(Screen reader announces: "Submit form button")
<button onclick="toggleMenu()">Menu</button>
(Screen reader recognizes this as an interactive button)
<h1>Page Title</h1>
<h2>Section</h2>
(Proper hierarchy, enables screen reader navigation by headings)How to Fix This Violation
DIY Approach
2. Turn off your monitor or close your eyes
3. Try to complete common tasks on your site using only audio
4. Note every place where you get confused or stuck
Common fixes:
- Add aria-label to icon-only buttons:
Professional Remediation
Professional screen reader testing involves using multiple screen readers (NVDA, JAWS, VoiceOver, TalkBack for mobile) across different browsers, as behavior varies. We test with actual blind users when possible to catch issues automated tools miss. We implement complex ARIA patterns for custom widgets (tabs, accordions, sliders), ensure dynamic content updates are announced properly, and document all issues with code-level fixes. For single-page applications, we implement focus management and route announcements. We've built accessible component libraries that work correctly with all major screen readers.
Cost to Fix
DIY Approach
Free (but requires significant learning - expect 10-20 hours to become proficient with screen readers)
Professional Fix
$1,500-$4,000 for comprehensive screen reader compatibility fixes (typically included in Comprehensive package: $6,000-$12,000)
Full Remediation
$6,000-$12,000 for Comprehensive remediation package
Our Experience Fixing This Violation
Screen reader compatibility is where accessibility gets really challenging. We've spent hundreds of hours testing with NVDA, JAWS, and VoiceOver to understand their quirks and differences. For Tractor Supply's site, we made their complex product search and filter system work with screen readers - every filter had to announce its current state, search results had to update without losing focus, and the entire experience had to be navigable by blind users. We've built accessible React component libraries where every custom widget (modals, tooltips, tabs, accordions) follows WAI-ARIA authoring practices and works correctly with screen readers. The key insight: you cannot fully understand screen reader compatibility without actually using screen readers extensively.
Related Accessibility Violations
Legal Disclaimer
This guide provides technical information about website accessibility violations based on our experience remediating WCAG issues. It is not legal advice and should not be relied upon as such. If you have received an ADA demand letter or are facing legal action, consult with an attorney who specializes in ADA defense. Laws regarding digital accessibility vary by jurisdiction and are subject to change. While we provide accurate technical guidance, we make no guarantees about legal compliance or outcomes.
Need Professional Help Fixing This Violation?
Our Houston-based team has 10+ years of experience remediating this exact violation across hundreds of websites. Get a free scan or book a call for a fixed-price quote.
Written by Houston Web Compliance
Our team has over 10 years of hands-on experience fixing website accessibility violations for enterprise e-commerce sites, complex web applications, attorney websites, and businesses nationwide. We've remediated WCAG violations on platforms including React, WordPress, Drupal, HubSpot, and custom applications.
Based in Houston, Texas | Serving businesses nationwide | Learn more about our team