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
"There is no silver bullet in system-level challenges; multiple interventions across different domains are needed."
Sheryl CababaExpanding Your Design Lens with Systems Thinking
February 23, 2023
"Staff working against long backlogs are inherently stretched for time, so engagement needs to be efficient and sensitive."
Ed MullenDesigning the Unseen: Enabling Institutions to Build Public Trust
November 16, 2022
"The curse of good enough is a real trap that we’re grappling with."
Steve PortigalLooking Back…to Look Ahead
March 26, 2024
"We are sensemakers. No matter what data we are given, we make sense of it."
Jemma AhmedTheme 1 Intro
March 10, 2026
"It's commonplace for at least two browsers to be available because some critical web-based tools work on some browsers and not on others."
Sharon BautistaTime to Make the Donuts: How User Research Helped Bridge Disparate Teams
January 8, 2024
"Teams with different thought worlds should start with who they are, what their roles are, and their passions inside and outside work."
Lin NieWhen Thought-worlds Collide: Collaborating Between Research and Practice
March 10, 2021
"It’s not on researchers to simply be resilient — systems and structures need to adapt and support them."
Brian MossWhat Does it Mean to be a Resilient Research Team?
March 9, 2022
"Design talent is the most valuable asset; empowering them to be part of decisions retains and motivates them."
Prerna MakanawalaAchieving Balanced Design Consistency
June 9, 2021
"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
