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
"You want to flex one or two variables to create range scenarios—best case, middle case, and worst case."
Giff ConstableFinancial fluency for product leaders: AMA with Giff Constable
April 11, 2024
"We are designing how the assistant is trying to reason, moving from scripting responses to orchestrating the AI's cognitive process."
Kritika YadavOptimizing AI Conversations: A Case Study on Personalized Shopping Assistance Frameworks
June 10, 2025
"Meetings tell us what kind of conversations we are having and what kind of conversations we are not having."
Alla WeinbergHow to Build and Scale Team Safety
January 8, 2024
"Deceptive patterns in cookie banners give users false choices that make it harder to reject tracking."
Harry Brignull Mark Leiser Robert StribleyBeyond Clicks and Tricks: Why deceptive design has grown into a regulatory faultline
January 16, 2026
"Design teams often don’t have enough people to support everything being asked of them."
Kit UngerTheme 2: Introduction
June 10, 2021
"If you don’t have the time and organizational support, don’t do it because you only set a precedent of failure."
Sofia QuinteroBeyond Tools: The Messy Business of Implementing Research Repositories
March 10, 2022
"You want to move from ‘make me a thing’ to ‘change customer behavior.’ That’s where the magic is."
Jeff GothelfThe Intersection of Lean and Design
January 10, 2019
"In our desire to see the big table, we often forget that sometimes it’s more important not to seek validation at the table but to offer it to someone else."
Kit Unger Lada GorlenkoTheme 3 Intro
June 10, 2022
"Avoid getting sidetracked by tools and processes so you can focus on the actual work those notes help enable."
Jorge ArangoThe Best of Both Worlds: How to Integrate Paper and Digital Notes (1st of 3 seminars)
April 5, 2024
