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 do not consume web pages linearly but use hotkeys to skim and drill down into relevant sections swiftly.
-
•
Customization of screen readers is essential; no user relies on out-of-box settings due to diverse needs.
-
•
The ARIA application attribute is crucial for complex web apps like Google Docs to manage keyboard input and screen reader focus.
-
•
Landmarks in HTML5 act like physical waypoints that help users instantly navigate to meaningful page sections.
-
•
Semantic HTML structure, especially proper use of headings and tables, dramatically improves screen reader navigation and comprehension.
-
•
Recruiting blind screen reader users benefits greatly from partnering with grassroots advocacy organizations to build trust and access skilled participants.
-
•
Mobile apps can be easier to navigate due to simplified design, but desktop remains preferred for tasks requiring heavy typing or complex input.
-
•
Consistent UI patterns across pages in a website, like Amazon, make navigation predictable and efficient for screen reader users.
-
•
Learning specialized hotkeys is manageable for frequently used apps but problematic for infrequently used or one-time apps.
-
•
Accessibility testing and design should involve real users to understand intrinsic workflows and expectations beyond technical guidelines.
Notable Quotes
"I’ve been blind since birth and I can’t remember a day without a talking computer in my house."
"NVDA is developed by users for users, mostly blind or visually impaired, showing the power of inclusive design."
"Most people listen to 250 words per minute; I listen to my screen reader at between 400 to 800 words per minute."
"Screen readers are not like podcasts or audiobooks; they are interactive, forward-leaning experiences."
"You don’t listen to every element on the page; you skim the top and drill down exactly where you want."
"On Amazon, every heading usually represents a new search result, making it easy to navigate quickly."
"Google Docs isn’t really a web page; it’s an application requiring the ARIA application attribute for accessibility."
"With great power comes great responsibility for developers to ensure hotkeys and focus management work perfectly."
"Mobile apps simplify navigation but typing on mobile is harder than on a full desktop mechanical keyboard."
"Trust is key: if an app has a history of accessibility, users are more willing to learn its hotkeys and features."
Or choose a question:
More Videos
"SAFe risks becoming codified bureaucracy that sidelines the customer, but it holds potential if adapted to foster real business agility."
Jack MoffettSAFe or Sorry? (Videoconference)
May 29, 2019
"I care about three magic quadrants from now — I want the analysts chasing me, not me chasing documents."
Tricia WangSCALE: Discussion
June 15, 2018
"Simplifying systems takes patience and happens slowly, often involving years of work and negotiation."
Fredrik MathesonFirst-time users, longtime strategies: Why Parkinson’s Law is making you less effective at work – and how to design a fix.
June 8, 2016
"If something was unclear or uncomfortable by just one person, that was an indication it had to be edited."
Laine Riley ProkayHow DesignOps can Drive Inclusive Career Ladders for All
September 30, 2021
"At first, VOC was just me synthesizing, but as the company grew, we needed tools like UserVoice and then Idiomatic."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"When teams rely on bad data reports repeatedly, it’s necessary to analyze and escalate to leadership to address underlying issues."
Kristen Guth, Ph.D.Out of the FOG: A Non-traditional Research Approach to Alignment
March 28, 2023
"When organizations have diverse voices driving agendas at the top, earnings increase by 8% for every 10% increase in gender diversity."
Joi FreemanA New Vantage Point: Building a Pipeline for Multifaceted Research(ers)
March 30, 2020
"Prioritization is a constant negotiation between what’s urgent and what’s important."
Victor UdoewaTheme One Intro
March 27, 2023
"If you do your job as a designer, talk to users, create great designs, it’s not enough. You need to get the strategy right."
Peter MerholzCustomer-Centered Design Organizations
June 8, 2017