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."
Dig deeper—ask the Rosenbot:
More Videos
"In order to lead change, you turn change itself into the product."
Doug PowellDesignOps and the Next Frontier: Leading Through Unpredictable Change
September 11, 2025
"You don't want to hide away for six months and try to build the perfect documentation. It won't work."
Gabrielle VerderberDocumentation Your Team Will Actually Use
October 3, 2023
"Using a screen reader demo helps leadership hear firsthand why accessibility matters and gain buy-in."
Suzan Bednarz Hilary SunderlandAccessibilityOps for All
January 8, 2024
"It matters what you build, but it matters more if you learn."
Brenna FallonLearning Over Outcomes
October 24, 2019
"Green spaces are not luxuries—they're necessities for urban life."
Ali Jeffery Sheri ChudowHow DesignOps Helped Enable Wall Street to Work Remotely
October 22, 2020
"There’s a huge opportunity in transitioning people from other disciplines into design roles."
Nick CochranGrowing in Enterprise Design through Making Connections
June 3, 2019
"Scaled Agile felt at first like a step backwards—design looked like just the finishing touch, not a key ingredient."
Erin HauberDesign is Not the Frosting on the Scaled Agile Layer Cake
October 24, 2019
"We’re not building to build, we’re building to learn."
Maria SkaadenContinuous Design: One eye on the horizon and the other on the next wave
November 8, 2018
"Everybody has something to say, whether it’s a personal narrative or a feature implementation. So we run writing workshops quarterly."
Michelle MorrisonCulture Design
May 21, 2020
