Scaling Accessibility Through Design Systems
Summary
Key Insights
-
•
Accessibility should be integrated early ('shift left') in the design and development process to reduce tech debt and remediation costs.
-
•
Automation tools catch about 30% of accessibility defects and cannot replace human audits and discernment.
-
•
Accessibility is often mistaken as limiting creativity, but it is actually a driver of innovation and inclusivity.
-
•
Unique naming for components like message bars is critical to avoid confusion for assistive technologies when multiple instances exist.
-
•
Breadcrumb navigation must not rely on color alone to convey meaning; it should be accessible through keyboard and screen readers and consider interactive behaviors.
-
•
Documenting accessibility decisions in design systems helps maintain consistency and educates users of the system.
-
•
Accessibility requires ongoing education and advocacy to get buy-in from diverse teams including designers, engineers, and product managers.
-
•
Small incremental changes to accessibility are better than no changes; it’s an ongoing journey rather than a one-time fix.
-
•
Accessibility levels range from inaccessible to legally compliant, usable, and ultimately innovative; compliance alone does not guarantee good UX.
-
•
Cross-functional collaboration and shared resources like accessibility one-pagers and bug-triaging spreadsheets improve scalability of accessibility efforts.
Notable Quotes
"Accessibility is innovation and this statement could potentially be some unchecked ableism."
"Automation only catches maybe 30% of all your a11y defects and even then we still receive a lot of false positives."
"I help you unlearn and relearn patterns so that you can build better products."
"If you’d rather exclude a group of people from using your product than do accessibility, then think about the impact you’re making."
"You can have a single page that’s got inaccessible, compliant, and accessible experiences all in one."
"No design system will ever be fully accessible because new features and permutations are always being introduced."
"Accessibility is a key component of user experience that has been neglected and requires specialists to close the gap."
"Small incremental changes are better than no changes at all from both the process and technical view."
"We’ve been taught to build fast and break things, and we often play accessibility on the back burner."
"Unique names for components like message bars are crucial, especially when multiple instances are shown at once."
Or choose a question:
More Videos
"We’re showing people how to collaborate like crazy and how to fail gracefully."
Phil GilbertA Consistent Culture of Design
May 14, 2015
"Design ops and product ops are way more alike than dissimilar; they differ mainly in the orgs they serve."
Rachel Posman John Calhoun"Ask Me Anything" with Rachel Posman and John Calhoun, Authors of the Upcoming Rosenfeld Book, The Design Conductors
September 25, 2024
"Our cohort facilitation sessions are one of the best parts of this conference."
Bria AlexanderOpening Remarks
June 10, 2021
"An agency developing shared technical infrastructure must market to itself why change is preferred, not just rely on top-down mandate."
Stefanie OwensOptimizing for Outcomes: Transformation Design in Systems at Scale
December 4, 2024
"You can control what happens to you but you can control how you respond to it."
Lisa GirondaOpener: Chief of Staff–An unexpected journey
January 8, 2024
"The lack of consistency between healthcare IT systems causes critical information delays and interrupted care."
Lais de Almeida Maria IzquierdoDesigning Data Services
December 4, 2024
"It’s about empowering a maker culture where the collective ‘we’ accomplishes something far beyond what any individual imagined."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"Prompt injection attacks can trick AI agents into accessing private data like emails without the user realizing."
Heidi TrostWhen AI Becomes the User’s Point Person—and Point of Failure
August 7, 2025
"If we don’t lead technology change, others will, and we want that change to be design-led and human-centered."
Greg PetroffEverything is About to Change: Software as Material
June 8, 2016
