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
"I promise chief design evangelism is not religious."
Shipra KayanMake your research synthesis speedy and more collaborative using a canvas
January 24, 2025
"Sometimes you need somebody else to tell you something obvious, like consultants should not be expected to know everything upfront."
Smitha Papolu Nova Wehman-Brown Melissa Schmidt Adam MenterTheme 3 Discussion
January 8, 2024
"If you can’t see how this artifact is going to be a reference that is constantly pointed to, maybe you shouldn’t make it."
Catt SmallCraft a Vision that Actually Gets Shipped
April 30, 2026
"Research evangelization is the highest rated in usefulness among researchers with over 12 years’ experience."
Dave HoraA Research Skills Evolution
March 10, 2021
"Sometimes it’s reasonable to consider your design as strategy and ship a piece now and other pieces later."
Scott Jensen Sarah Delaney Carmen LiuShort Take #2: UX/Product Lessons from Your Industry Peers
December 6, 2022
"A tabletop exercise is like we’re all on the same team building a plan, but a war game is competition against other teams."
Terry BuckmanWargaming (An Introduction)
August 10, 2023
"At Hotcho, we started with a qualitative focus, swung too far into quantitative, and then found a balanced middle ground."
Andrew MichaelBuilding a Product Insights Team
March 10, 2022
"No tracking is perfect because numbers tell you what likely happened, but not why it happened."
Erin WeigelUX Lessons from running more than 1,200 A/B Tests
July 10, 2024
"We believe in coexistence of our tool, ChatGPT, and real customer visits where possible."
Joerg Beringer Thomas GeisScaling User Research with AI: Continuous Discovery of User Needs in Minutes
June 10, 2025
