Designing For Screen Readers: Understanding the Mental Models and Techniques of Real Users
Summary
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
"Designers should have a sense of belonging too. They should be having fun while learning and working."
Ebru NamaldiDesigning the Designer’s Journey: Scaling Teams, Culture, and Growth Through DesignOps
September 11, 2025
"Complexity is not a barrier to accessibility; even complicated games like The Last of Us are accessible."
Samuel ProulxInvisible barriers: Why accessible service design can’t be an afterthought
December 3, 2024
"Google’s HEART framework is great because different teams—engineering, product, and design—can all use it."
Kristin Skinner Kamdyn MooreGroup Activity: A Deep Dive Into Value and Outcomes
October 23, 2019
"AI won’t transform all things at once; it’s about piloting and delivering discrete business value first."
Jon Fukuda Amy Evans Ignacio Martinez Joe MeersmanThe Big Question about Innovation: A Panel Discussion
September 25, 2024
"Our engineering days let engineers pick up smaller ideas from research or bugs and improve the product incrementally."
Smitha Papolu Nova Wehman-Brown Melissa Schmidt Adam MenterTheme 3 Discussion
June 4, 2019
"Think about what your manager is being rewarded for to figure out how to better support them and your team."
Ellen ChisaThe Values of Design
November 29, 2023
"Inclusive design isn’t about a 1, 2, 3 checkbox. It’s about interpersonal work unraveling historical inequities."
Zariah CameronStreamlining an Inclusive Design Practice
October 3, 2023
"Some of these talks might make people feel a little uncomfortable because we haven’t had these conversations before."
Saara Kamppari-MillerTheme Three Intro
September 9, 2022
"Everyone was doing a little bit of design ops here and there, which created a lot of gray area around decision making."
Michelle ChinThe DesignOps Starter Kit
September 29, 2021
Latest Books All books
Dig deeper with the Rosenbot
How can candidates identify their skill gaps and communicate growth areas during interviews?
Why is it expensive and complicated to design AI-powered UX across different platforms like Slack, Teams, and Claude?
How can designers sustain long-term accessibility projects financially and organizationally?