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
"You want to flex one or two variables to create range scenarios—best case, middle case, and worst case."
Giff ConstableFinancial fluency for product leaders: AMA with Giff Constable
April 11, 2024
"Don't design for a response, design for reasoning. Teach AI to think critically, analyze information, and arrive at logical conclusions."
Kritika YadavOptimizing AI Conversations: A Case Study on Personalized Shopping Assistance Frameworks
June 10, 2025
"Meetings tell us what kind of conversations we are having and what kind of conversations we are not having."
Alla WeinbergHow to Build and Scale Team Safety
January 8, 2024
"Designing for privacy is like designing for accessibility — you should aim beyond mere compliance to user-centered solutions."
Harry Brignull Mark Leiser Robert StribleyBeyond Clicks and Tricks: Why deceptive design has grown into a regulatory faultline
January 16, 2026
"We’re typically designing products to solve really complex issues."
Kit UngerTheme 2: Introduction
June 10, 2021
"It’s about helping your colleagues be more productive and make better decisions to help customers."
Sofia QuinteroBeyond Tools: The Messy Business of Implementing Research Repositories
March 10, 2022
"The only way we know we’re delivering value is if somebody changes their behavior."
Jeff GothelfThe Intersection of Lean and Design
January 10, 2019
"Our aspirations and anxieties are our users and messages, our passions and pet peeves."
Kit Unger Lada GorlenkoTheme 3 Intro
June 10, 2022
"We think with things; our brain is part of us but we extend our cognition into our environments and tools."
Jorge ArangoThe Best of Both Worlds: How to Integrate Paper and Digital Notes (1st of 3 seminars)
April 5, 2024
