Scaling Accessibility Through Design Systems
Summary
Incorporating accessibility can be seen as a daunting task, especially for products that have already been released. Alexis Lucio, Senior Accessibility Lead at Splunk, will share her journey in making accessibility a first-class citizen within Splunk Design System. Topics include: how to advocate for accessibility, utilizing use cases to optimize design and dev, how to utilize user input, and ideas on how to collaborate with cross-functional partners.
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
"Keep trying and iterating your design ops initiatives even if stakeholders resist at first."
Frances YllanaDesignOps–Leading the Path to Parity
April 27, 2023
"We developed this research framework during our time at Uber together with an extended leadership team as the team grew from 30 to 100."
George Zhang Molly StevensUX Research Excellence Framework
March 11, 2021
"The more participatory the practices, the deeper and more intentional the engagement needs to be."
Alexia Cohen Adriane AckermanIncreasing Health Equity and Improving the Service Experience for Under-Served Latine Communities in Arizona
December 4, 2024
"Most people have a marketing or sales strategy, but many research leaders look puzzled when asked about their research strategy."
Chris Geison Cristen Torrey Eric MahlstedtWhat is Research Strategy?: A Panel of Research Leaders Discuss this Emergent Question
March 4, 2021
"Design requires teams because you can't be expert in everything—from pixels to hardware to databases."
Paul Pangaro, PhDSystems Disciplines: Table Stakes for 21st Century Organizations
June 6, 2023
"Dynamic permission management and turning on SSO or SIEM help manage tools at scale without nano work."
Farid SabitovTheme Four Intro
September 9, 2022
"Designing for change means focusing on learnability and product consumability, not just ease of use."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"Sometimes minor questions don’t matter much, and AI can help get those out of the way so researchers focus on strategic work."
Taylor Jennings Alexis McNutt Unis Sydney LawsonResearch Debate Club
March 11, 2026
"Junk in, junk out. Bad data is worse than no data at all."
Jemma Ahmed Steve Carrod Chris Geison Dr. Shadi Janansefat Christopher NashDemocratization: Working with it, not against it [Advancing Research Community Workshop Series]
July 24, 2024