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 for accessible, public use? How can civic 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
-
•
Using assistive technology like screen readers is a skill that requires significant training and practice.
-
•
Screen readers navigate web pages by jumping between semantic elements like headings rather than reading everything sequentially.
-
•
Default out-of-the-box settings for screen readers do not reflect the experience of expert users, who heavily customize them.
-
•
Hover-only interface elements are inaccessible to screen reader users who rely on keyboard navigation.
-
•
Visual states such as pressed buttons must be communicated through ARIA attributes or focus changes for screen reader users.
-
•
Dialogs and dynamic content must manage focus properly to notify screen reader users of changes.
-
•
Screen reader users rely on short, immediate alerts for form errors and can explore more detailed messages at their own pace.
-
•
Custom hotkeys for applications should be designed considering frequency of user interaction and the complexity of memorization.
-
•
Accessibility must be a shared responsibility, integrated across design, development, and content rather than siloed.
-
•
Screen reader users can customize voice profiles and settings, meaning one-size-fits-all accessibility assumptions are flawed.
Notable Quotes
"It is very difficult for somebody who has never used assistive technology to have the same experience as someone who uses it daily for everything."
"The experience of using a screen reader is probably 10 times faster as you become more expert with it."
"Screen readers navigate based on the code and semantics, not on visual layout or appearance."
"If something is only visible on hover, it either needs to be visible to screen readers at all times or have an alternative way to access it."
"When you press a button like an upvote, it’s the developer’s job to make sure the visual state is communicated via ARIA landmarks."
"Focus changes are critical to inform screen reader users when dialogs open or content changes."
"Errors in form fields should alert users immediately but also allow them to explore details at their own pace to avoid cognitive overload."
"If you’re designing a site used infrequently, don’t overload it with custom hotkeys that are hard to memorize."
"Accessibility is not just one person’s responsibility; it must be distributed through the whole product team."
"Screen reader users control how metadata or tooltip voices are played, it’s a personal setting, not dictated by web designers."
Or choose a question:
More Videos
"Empathy sticks with you; if I tell you an inspirational story about what a customer has done, you’ll remember it."
Ross SmithBreaking Barriers with Empathy
June 9, 2017
"Engineers are great at executing code but often lack connection to user experience and design processes."
Kevin M. HoffmanTheme 2: Enterprise Team Journey
June 3, 2019
"If you’re amazing at your job but no one listens to your research or design, does it really have impact?"
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"Apple has thought hard about letting people unbox and set up their phone entirely without help, including turning on VoiceOver."
Sam ProulxUnderstanding Screen Readers on Mobile: How And Why to Learn from Native Users
October 2, 2023
"When design ops comes in hot, it means honest, orchestrated, and timely."
Briana Thomas Christina RodriguezWhen Design Ops Comes in H.O.T. : A Tale of a Transformed Design Org
September 30, 2021
"Achieving coherency across products leads to less training, fewer support calls, and more users successfully adopting products."
Prerna MakanawalaAchieving Balanced Design Consistency
June 9, 2021
"Our tool is not partial to Sketch — we support Adobe XD and will soon support Figma, enabling flexible integration in design workflows."
George Abraham Stefan IvanovDesign Systems To-Go: Reimagining Developer Handoff, and Introducing App Builder (Part 2)
October 1, 2021
"Identifying the right success metrics is the number one challenge teams are facing today."
Dana Bishop2022: The Year UX Demonstrates its Business Impact
March 11, 2022
"Changing course based on evidence of actual human behavior is what agility really means."
Jeff GothelfWho does what by how much?
November 20, 2025
