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
"Low vision users often invert colors and use magnification levels as high as 400 percent to reduce eye strain."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
"The biggest bottleneck is the bureaucracy, like the Paperwork Reduction Act, we have to creatively navigate that."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"I tried to do everything all by myself at first and it didn’t catch on because no one else knew I was doing it."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"People care about titles way too much. I had a guy whose business card said star-bellied sneak—love that."
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
"We categorized all our work into may-do, must-do, and desire-to-do buckets to better allocate our efforts."
Amy EvansHow to Create Change
September 25, 2024
"You should take risks, and if you fail, you need to fail fast and pivot immediately."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"It’s impossible to be angry with a warm cup of tea in your hand."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"Providing immediate tactical value is the big one for just-in-time curation."
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020
