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
"It is impossible to survive in this industry by pushing against the current all the time; you must put yourself in positions to leverage the current."
John CutlerOxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)
December 3, 2024
"When fellow co-workers label an individual as difficult, it's hard not to treat that individual as a problem."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"We’re all in this together and figuring it out — making it up as we go along."
Dave GrayGroup Activity: Making Sense of DesignOps
November 7, 2017
"A story lets people assign the meaning that's powerful to them and then think about the decisions they need to make and align."
John CutlerThe Alignment Trap
November 29, 2023
"Diagrams provide transparency in the face of uncertainty by showing what there is to know, even if the news is not good."
Abby CovertStuck? Diagrams Help
October 27, 2022
"Side-pav proposals answer what’s going on, why it matters now, what you propose, what action to take, and what benefit comes from it."
Mark InterranteCollaboration Flows in Product Development
June 9, 2017
"The metaverse has not summoned those angels; instead, it has brought in all the good and the bad from the real world."
Devon PowersImagining Better Futures
March 9, 2022
"Bring your research team as note takers and facilitators—they make excellent collaborators and help build feedback loops."
Prayag NarulaHow to Empower Your Designers to Do Good Research – And Why You Want To
June 10, 2022
"You can’t just be a designer adapting UX workflows assuming everybody else’s workflow stays the same; everything is changing with AI."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
Latest Books All books
Dig deeper with the Rosenbot
How does aligning on strategic objectives enable team autonomy and better prioritization?
What strategies help UX teams translate usability findings into stakeholder-relevant outcomes like cost savings or risk reduction?
Why is play and hands-on experimentation critical when teaching design and AI to new learners?