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."
Dig deeper—ask the Rosenbot:
More Videos
"Sharing enables lots of great things to happen—it’s better than being locked in silos."
Etienne FangPower of Insights: Why sharing is better than silos with Uber’s Insights Platform
December 16, 2019
"We don’t limit applicants by their major or background; it doesn’t matter if they studied physics or marketing."
Victor M. GonzalezPracticing Learners and Learning Practitioners
March 10, 2021
"Getting stakeholders involved from the very beginning helps build buy-in and excitement around the research."
Roberta Dombrowski Sam Duong WoloszynskiMaking Research a Team Sport
March 11, 2022
"If patients stop using the app because they’ve got their health under control, that’s like a dating app success — they got married, not that the app failed."
Daniel J. RosenbergDigital Medicine Design
September 26, 2019
"Document your design decisions and architecture visually so new team members can quickly understand your system."
Jaime CreixemsBest Practices when Creating and Maintaining a Design System
June 7, 2023
"Language matters — calling people 'users' reflects and reinforces the reality of reduced agency."
Tricia WangFrom Users to Shapers of AI: The Future of Research
March 25, 2024
"If the game is chess and you're playing darts, no one is going to think you have any value."
Shahrzad SamadzadehWhat Is My Value? Two Takes and Some Mistakes
January 8, 2024
"Co-creation brings other stakeholders into the design process, not just for requirements but to actually do the design work."
Jorge ArangoDesign as an Antidote to VUCA
May 9, 2019
"We do about a hundred free community sessions a year where anyone with membership can attend."
Louis RosenfeldThe Rosenbot and the Rosenverse: An AMA with Lou Rosenfeld
June 5, 2024
