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
"We are witnessing the most rapid loss of biodiversity in human history."
Alex Hurworth Bonnie John Fahd Arshad Antoine MarinDesigning a Contact Tracing App for Universal Access
October 23, 2020
"Investing in new practitioners is mutually rewarding; we learn from their fresh perspectives and reassess what we know ourselves."
Laine Riley Prokay Lisa GordonCarving a Path for Early Career DesignOps Practitioners
September 9, 2022
"We did a great cleanup of patterns from every decade and deleted anything off brand or untested."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Rather than aiming for the chief strategy officer directly, build relationships with junior strategists who are more accessible."
Nathan ShedroffDouble Your Mileage: Use Your Research Strategically
March 31, 2020
"Accessibility is an ongoing process where we iterate, improve, and expand, and mobile-first makes the journey easier."
Sam ProulxMobile Accessibility: Why Moving Accessibility Beyond the Desktop is Critical in a Mobile-first World
November 17, 2022
"You need clear roles for moderators, note takers, recruiters, and designers in a rapid research program."
Feleesha SterlingBuilding a Rapid Research Program (Videoconference)
May 18, 2023
"We are at an inflection point where what got us here won't get us to a thriving future."
Neil BarrieWidening the Aperture: The Case for Taking a Broader Lens to the Dialogue between Products and Culture
March 25, 2024
"Incremental improvements and disruptive innovation require very different methods and measures."
John DevanneyThe Design Management Office
November 6, 2017
"Small experiments that fit into existing structures make it easier to involve collaborators and reduce resistance."
Katy MogalBut Do Your Insights Scale?
March 12, 2021
Dig deeper with the Rosenbot
How might subscription services be redesigned using thinking styles to better address user financial and emotional concerns?
What role does craft play in digital design, and how can we preserve the human presence in AI outputs?
How can voting and clustering features be used to prioritize research risks and concerns?