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
"Without a design ops function, teams make their own flavors that dilute brand and accessibility."
Rachael Greene Alison DavisBuilding a Design Ops Practice that Really Works (Most of the Time)
October 2, 2025
"Personal resiliency is no match for environmental toxicity."
Kat VellosOpener: The Other L Word
January 8, 2024
"You should not try to deliver your playbook from the ivory tower of design ops. It just will not be successful."
Gabrielle VerderberDocumentation Your Team Will Actually Use
October 3, 2023
"ESPN’s site is a great example of poor hierarchy and alignment — it’s hard to know where to start or where to go next."
Billy CarlsonPro-level UI Tips for Beginners
September 9, 2022
"It's all of our job to question why we’re doing what we’re doing and how we’re doing it."
Maria SkaadenPanel Discussion: Methodologies and Work Environments
November 8, 2018
"Even though we’re user researchers, we’re not looking at digital products — our users often include people suffering homelessness, addiction, or trauma."
Brian MossWhat Does it Mean to be a Resilient Research Team?
March 9, 2022
"We want to send fewer mailers but make them more impactful, using A/B testing to optimize open and click rates."
Kristin WisnewskiMeasuring What Matters
October 23, 2019
"Humans tend to give too much authority to autonomous systems, which can lead to overtrust."
Helen ArmstrongAugment the Human. Interrogate the System.
June 7, 2023
"Please keep your questions within the speaker’s thread so we don’t lose track of them in the busy chat."
Bria AlexanderOpening Remarks
September 9, 2022
