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
"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
"You can mine metadata from your platform to spot emerging patterns and commoditize new components."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"Cisgender binary options in onboarding flows exclude non-binary and gender-expansive identities."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"When fellow co-workers label an individual as difficult, it’s hard not to treat that person as a problem."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"My goal today is to showcase how generative AI can go beyond just speeding up our processes and actually catapult us in our career."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"The seven-foot-wide diagram showed the product’s true complexity, sparking necessary conversations with leadership."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"Investing in people and fostering collaboration always pays off in stronger teams and better user experiences."
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
"Design leaders want predictable roadmaps and healthy teams, measurable against timelines and goals."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
