Prototype Reviews, People With Disabilities, and You
Summary
In this interactive session, Sam Proulx, accessibility evangelist at Fable, will draw from experience as a person with a disability, and from Fable’s thousands of hours of research experience, to answer all of your questions about conducting prototype reviews with people with disabilities. What design systems work best? What disabilities can participate in prototype reviews out of the box, and what types of disabilities might need special adaptations? What information should a prototype contain, to get the best feedback and engagement from people with disabilities? How can you and your organization learn to better shift left, and involve people with disabilities as early as possible in the design process, and why should you? We’ll also have plenty of time for your own questions! If you’ve been wanting to conduct prototype reviews that involve people with disabilities, but weren’t quite sure where to begin, don’t miss this session!
Key Insights
-
•
Starting prototype reviews with screen magnification users offers high impact with minimal adaptation.
-
•
Screen magnification users benefit from graphical prototypes because they can magnify visuals and assess color contrast and text size directly.
-
•
Users with physical challenges may need researchers to operate prototypes on their behalf due to assistive tech limitations, especially with hover and click targets.
-
•
Screen reader users require prototypes with semantic markup like proper heading levels, labeled controls, and landmarks, which traditional wireframes usually lack.
-
•
Prototyping tools like Figma and Adobe currently have limited accessibility support for screen reader users but are actively researching improvements.
-
•
Building prototypes for screen reader users often involves using document-based tools like Microsoft Word or Google Docs to show semantic structure and text equivalents.
-
•
Hover interactions pose significant challenges for users relying on alternative navigation methods such as switch systems or head mice.
-
•
Control labeling consistency in prototypes is crucial to avoid confusion, particularly for those using voice dictation or alternative input.
-
•
Low vision users who do not fully rely on screen readers are the largest group benefiting from improved prototype accessibility.
-
•
Mobile accessibility considerations largely mirror desktop concerns, with screen size and gesture differences being the main changes.
Notable Quotes
"Including people with disabilities in prototype reviews can be different based on the assistive technology they use and their needs."
"Screen magnification is really about making the screen larger, changing color contrast, reducing motion, and panning around the magnified area."
"Screen magnification users are a great place to start because your prototypes and tools will mostly just work with minimal adaptation."
"Users with physical challenges often can see and interpret prototypes but may need help clicking through them because assistive tech may not support the prototype system."
"Screen reader users need semantic structure that graphical prototypes typically don’t have, like labeled headings, controls, tables, and landmarks."
"For screen reader users, you often need to build entirely new prototypes using systems like Microsoft Word or Google Docs to convey semantic information."
"Hover is very difficult for users who use switch systems or head mice because they can only click or not click and have trouble holding steady to hover."
"Consistency between control labels and prototype instructions matters a lot, because mismatches can cause big problems for alternative navigation."
"Most of the work on accessible prototyping for screen readers is still in early or mid research stages but is improving rapidly."
"Involving people with disabilities throughout the product development cycle is crucial, from prototype reviews through to acceptance testing."
Or choose a question:
More Videos
"Compound effect means good upon good upon good eventually builds to incredibly fast growth."
Erin WeigelUX Lessons from running more than 1,200 A/B Tests
July 10, 2024
"The essence of strategy isn’t painting a grand vision of the future, it's deciding what not to do."
Mike OrenWhy Pharmaceutical's Research Model Should Replace Design Thinking
March 28, 2023
"The era of 100-page reports is ending because we simply can’t produce them fast enough at scale."
Lija Hogan Milan Mijatovic Sam Proulx Louis RosenfeldThree Years Out: Perspectives on the Near-Term Future of User Research
March 15, 2024
"Alice often perceives Charlie as just another barrage of alerts filled with jargon she doesn't understand."
Heidi TrostWhen AI Becomes the User’s Point Person—and Point of Failure
August 7, 2025
"The IBM design language is about system unity instead of uniformity, so designers aren’t cookie cutters."
Adam CutlerPeople + Places + Practices = Outcomes
June 8, 2016
"Digital literacy requires someone to examine and peruse information on digital platforms, not just basic use."
Rittika BasuAge and Interfaces: Equipping Older Adults with Technological Tools
February 23, 2023
"Accessibility is more of a process than a result; it starts at the very beginning of product development with research including disabled users."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility
May 26, 2022
"Practical ops is about getting stuff done because it’s our job to scale the organizational ability to design and amplify the work of designers."
Bria AlexanderTheme Two Intro
October 3, 2023
"Building a network early can create amazing opportunities further along the career path."
Laine Riley Prokay Lisa GordonCarving a Path for Early Career DesignOps Practitioners
September 9, 2022
Latest Books All books
Dig deeper with the Rosenbot
How could universal acceptance and personalized learning journeys change college admissions and education?
What are the benefits of linking AI-powered research repositories with tools like Slack for organizational adoption?
What HIPAA-compliant platforms are recommended for quickly developing healthcare apps?