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
"We confuse that solution with what our clients have actually asked for or wanted or need. We need to allow for design to do what it does best, which is understanding problems and people."
Brianna SylverLead With Purpose
March 31, 2020
"Eventually, I expect AI to help create designs by combining patterns from meta design systems and research, making design more about crafting experiences."
Abby Covert Tomer SharonPanel: Collaboration Tools
November 6, 2017
"We’re in this initial stage of tinkering, just trying to make the tech behave the way we expect it to."
Sheryl Cababa Ethan Marcotte Milena PribicDay 2 Panel
June 5, 2024
"Sometimes you have to make it messy before it can be clean again — disrupt to improve."
Liza Pemstein Jane DavisScaling Research Via an Ops First Model at Clever
March 27, 2023
"You can never be sick enough to help the sickest people."
Deanna ZandtThe Unspoken Complexity of “Self-Care” with Deanna Zandt
July 21, 2022
"The team can now tell the World Service what to do, not just what the audience thinks."
Catherine BlizzardUsing Integrated Insight to Drive Growth
March 10, 2022
"We need secure defaults that protect users out of the box without them having to figure it out."
Heidi TrostWhen AI Becomes the User’s Point Person—and Point of Failure
August 7, 2025
"We needed a framework to know what we don’t know and prioritize secondary inclusive research."
Saara Kamppari-MillerInclusive Design is DesignOps
September 29, 2021
"Designers would often say, I didn’t realize research was this hard or what you go through is traumatic."
Marjorie Stainback Kelsey KingmanTransforming Strategic Research Capacity through Democratization
October 24, 2019
