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
"Service designers are best placed to make inclusive design the default, not the exception."
Samuel ProulxFrom Standards to Innovation: Why Inclusive Design Wins
November 19, 2025
"Manuel Herrera is here to take the burden of note-taking off us, so you can focus on the moment."
Louis Rosenfeld Bria AlexanderOpening Remarks
October 2, 2023
"Aim to work with at least one person on each platform your product supports, because assistive tech varies."
Sam ProulxPrototype Reviews, People With Disabilities, and You
December 8, 2021
"This day continues threads heard in previous days, now focused on physical public spaces."
Sarah BrooksTheme Three Intro
November 18, 2022
"Artificial intelligence promises new independence for people with disabilities but raises questions of bias and privacy."
Sam ProulxTo Boldly Go: The New Frontiers of Accessibility
September 9, 2022
"If we stay focused on research maturity alone, we'll have problems in the coming years because the ecosystem around us is changing."
Megan Blocker Lada Gorlenko Fatimah Richmond Molly StevensWhat UX research maturity looks like and how we get there [Advancing Research Community Workshop Series]
November 9, 2023
"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
"If we don’t respect legacy habits, we risk interrupting workflows and causing users to have a bad day."
Paula BachImproving Legacy Software: How Much Better Does it Have to Be?
March 11, 2022
"I try to position the system as an enabling force for designers to succeed better, not as confines or limits."
Nathan Curtis Nalini P. Kotamraju Jack Moffett Dawn ResselDiscussion
June 9, 2016
Latest Books All books
Dig deeper with the Rosenbot
How can service designers socialize their role effectively within organizations dominated by non-design logics?
Why is changing incentive and reward systems crucial for successful OKR adoption?
How can visualization techniques demonstrate the measurable impact of behind-the-scenes service design work?