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 process was do what you want, I’m cool with that. Nobody really cared what others did, which created silos of indifference."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Design operations focuses not only on designers but on how designers work with other disciplines to increase speed, efficiency, and quality."
Farid SabitovAutomatization for Large Enterprise Teams
January 8, 2024
"I just said yes to everything climate-related until I found the right fit."
Louis Rosenfeld Matt Jones Olga Khroustaleva Michael Leggett Karol MunozDo you want to work on climate? (Climate UX Discussion Series)
November 15, 2023
"Big picture thinkers move past obstacles and create unexpected paths and new solutions."
Sol MeszHands or Brains? How to Hire for Strategy, Strategically
January 8, 2024
"ChatGPT’s approach in analogy generation segmented the narrative into unrelated metaphors, which confused the overall story."
Weidan LiQualitative synthesis with ChatGPT: Better or worse than human intelligence?
June 4, 2024
"Discovery doesn’t usually come with a launch party or even its own Jira ticket, but it’s what turns speed into progress."
Bianca JeffersonFrom Sprints to Systems: Operationalizing Continuous Discovery Through DesignOps
September 10, 2025
"Continuous Discovery runs every two to three weeks with dedicated researchers tied to specific product journeys."
Jen Cardello Jennifer OttoLearning Velocity—The Insights Speedometer
September 16, 2021
"Tracking implementation commitments after each design network group keeps momentum and accountability."
Prerna MakanawalaAchieving Balanced Design Consistency
June 9, 2021
"Upskilling customer success managers and others to help with testing meant we could do far more research than I alone could manage."
Dr Chloe SharpUsing Evidence and Collaboration for Setting and Defending Priorities
November 29, 2023
