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? After this introduction, the floor will open to your questions! If you’ve never worked with a screen reader user before, or if you have burning questions about how people who are blind use the Internet, this is your chance! Ask any question at all in an open, safe learning environment.
Key Insights
-
•
Screen readers like NVDA are extensively customizable; almost no user relies on default settings.
-
•
Screen reader users navigate webpages primarily by semantic elements like headings and landmarks, not by tabbing through every item.
-
•
NVDA has separate modes: browse mode for navigation and focus mode to interact with editable fields or complex web apps.
-
•
Many web pages fail to properly manage keyboard focus when dialogs (e.g., cookie consents) appear, leaving screen reader users unaware.
-
•
Web apps must handle all keyboard inputs precisely and maintain correct focus and semantics to be accessible.
-
•
Custom keyboard shortcuts in apps should be minimized if the app is used infrequently; learning many shortcuts is burdensome.
-
•
Mobile screen readers rely on limited gestures and intercept all touches to allow exploration without accidental activation.
-
•
Desktop screen readers offer more shortcuts, making them more efficient than mobile screen readers for complex tasks.
-
•
Accessibility improvements must include updates to semantics (like ARIA states) alongside visual changes for effective screen reader feedback.
-
•
Real user testing with participants using their own environment and customized settings yields more authentic accessibility insights.
Notable Quotes
"I don’t know anyone who uses the configuration out of the box without customizing it heavily and extensively."
"What a screen reader user does is they don’t start at the top and tab through every single element; they navigate by headings and landmarks."
"Screen readers have two modes: browse mode for navigating content and focus mode to interact with form fields or apps."
"If a dialog pops up but the keyboard focus isn’t moved into it, a screen reader user might not know it’s there."
"Google Docs is not a web page; it’s a web app that requires handling many keyboard shortcuts and focus management."
"If you make an app that users only use once a year, don’t expect them to learn dozens of custom shortcuts."
"On mobile, the screen reader intercepts all touches so users can explore without accidentally activating anything."
"Desktop screen readers can run at speeds up to 800 words per minute because users get used to synthetic speech."
"Reddit recently fixed their upvote button so it announces toggle states, something many sites neglect."
"Testing with the tab key is important, but it has nothing to do with a screen reader user’s actual experience."
Or choose a question:
More Videos
"Product designers I have worked with have experience deeply grounded in standards like NIST, ISO, IEEE, and HL7 for healthcare."
Noreen Whysel Katie SaindonShort Take #4: UX/Product Lessons from Your Industry Peers
December 6, 2022
"Collaboration is not just beneficial, it's essential for effective climate action."
Ash BrownSilver Linings: What DesignOps Learned in the Shift to WFH
October 23, 2020
"Accessibility and inclusivity are not afterthoughts; they must be baked into the design from the start."
Uday GajendarTheme 1: Introduction
June 9, 2021
"Designing and researching wisdom is a dialogue, not a monologue."
Cassini Nazir Meah LinThe Dangers of Empathy: Toward More Responsible Design Research
March 27, 2023
"Research leaders have a superpower to connect dots between users and the entire organization."
Gregg BernsteinOpportunistic Research with Gregg Bernstein
July 11, 2019
"After a year of D for D, nothing had changed. The initiative looked like just another check box."
Kaaren HansonStop Talking, Start Doing
June 9, 2017
"Two researchers can’t come close to digging into the customer problems for 17 product teams."
Erin May Roberta Dombrowski Laura Oxenfeld Brooke HintonDistributed, Democratized, Decentralized: Finding a Research Model to Support Your Org
March 10, 2022
"When it comes to the data we’re providing, that decision point is really important for PMs."
Brad Peters Anne MamaghaniShort Take #1: UX/Product Lessons from Your Industry Peers
December 6, 2022
"I was a very difficult person there. I was able to be head of design because I could sell my vision, but it was incredibly lonely."
Tutti TaygerlyVideconference: How to Work with Difficult People with Tutti Taygerly
June 25, 2020
