
Screen readers in 2026: what 1,780 users expect from your pages, and where to start
In late September 2026, WebAIM published the results of its eleventh screen reader user survey: 1,780 valid responses, collected in July and August 2026 from people who browse every day with JAWS, NVDA, VoiceOver or TalkBack. A month later, on 26 October, NV Access shipped NVDA 2026.3, and on 4 November the W3C updated its accessibility roadmap. These three signals tell product teams the same thing: people who do not use a mouse have very specific habits, and most websites still ignore them.
What users say
- Headings first. On a long page, 67.8% of respondents start by scanning the section headings. The find-in-page feature comes far behind (12.5%), then linear reading (9.7%) and link navigation (6.7%). Heading levels are rated useful by 88.3% of them.
- Landmarks are underused. Only 3.4% rely first on page regions to find information, and their frequent use drops to 28.3%, down from 31.8% in 2024. Skip links, on the other hand, are gaining ground: 37.7% use them always or often, up from 31.2% in 2021.
- PDF remains the main document barrier. 85.6% of respondents consider it very or somewhat likely that a PDF will cause them significant problems, up from 75.1% in 2019. For a Word document, the figure falls to 31.1%.
- Perceived progress is eroding. 32.2% find the web more accessible than before, 44.9% see no change and 22.9% find it less accessible. And 83.9% believe that better websites would have more impact than better assistive technology.
- AI is now part of daily use. 60.1% use AI to describe images, 49.7% to analyse complex images, 40.6% for guidance through an online task. Only 8.2% never use it. It is a crutch, not an excuse: it fills gaps the website should have avoided.
The panel is shifting too. JAWS is again the primary desktop screen reader (55%, up from 41% in 2024), NVDA falls to 32.9% and VoiceOver to 6.5%. Chrome dominates (52.3%), ahead of Edge (23.6%) and Firefox (15.9%); the most common combination is JAWS with Chrome (31.2%). On mobile, 91.8% use a screen reader, 73.3% of them on iPhone or iPad. And 70.3% juggle several screen readers: testing with one is not enough.
Why now
The tools are moving fast. NVDA 2026.3, released on 26 October 2026, now announces headings, paragraphs and lists inside an alert, stops repeating row and column headers in ARIA grids, adds quick navigation to clickable elements and a native selection mode for Firefox and browsers based on Chromium 134 or newer. A component that passed with an earlier version may behave differently today.
On the standards side, the W3C WAI roadmap, updated on 4 November 2026, plans for November or December a Candidate Recommendation Snapshot of WAI-ARIA 1.3 and an updated draft of the guidance on applying WCAG 2.2 to mobile applications. WCAG 3, whose latest draft dates from 10 September, remains years away from completion: the operational reference is still WCAG 2.2.
Who is concerned
Any organisation that publishes pages, forms or documents: customer portal, member area, line-of-business application, institutional website, SaaS product. Decision-makers see a regulatory risk and a reputation issue; product teams, a short list of conventions to follow; technical teams, concrete behaviours to verify with the tools people actually use.
Where to start
- Audit the heading structure of your ten most visited pages: a single main heading, levels without gaps, labels that describe the section. It is the first move of two users out of three.
- Add a skip link visible on focus and named regions: header, navigation, main content, footer. Inexpensive, and increasingly used.
- Screen your PDFs: title, language, reading order, tagging. Where possible, replace them with an HTML page.
- Test with JAWS and NVDA on Chrome, then VoiceOver on iPhone: this trio covers most of the panel. Replay your alerts, tables and menus after every screen reader update.
- Do not let your users’ AI describe your images for you: write the text alternatives, especially for charts and image buttons.
We carry out these structure and keyboard navigation audits, and we support teams all the way to testing with real screen readers. Let’s talk about the accessibility of your journeys.
I can help you.
Let's discuss your project.