Designing For Screen Readers: Understanding the Mental Models and Techniques of Real Users
Summary
Key Insights
-
•
Screen reader users consume web pages by skimming headings and landmarks, not reading linearly like audiobooks.
-
•
NVDA screen reader is open source and developed primarily by blind users, demonstrating inclusive design.
-
•
Screen readers are highly customized by users; almost no one uses default settings.
-
•
Semantic HTML landmarks enable quick navigation to relevant page sections, reducing cognitive load.
-
•
Web applications like Google Docs need ARIA application roles and custom hotkeys to manage complex interactions.
-
•
Consistency across a website’s page structure is crucial for efficient screen reader use.
-
•
Mobile apps are gaining popularity among blind users for tasks with limited typing, but desktop remains preferred for heavy typing.
-
•
Learning specialized hotkeys is acceptable if the user frequently returns to that application; infrequent apps should avoid them.
-
•
Partnering with grassroots accessibility organizations fosters trust and helps recruit diverse screen reader users.
-
•
Properly coded tables using semantic HTML enable screen readers to provide meaningful navigation and context.
Notable Quotes
"I can’t remember a day when there wasn’t a talking computer in my house."
"Screen reader users don’t listen to a web page like a podcast, it’s a very forward-leaning interactive experience."
"Most people listen to 250 words per minute; I often listen at 400 to 800 words per minute."
"Every assistive technology is not one size fits all, there are thousands of options to configure."
"Landmarks are like physical landmarks but for web pages, marking content roles for screen reader users."
"The more complicated a web app becomes, the more necessary the ARIA application attribute is."
"Mobile apps simplify design because of less screen real estate, which benefits all users including those using assistive technology."
"The real problem is asking me to learn specialized hotkeys for an application I only use once a year."
"Consistency is very important so what you learn on one page applies to all pages on that website."
"If you partner with grassroots organizations, they can help not only with recruiting but trust building and getting your name out there."
Or choose a question:
More Videos
"If you want to scale, incorporate global UX research from day one and test your assumptions broadly."
Nancy DouyonWe'll Figure That Out in the Next Launch: Enterprise Tech's Nobility Complex
June 15, 2018
"All behavior your component is capable of, including responsive and interaction states, will work inside UXPin."
Jack BeharHow to Build Prototypes that Behave like an End-Product
December 6, 2022
"Vision types help us envision ideal futures freed from near-term constraints but must avoid magical thinking."
Jorge ArangoMeeting of the Waters: Designing for Successful Inorganic Growth
August 12, 2021
"What good are the insights if we can’t get them where they need to go, when they need to go there, and make sure they get used?"
Jon White Erin MayUnsticking Research for Better Information Flow
March 11, 2026
"Give a why of why you’ve made this design decision. It helps your team understand and reduces defensiveness."
Jessamyn EdwardsSurviving Your UX Career in Enterprise Design
December 2, 2021
"What one government agency does often serves as the playbook for success at another."
Stefanie OwensOptimizing for Outcomes: Transformation Design in Systems at Scale
December 4, 2024
"Friction can be good, especially when protecting private information."
Ron BronsonDesign, Consequences & Everyday Life
November 18, 2022
"As a starter, I’m great at beginning things, but the company has the infrastructure to maintain them."
Louis RosenfeldThe Rosenbot and the Rosenverse: An AMA with Lou Rosenfeld
June 5, 2024
"Every small initiative can lead to significant change when multiplied across communities."
Ash BrownSilver Linings: What DesignOps Learned in the Shift to WFH
October 23, 2020
