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
"People don’t always get straight to their question; they might need to do some investigation first before they figure out what to ask."
Liwei DaiThe Heart and Brain of the AI Research
March 31, 2020
"We cannot be everywhere. So is the goal to conduct more studies faster? And we said no, it’s not. That’s poison."
Jen Cardello Jennifer OttoLearning Velocity—The Insights Speedometer
September 16, 2021
"You have to sometimes extend research timelines and ask hard questions to understand diverse needs."
Lija HoganPractical Principles of Inclusive Research
March 27, 2023
"If you get the interview, say, I don’t have experience in that field, but here’s how I solved similar complex problems."
Dave Hoffer Joanne WeaverUX Job Search AMA #2 with Joanne Weaver and Dave Hoffer
May 21, 2025
"The success of SLDS is not about the technology itself but about people and relationships."
Nalini P. KotamrajuAn Organizational Story: Salesforce Lightning Design System
June 9, 2016
"The issue is not research ops being more organized researchers — the problems and scale are very different."
Kate TowseyThe State of ResearchOps: More Than Just Theory
June 20, 2019
"Running AI categorization on 2000 posts took 38 hours, $19, and as much carbon as driving a 1998 Chevy Malibu from Philly to Brooklyn."
Karen McGrane Jeff EatonAI for Information Architects: Are the robots coming for our jobs?
November 21, 2024
"If you don’t trust it, then there’s nothing here."
Daniel J. RosenbergDesigning with and for Artificial Intelligence
August 11, 2022
"I gave birth to two things at once: my talk and my son Mateo within two days."
Smitha Papolu Nova Wehman-Brown Melissa Schmidt Adam MenterTheme 3 Discussion
January 8, 2024
Latest Books All books
Dig deeper with the Rosenbot
How does embedding interactivity directly into SVG files help designers independent of developers?
Why is it important not to wait for organizational permission when pursuing new UX-related initiatives?
What are the emotional and physical health impacts after leaving a high-pressure UX leadership role?