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 the biggest impact with the least adaptation needed.
-
•
Screen magnification users benefit from simply enlarging visuals, color contrast changes, and panning, making graphical prototypes easily accessible.
-
•
Users with physical challenges often struggle with hover states and unlabeled controls, requiring adaptations or researcher assistance during prototype reviews.
-
•
Screen reader users are the hardest group to include in prototype reviews because graphical prototypes lack semantic structure needed for screen readers to interpret.
-
•
Prototypes for screen reader users often must be recreated in text-based formats like Microsoft Word or Google Docs to represent semantic layout accurately.
-
•
Design systems like Figma and Adobe XD generally do not natively support screen reader-compatible prototypes, though progress is underway.
-
•
Accessibility reviews should include checking control labeling consistency to match voice commands for users relying on voice dictation or alternative navigation.
-
•
Large white space becomes a major concern for screen magnification users as it can consume excessive screen real estate when magnified.
-
•
Mobile app accessibility concerns largely mirror desktop issues, differing mainly in screen size and gesture input.
-
•
Companies like Adobe are leading active research efforts into improving prototyping tools for better accessibility support, especially for screen reader users.
Notable Quotes
"Including people with disabilities in prototype reviews can be a little different based on the assistive technology someone uses and their needs."
"Screen magnification users see everything bigger but have less available screen real estate, so they pan around a lot more."
"The best bang for your buck with least effort is to start with screen magnification users in your prototype reviews."
"Users with physical challenges often cannot hover easily, so prototypes need to indicate where hover is required and how sensitive it is."
"Significant adaptation is required to involve screen reader users in prototype reviews because prototypes are graphical and lack semantic markup."
"Microsoft Excel, Google Docs, and Word are surprisingly good places to build screen reader accessible prototypes using semantic labels and structures."
"When working with screen reader users in prototype reviews, you have to simulate the screen reader experience with them interactively."
"There is a lot of research going on to make screen reader accessible prototypes easier to build, but right now it’s early to mid-stage."
"Control labels need to be consistent because people using voice dictation rely on those labels to interact with controls."
"Mobile accessibility testing isn’t fundamentally different from desktop; it mainly comes down to screen size and gesture differences."
Or choose a question:
More Videos
"The hardest part about remote is making design reviews feel collaborative and team-based."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"Many product managers got their roles because they know the business or subject matter, but they don’t know how to manage product development."
Peter MerholzThe Trials and Tribulations of Directors of UX (Videoconference)
July 13, 2023
"Governance is about decision making, not workflow processes."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"Green spaces in cities can greatly enhance our quality of life and resilience."
Vincent BrathwaiteOpener: Past, Present, and Future—Closing the Racial Divide in Design Teams
October 22, 2020
"If you forget the individual, you cut out psychological safety, and that’s the foundation of strong teams."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Hip hop proves that we can re-animate spaces with highly generative communities that weren't built for us."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Creating hypotheses from pain points with measurable success criteria helped prioritize which to pursue."
Edgar Anzaldua MorenoUsing Research to Determine Unique Value Proposition
March 11, 2021
"Our brains are terrible at operating only on one type of information, whether object-oriented or context-oriented."
Designing Systems at Scale
November 7, 2018
"The conversion design process creates collective knowledge, which gets reinfused to strengthen future experiments."
Erin WeigelGet Your Whole Team Testing to Design for Impact
July 24, 2024
