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
"I was talking with a person who said I’m like an idea machine, a 24-7 idea machine. The reply was immediate. It isn’t, you get used up and spat out."
Dr. Karl JeffriesThe Science of Creativity for DesignOps
January 8, 2024
"The culture between buyer and user impacts feature adoption and overall satisfaction."
Amy MarquezINVEST: Discussion
June 15, 2018
"The weakest insight method might win simply because of the relationship to the power structure."
Steve Portigal Chris Chapo Kelly Goto Christian RohrerDiscussion
May 13, 2015
"Involving designers early in the process is crucial to avoid the 'fast-food' model where they feel like order takers."
Alicia MootyDesign Staffing Models
September 30, 2021
"We want to stay in the game no users cursing our name."
Ana Maria Montero Barrantes Aditi Dhar Michelle Kaplan Nate Osborne Matt LaurenceThe Authentic UX Talent Show
January 8, 2024
"Junior team members don’t have to talk directly to executives; working effectively with peers can create grassroots buy-in."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"Choosing a research repository is a big battle in your organization; the right decisions can really help you succeed."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"Large companies demand certainty, but certainty is the opposite of innovation."
Laura KleinUnique challenges of innovation in enterprises
April 23, 2020
"Existing research repositories die at the bottom of slide decks; that’s why I started Everywhere to rethink how we manage insights."
Andrew MichaelBuilding a Product Insights Team
March 10, 2022
