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
"Participant recruitment was the number one problem that people mentioned."
Veevi RosensteinBuilding for Scale: Creating the Zendesk UX Research Practice
January 8, 2024
"The Gender Shades project exposed how facial recognition algorithms had up to a 33% error rate disparity between demographic groups."
Joel BranchHumanizing AI: Filling the Gaps with Multi-faceted Research
March 11, 2021
"It’s not just an admin task; knowledge management provides agency and enabling information to the entire team and organization."
Sean Baker Sara RomanoskiWeaving Knowledge Management into the Fabric of Our Design Practice
September 11, 2025
"We segment sessions into 101 and 201 tracks so people new to IBM and more experienced can both get value without being bored or overwhelmed."
Nicole UmphressDelivering Design Education During a Global Pandemic: Lessons Learned
June 9, 2022
"Civic design and government design practice have reached many milestones in the past 10 years."
Kara KaneTheme One Intro
November 16, 2022
"If you can’t measure the impact and scale of a problem, then it’s hard to communicate that the problem exists or the value of a UX team that could possibly solve it."
JD BuckleyCommunicating the ROI of UX within a large enterprise and out on the streets
June 14, 2018
"If you get eight people who give a crap together, you can start a federal agency."
Juhan SoninDesign Now! The Agenda for Action
September 4, 2025
"The research-practice gap frustrates me, and I try to bridge it when it makes sense to."
Lin NieWhen Thought-worlds Collide: Collaborating Between Research and Practice
March 10, 2021
"Vivo Pulse helps with rapid iterations, while Vivo Pro validates signals with real users."
Gillian Salerno-Rebic Mark MicheliRedefining Speed and Scale: How Accenture’s GrowthOS Uses AI-Simulated Insights to Reduce Risk and Accelerate Innovation
June 10, 2025
Latest Books All books
Dig deeper with the Rosenbot
When should specialized researchers be involved in a research study based on problem clarity and risk?
How can teams integrate inclusive design into early product development stages to avoid costly late fixes?
What lessons did Bethany share about balancing ambition and credibility in AI transformation?