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, within the public sector, 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
-
•
Start accessibility testing with screen magnification users because they can interpret visual prototypes with minimal adaptation.
-
•
Involving users with physical challenges requires clear indications of hover states, control labels, click target sizes, and may require operating prototypes on their behalf.
-
•
Screen reader users cannot effectively use typical visual prototypes because they lack semantic markup; alternative prototyping using structured documents is necessary.
-
•
Accessibility testing should expand in a circle: from screen magnification to physical challenges, then to screen readers.
-
•
Addressing accessibility issues for one group often benefits other groups, creating a positive cascading effect.
-
•
Prototypes frequently lack critical information like semantic structure, focus states, keyboard navigation, and alt text needed by screen reader users.
-
•
Prototyping tools like Webflow support coding prototypes that better simulate real assistive technology environments but require technical expertise.
-
•
Considering platform differences (Windows, Mac, iOS, Android) is essential as assistive technologies behave differently across them.
-
•
Excessive white space can hinder usability for screen magnification users by forcing excessive scrolling.
-
•
Early involvement of people with disabilities in design avoids costly retrofits and leads to more effective accessibility solutions.
Notable Quotes
"The best way to build a fully accessible foundation is to involve the voices of people with disabilities at every step."
"Screen magnification users are low vision and interact visually with prototypes, so little adaptation is needed."
"For users with physical challenges, hover states can be very difficult, especially for eye, head tracking, or voice control users."
"Screen reader users require prototypes that contain semantic information like heading levels, control labels, and landmarks."
"You may need to operate the prototype on behalf of users whose assistive tech can’t click or interact with clickable prototypes."
"Fixing problems found for one disability group often helps fix problems for others too."
"When you magnify prototypes, they may look blurry, but that’s something to fix in the final website design."
"Webflow is an ideal tool for prototypes with code because users can test in the actual browser environment."
"Aim to work with at least one person on each platform your product supports, because assistive tech varies."
"You can create prototypes for screen reader users in Word, Excel, or Google Docs by simulating semantic markup."
Or choose a question:
More Videos
"I approached design not from the context of user experience first, but from what job we’re trying to satisfy for our customers."
Dantley DavisLeadership & Diversity—A Fireside Chat with Dantley Davis
September 17, 2020
"AI can help us develop better alt text for images, which improves accessibility for unsighted users."
Frances Yllana Jorge Arango Maria Taylor Briana ThomasThe Big Question about Impact: A Panel Discussion
September 24, 2024
"The journey is from guilt to atonement—not necessarily forgiveness—but being integrated into society."
Jim KalbachPeace is waged with sticky notes: Mapping Real-World Experiences
June 14, 2018
"The pod system gave leads more credibility and leadership opportunities while supporting junior growth."
Sarah Kinkade Mariana Ortiz-ReyesDesign Management Models in the Face of Transformation
June 8, 2022
"Watch your language; terms like 'that's so lame' can be exclusionary or offensive."
Reginé GilbertAsking the Right Questions: Life, Hope and Moving Forward During the Pandemic
June 10, 2022
"We’re not going back to stability; we’re riding this wave of perpetual upheaval and must learn to surf it."
Robin BeersNavigating organizational systems: Rethinking researcher’s role in driving change
March 13, 2025
"Are we an agency that is also kind of a product? Is the agency a product? The product an agency? We’re an agenuct? No, pragency."
Paul FordNew work, new words: A glossary for AI
June 9, 2026
"If you don’t continually check whether people are benefiting, the system’s reputation can quickly suffer."
Dan DonaldDesign Systems as a Vehicle for Systemic Change
June 1, 2023
"You get real coded components, not just HTML snippets or style attributes, meaning developers can drag, drop, and extend with hooks already in place."
George Abraham Stefan IvanovDesign Systems To-Go: Reimagining Developer Handoff, and Introducing App Builder (Part 2)
October 1, 2021
Latest Books All books
Dig deeper with the Rosenbot
In what ways can talking to a financial advisor change retirement planning for tech professionals?
What strategies help designers manage executives who overestimate AI’s ability to replace skilled work?
How have foreseeable harms in social media and gig economy platforms been linked to power imbalances?