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 websites and apps? How can 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 consume web pages by skimming headings and landmarks, not reading linearly like audiobooks.
-
•
NVDA screen reader is open source and developed primarily by blind users, demonstrating inclusive design.
-
•
Screen readers are highly customized by users; almost no one uses default settings.
-
•
Semantic HTML landmarks enable quick navigation to relevant page sections, reducing cognitive load.
-
•
Web applications like Google Docs need ARIA application roles and custom hotkeys to manage complex interactions.
-
•
Consistency across a website’s page structure is crucial for efficient screen reader use.
-
•
Mobile apps are gaining popularity among blind users for tasks with limited typing, but desktop remains preferred for heavy typing.
-
•
Learning specialized hotkeys is acceptable if the user frequently returns to that application; infrequent apps should avoid them.
-
•
Partnering with grassroots accessibility organizations fosters trust and helps recruit diverse screen reader users.
-
•
Properly coded tables using semantic HTML enable screen readers to provide meaningful navigation and context.
Notable Quotes
"I can’t remember a day when there wasn’t a talking computer in my house."
"Screen reader users don’t listen to a web page like a podcast, it’s a very forward-leaning interactive experience."
"Most people listen to 250 words per minute; I often listen at 400 to 800 words per minute."
"Every assistive technology is not one size fits all, there are thousands of options to configure."
"Landmarks are like physical landmarks but for web pages, marking content roles for screen reader users."
"The more complicated a web app becomes, the more necessary the ARIA application attribute is."
"Mobile apps simplify design because of less screen real estate, which benefits all users including those using assistive technology."
"The real problem is asking me to learn specialized hotkeys for an application I only use once a year."
"Consistency is very important so what you learn on one page applies to all pages on that website."
"If you partner with grassroots organizations, they can help not only with recruiting but trust building and getting your name out there."
Or choose a question:
More Videos
"Career managers develop close relationships with designers and advocate for staffing and promotions on their behalf."
Ignacio MartinezFair and Effective Designer Evaluation
September 25, 2024
"Unstructured interviews are participant-controlled, spontaneous, and offer rich data but are less replicable."
Amelia ColeData-Prompted Interviews
December 17, 2021
"We're just getting started — there’s an opportunity for all of us to continue to participate and build this community."
Kristin SkinnerTheme 1 Intro
September 29, 2021
"Wire frames plus a little bit of storytelling is awesome."
Billy CarlsonTips to Utilize Wireframes to Tell an Effective Product Story
June 6, 2023
"Technology can be used for harm, like facial recognition systems misidentifying people of color as criminals."
Yolanda RankinBlack Feminist Epistemology as a Critical Framework for Equitable Design
March 11, 2021
"How do we empower others to perform research by becoming coaches?"
Eduardo OrtizTheme 3 Intro
March 13, 2025
"We created APIs so people can submit ideas or resource requests in a simple structure, and then track their status from accepted to rejected."
Toby HaugDiscussion
June 9, 2017
"To me, sweating the pixel means paying attention to the details of interactions and keeping our eye on quality as designers."
Joseph MeersmanSweating the Pixel: Scaling Quality through Critique
June 10, 2021
"I don’t think it’s taking the joy out, it’s helping people find where the joy is."
Bob BaxleyLeading with Design Operations Past and Present
December 19, 2019
