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
"Before we started this process, we banned words like designer and prototype."
Saara Kamppari-Miller"Prototype" vs "Prototype"--Breaking Down and Rebuilding Our Understanding of What We Do
October 24, 2019
"Short-term learnings kind of roll into long-term ones as you iterate and build on historical findings."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"Connecting strings of Christmas lights is a mental model for connecting teams’ insights without superseding their systems."
Etienne FangPower of Insights: Why sharing is better than silos with Uber’s Insights Platform
December 16, 2019
"Designers are the most insecure function in many companies because their role—to represent people's needs—is both critical and ambiguous."
Tricia WangThe most popular design thinking strategy is BS
January 27, 2022
"We’ll hear multi-disciplinary views on how to build trust with stakeholders."
Ariel KennanTheme 2 Intro
December 9, 2021
"Designers have long thought of themselves as heroes, but we had to unpack that conception."
Frances Yllana Ann Buechner Jess Jones Betsy RamacciaD.E.A.R.R. Diaries (Discipline, Experience, Architecture, Reflection + Revolution)
November 16, 2022
"By automating deliverables analysis, we saved 12 hours per week within one design team alone."
Farid SabitovAutomatization for Large Enterprise Teams
January 8, 2024
"AI users have reduced critical thinking skills within just two years of using AI-assisted tools."
Aras BilgenWho does the math: A designer’s journey in building an AI-based tutoring app
June 10, 2025
"If someone says they don’t want to do this team activity, I say great, you should lead the next one with your idea."
Shipra Kayan Tess DixonHow Tess Dixon Facilitates Team Engagement and Collaboration at Condé Nast Using Miro
October 1, 2021
