When you build a digital foundation for higher education and healthcare, web accessibility is not a post-launch checklist item. It is structural.

WebAIM recently released its Screen Reader User Survey #11, providing fresh data on how people with visual impairments or assistive technology needs actually experience the web. Rather than guessing what works, here is what the data tells us and what it means for institutional web teams.

Key Findings: Tech & Navigation Trends

Desktop Screen Reader Usage Shifts

  • JAWS leads desktop usage: 55% of respondents cite JAWS as their primary desktop screen reader (a notable rise from 41% in 2024), followed by NVDA (32.9%) and VoiceOver (6.5%).
  • Multi-tool workflows are the norm: Over 70% of respondents regularly use more than one desktop screen reader.
  • High overall satisfaction: 95%+ of users report being very or somewhat satisfied with their primary screen reader.

Browsers & Mobile Platforms

  • Chrome + Windows is the dominant desktop stack: Chrome (52.3%) leads browser choice, ahead of Edge (23.6%) and Firefox (15.9%). Windows serves as the primary OS for 90.7% of respondents.
  • Mobile usage remains vital: 92% use screen readers on mobile devices, with Apple/VoiceOver (73.3%) remaining the dominant ecosystem compared to Android/TalkBack (24%).

Navigation Behavior

  • Headings are the primary navigation tool: 68% of users rely primarily on page headings to find information, and 88% explicitly rate heading hierarchy as useful.
  • Skip links and landmarks are secondary: While ARIA landmarks (e.g., main, navigation) and skip links are valued, they are used far less frequently than structured heading navigation.

AI Integration & Document Barriers

  • PDFs remain a major friction point: Over 85% of respondents state that PDFs are likely to create significant accessibility barriers.
  • AI adoption is accelerating: 91.8% of respondents use AI assistive features, such as generating automated image descriptions, summarizing dense content, and navigating complex online tasks.
  • Website quality matters most: 84% of users believe that building better websites has a far greater impact on accessibility than relying solely on better assistive technology.

What This Means for Your Web Strategy

  • Test with real technical stacks: Do not rely on a single browser-screen reader combination during testing. Standardize QA workflows across JAWS + Chrome, NVDA + Firefox/Chrome, and VoiceOver + iOS.
  • Treat heading hierarchy as navigation infrastructure: Headings are not just styling elements; they act as the site map for screen reader users. Maintain a strict, logical hierarchy (e.g., h1 → h2 → h3) without skipping levels.
  • Migrate critical PDF content to web HTML: If important information lives inside a PDF document, consider converting it into well-governed, structured HTML pages. HTML offers better responsiveness, lower maintenance debt, and superior accessibility.
  • Design for AI and human parsing simultaneously: Clear headings, clean semantic markup, and structured data do not just help screen reader users. They also help AI search tools (e.g., GEO) index and accurately summarize your institution’s content.

Building Digital Foundations That Last

At Digital Wave, we believe accessible design should be built into your digital foundation from day one, not patched on after launch. Whether you need an accessibility audit, keyboard/screen reader testing, or a long-term content governance plan, we make the complex manageable.