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
"Screen readers let us jump from one heading to another, replicating the experience of skimming a page visually."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
"Most of our designers are contractors; they have limited voice because they’re bound by contracts."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"The rebrand caused our NPS to plummet and freaked out our executives — that was the trigger to get serious."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"If you’re amazing at your job but no one listens to your research or design, does it really have impact?"
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"The chief of staff serves as a bridge between the design program managers, executive assistants, and other ux and product chiefs of staff."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"Starting with one line of business and showing success creates a trickle effect for broader organizational adoption."
Amy EvansHow to Create Change
September 25, 2024
"Design ops is undergoing a transformation into a CX focused team with a refined mission to drive efficiency and customer experience excellence."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"The higher up you are in an organization, the more distorted your reality is likely to be."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"You have to push against 200,000 years of human evolution to get researchers to create reusable knowledge."
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020
