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
"Search alone doesn’t cut it, particularly when people don’t know what they’re looking for or lack context."
Jorge ArangoScale Smart: AI-Powered Content Organization Strategies
September 24, 2024
"The biggest problem was to solve the engagement problem first with the sponsor, then the team, then external stakeholders."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"If you put one person across three teams, every day they have to decide who they’re going to piss off."
Jeff GothelfThe Intersection of Lean and Design
January 10, 2019
"Ethics must live in the practitioner; companies are not people and cannot embody ethics without individuals choosing to do so."
Mariah HayEthics in Tech Education: Designing to Provide Opportunity for All
June 14, 2018
"Developers have their heads down coding; they don’t think about grid intensity or carbon impact."
Tristin OldaniTurning awareness into action with Climate UX
January 16, 2025
"You’re never going to convince business people with product language, but you can with financial language they care about."
Giff ConstableFinancial fluency for product leaders: AMA with Giff Constable
April 11, 2024
"Qualitative research is excellent for discovering needs but poor at quantifying their scale or priority."
Michaela MoraAdvanced Concept Testing Approaches To Guide Product Development and Business Decisions
March 11, 2022
"Imagine a world where research bots at IBM talk to the Rosen bot to give you better guidance on interpreting research."
Louis RosenfeldThe Rosenbot and the Rosenverse: An AMA with Lou Rosenfeld
June 5, 2024
"Customer value outcomes should drive empowered product teams rather than technical outputs or budgets."
Sabrina Mach Nina WainwrightHow to Design Your Design Operating Model
September 29, 2021
