Integrating Accessibility in DesignOps
Summary
Key Insights
-
•
Build an active panel of participants with accessibility needs focused on user requirements, not medical disability labels.
-
•
Recruiting from existing communities like customers, employees, or accessibility vendors reduces the burden of building a panel from scratch.
-
•
Ask about specific user needs like captioning, magnification, or navigation challenges instead of asking directly about disabilities.
-
•
Accessibility research should be integrated with general user research, balancing fewer general population participants with more accessibility participants.
-
•
Prototyping sessions must be adjusted to participant needs, including screen sharing, live captioning, or sign language support.
-
•
Rapid iteration with 3-5 users per phase (needs discovery, prototype testing, usability validation) accelerates inclusive design without overwhelming teams.
-
•
Automated accessibility tools complement but cannot replace testing with actual users with disabilities.
-
•
Design systems require testing of both foundational elements (like color, typography) and interactive components in real code for accessibility.
-
•
Accessibility documentation and annotation integrated within design tools (e.g., Figma widgets) help communicate user feedback to design and engineering teams.
-
•
Continuous evaluation of design system components in production is necessary to catch new accessibility barriers caused by integration conflicts or third-party tools.
Notable Quotes
"I recommend asking about user needs rather than disability, like whether someone needs captions or larger fonts."
"If you only have five people with disabilities available for research, it can be hard to get the scale you need."
"Accessibility research is part of overall user research; including people with accessibility needs can replace some general population participants."
"Automated tools find many issues at scale, but user testing finds problems those tools can't detect. They pair really nicely."
"It's cheaper to fix accessibility issues in the design phase than to wait until after coding or production."
"Testing with people who have low vision shows that even passing contrast ratios can still result in unreadable text if font weights are too thin."
"One of the best places to start is just learning about assistive technologies: what exists and how they work."
"Rapid iteration with three to five user interviews is often enough to inform design and validate accessibility effectively."
"When sharing prototypes that aren't accessible, facilitators may need to control the prototype and follow user directions."
"Create documentation around accessibility for your design system that includes user needs, testing methods, and panel access."
Or choose a question:
More Videos
"UX really doesn’t have a seat at the table yet and that has some implications for us."
Rich MironovHow Can Product Managers and UXers Help Each Other (and Why are Product Folks so Annoying Sometimes)?
December 6, 2022
"Every talk you hear today couldn’t get more personal to our community."
Bria AlexanderTheme Two Intro
October 3, 2023
"I am usually the only designer on the team, and it gets difficult to get the information needed for design decisions."
Ruzanna RozmanGetting in Flow with Your Team
January 8, 2024
"We unapologetically move forward when high-level stakeholders miss deadlines, but also collect feedback via surveys."
Briana Thomas Christina RodriguezWhen Design Ops Comes in H.O.T. : A Tale of a Transformed Design Org
September 30, 2021
"Every experience at the VA is broken in its own way."
Marina MartinLives on the Line: The Stakes of UX at the Scale of Government
June 14, 2018
"Scaling up research impact means turning visibility way up and opening access despite some risk of misuse."
Jake BurghardtStop wasting research: Create new value with insight summaries
July 9, 2025
"If we test now, we’ll save two or three iterations waiting for organic user feedback later."
Clemens Janssen Jane DavisEfficiently Scaling Research as a Team of One
March 28, 2023
"We’re entering an information era because information itself is infrastructure and has actual monetary value."
Bram WesselEnterprise Information Architecture
January 10, 2020
"The town of Carlsgo wasn't consciously disadvantaging women, they were just following a best practice that ignored different experiences."
Kaitlin TaskerFast and Fearless Inclusive Research
March 27, 2023
