Designing For Screen Readers: Understanding the Mental Models and Techniques of Real Users
Summary
Starting out with a ten-minute live demo from an expert screen reader user, Samuel Proulx will introduce you to not only how they work, but the thought processes behind using the Internet with a screen reader. What are some of the most important things to take into account when attempting to construct a mental model of a screen reader user? How do these effect the way you think about designing websites and apps? How can designers learn to move beyond thinking visually, to create designs that work for everyone? After this introduction, the floor will open to your questions! If you have burning questions about how people who are blind use the Internet, or what design patterns work best and why or why not, this is your chance! Ask any question at all in an open, safe learning environment.
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
"The estuary is highly resilient but also very sensitive to industrial waste—creative collaboration areas in organizations are similar."
John CutlerOxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)
December 3, 2024
"If you’re generating buy-in, don’t forget what it will mean for your difficult stakeholders—they may have external pressures you don’t know about."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Executive air cover is having someone in a senior role who protects and supports the design team from other business pressures."
Dave GrayGroup Activity: Making Sense of DesignOps
November 7, 2017
"Executives only like things in threes, but if you do a three by three, you can get away with nine boxes—that's the max executive information processing."
John CutlerThe Alignment Trap
November 29, 2023
"Diagrams help when we feel stuck—providing stability, transparency, understanding, clarity, and kindness."
Abby CovertStuck? Diagrams Help
October 27, 2022
"We started to build an API for how other teams could interact with us like a contract."
Mark InterranteCollaboration Flows in Product Development
June 9, 2017
"Afrofuturism shows us the future must reckon with the past and center difference and diversity."
Devon PowersImagining Better Futures
March 9, 2022
"Bring your research team as note takers and facilitators—they make excellent collaborators and help build feedback loops."
Prayag NarulaHow to Empower Your Designers to Do Good Research – And Why You Want To
June 10, 2022
"Skills are like onboarding material for the model; you write them as simple markdown files that describe workflows or tools."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
