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
"The secondary first, primary second sequence may seem a numerical mismatch, but it is the way to go."
Joerg Beringer Thomas GeisScaling User Research with AI: Continuous Discovery of User Needs in Minutes
September 10, 2025
"We do not have online indicators in our communication software, so people know they shouldn’t wait for an immediate response."
Ana FerreiraDesigning Distributed: Leading Doist’s Fully Remote Design Team in Six Countries
January 8, 2024
"The next big thing will be knowledge management powered by new no-code and integrative tools."
Deanna Washington Bria Alexander Jon Fukuda Saara Kamppari-Miller Farid SabitovConnecting the Ops: Plenary Panel and Closing Circle
September 9, 2022
"Everyone has a different context—teams, culture, and history—that shapes how they work and think."
Sean McKayWhole Product Thinking: Expanding beyond problem and solution space thinking
March 14, 2024
"Who do builders become in this new future AI universe and how do we play together?"
Aletheia DelivreNew Shapes and Emerging Identities for Design Ops
September 11, 2025
"Too often journeys are these beautiful artifacts that no one actually understands or uses."
Sean DolanA Practical Look at Creating More Usable Enterprise Customer Journeys
October 31, 2019
"The skills we hold are exactly the skills that this moment requires."
Jemma AhmedTheme 1 Intro
March 10, 2026
"Vibe coding turns the conversation 'should designers code?' on its head — now designers can just talk to bots."
Christian CrumlishThe Pygmalion Effect: In Which a Vibe Coding Experiment Becomes a Million Lines…
August 14, 2025
"Why am I talking? Sometimes it’s better to ask a question and be silent."
Laura WeissThere is No Playbook: Leader as Coach During Challenging Times
April 26, 2024
