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
"The Ab Builder is a collaborative workspace where designers and developers have synchronized component libraries and themes."
George Abraham Stefan IvanovDesign Systems To-Go: Reimagining Developer Handoff, and Introducing App Builder (Part 2)
October 1, 2021
"The rocking chair test helps you evaluate if you’re living a life you won’t regret when you’re old."
Greg PetroffDesign is the Differentiator: Bringing New Design Innovations to a Very Antiquated and Very Large Industry
June 9, 2021
"Psychological safety is key—if folks aren't in the right state, the conversation isn't productive."
Joshua GravesWe Need To Talk: Managing Ludicrous Requests at Work (Part 3 of 3)
May 12, 2025
"We don’t use yesterday’s retail playbook to solve problems for today — that’s impossible."
Sara Asche Anderson Jamie KaspszakNot Your Ordinary Re-Brand: Design's Path to Driving Customer Obsession at Best Buy
January 8, 2024
"If we all implement one small impactful thing in our projects, that can lead to meaningful change."
Tristin OldaniTurning awareness into action with Climate UX
January 16, 2025
"Emergence is a property where individual independent actions create a collective behavior like a school of fish moving together."
Erin Hoffman-JohnThis Game is Never Done: Design Leadership Techniques from the Video Game World
November 6, 2017
"Mobile screens have forced designers to create simplified interfaces without reducing features."
Sam ProulxMobile Accessibility and You
June 9, 2022
"Process is a scary word because smart people do not like to be told what to do."
Michelle MorrisonPractice What You Preach
January 8, 2024
"We’re not studying products anymore; we’re studying experiences in ecosystems."
Jonathan Fairman Kevin JohnsonIntegrating generative AI into enterprise products: A case study from dscout
June 5, 2024
