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
-
•
Screen reader users do not navigate web pages linearly like listening to a podcast; they jump between semantic landmarks like headings and regions.
-
•
Assistive technology settings are heavily customized by users and rarely used in their default configurations.
-
•
Proper semantic HTML usage is critical because screen readers rely on code structure, not visual styling.
-
•
Hover-only interactive elements are inaccessible unless they provide keyboard-accessible alternatives or are always visible.
-
•
Moving keyboard focus programmatically is essential for announcing changes like expanded menus or dialog pop-ups to screen reader users.
-
•
ARIA attributes like aria-pressed and aria-expanded communicate visual state changes to assistive technologies.
-
•
Error messages for form validation must be concise when announced automatically but allow users to get details at their own pace.
-
•
Custom hotkeys must be designed carefully to work well with screen reader interception and consider user familiarity.
-
•
Screen readers can use different voice profiles for metadata, but these are user-controlled settings, not controlled by websites.
-
•
Accessibility responsibility should be distributed across design, development, and content teams, not isolated to one person.
Notable Quotes
"The experience that I’m having is probably 10 times faster than the experience of having the voice at a slower speed."
"Assistive technology is not a one-size-fits-all solution."
"We’re not going to start from the top. We’re going to use headings and landmarks to quickly scan a webpage."
"If something is only visible via hover, it needs to be visible to the screen reader at all times or have an alternative."
"If you press a button and the semantics haven’t changed or the focus hasn’t moved, as far as I’m concerned, nothing has happened."
"It can be very useful to put key status information, like new messages, into the page title so screen readers can alert users automatically."
"Visual states like an upvote button being pressed must be communicated with ARIA attributes or focus changes."
"Accessibility has to be distributed throughout the team — it can’t be just one person’s responsibility."
"There’s a balancing act with error messages: short enough to be processed immediately, detailed enough to explore as needed."
"Screen reader hotkeys can intercept keys, so when creating custom hotkeys, you have to ensure they work smoothly for screen reader users."
Or choose a question:
More Videos
"There’s never enough attention you can give to change management in scaling design impact — don’t do it alone."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"If I don’t have a map, I can’t see patterns or apply context-specific gameplay."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"Many smartwatch designs assume male hands as default, excluding smaller wrists and diverse body types."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"I felt on edge around Jeff and physically depleted after our interactions."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Using ChatGPT allowed me to elevate from a researcher to a strategist by increasing my visibility and trust in the company."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"There is a common thread in craft: dignity, purpose, utility, and beauty."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"We formed a small core task force empowered to make decisions to avoid delays from formal reviews."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"You won’t know what success looks like until you put something out there and see how it works in practice."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"At Qubits, you can customize or copy standard design processes like Lean UX and add or remove activities easily."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
