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
"Value of design is never going to get a single answer because you need the who, what, and why."
Sarah CoyleDesign and Analytics with Sarah Coyle
July 30, 2020
"My job was to find out why. Why was he frowning? Why was he sighing?"
Susan Simon-DanielsWar Stories LIVE! Susan Simon-Daniels
March 30, 2020
"There’s a big discrepancy between accessible consumer AI and what deep research-driven AI can do - Brittany."
Bria Alexander Brittany Hobbs Christopher NoesselDay 1 Panel: Up to the Minute: The latest in AI’s impact on UX
June 10, 2025
"Fourth order design is about understanding system structure and intervening to create new pathways of experience."
Richard BuchananCreativity and Principles in the Flourishing Enterprise
June 15, 2018
"Sometimes you have to fill a need even if there’s no formal name or structure for it yet."
Rob Mitzel Sébastien MaloThe Tale of Two Companies: Building a Successful UX Practice in a Century-Old Enterprise
January 8, 2024
"Short-term learnings kind of roll into long-term ones as you iterate and build on historical findings."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"Developers have their heads down coding; they don’t think about grid intensity or carbon impact."
Tristin OldaniTurning awareness into action with Climate UX
January 16, 2025
"The design system started as a scrappy corner initiative of designers doing the right thing."
Nalini P. KotamrajuAn Organizational Story: Salesforce Lightning Design System
June 9, 2016
"What am I personally doing to contribute to the dynamics that stand in the way of better futures?"
Chris GeisonTheme 1 Intro
March 9, 2022
