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
"Use the latest version starring feature so your team only gets updates when they’re ready, avoiding constant notifications."
Jaime CreixemsBest Practices when Creating and Maintaining a Design System
June 7, 2023
"Design thinking has helped raise awareness but often lacks the depth of design practice which requires dedicated craft."
Jorge ArangoDesign as an Antidote to VUCA
May 9, 2019
"I love that clients don’t actually care what I call myself as long as I’m helping them achieve great outcomes."
Rebecca BuckMission: Keep Talent in Research Roles!
March 10, 2021
"We’re always taking suggestions for new apps to add to the tools map for later iterations."
JP Allen Holly HoldenNavigating the UX Tools Landscape
October 1, 2021
"Throwing away old methods for something new can unlock skills you didn’t know you had."
John DonmoyerShipping your code generation experiments to production
June 11, 2025
"We used standard metrics like task success, time to complete, number of errors, confidence, and delight."
Discussion
June 9, 2017
"When you get lonely, battle that loneliness by identifying allies and people you can trust in your organization and the design ops community."
Jackie AjouxLeveling-Up: A Single-Player’s Guide to the DesignOps Team-of-One
January 8, 2024
"We used design principles like look but don't copy, this is a calculator not a person, and no gamification to guide tough decisions."
Aras BilgenWho does the math: A designer’s journey in building an AI-based tutoring app
June 10, 2025
"Hiring people who are relentlessly seeking improvement will grow your team and your work."
Rachel Radway Katie Bingham Joe WiertelThe Many Paths Of Design Operations
September 8, 2022
