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
"From 1995 to 2012, Windows users had a consistent start button habit path to reach settings; Windows 8 broke that 15-year habit."
Paula BachImproving Legacy Software: How Much Better Does it Have to Be?
March 11, 2022
"There is no need for you to take notes because session notes, videos, and decks will be shared as soon as possible."
Bria AlexanderOpening Remarks
November 17, 2022
"The insight and research community had such a hunger to keep growing and evolving to better amplify the voices of the people we seek to understand."
Jemma AhmedTheme 2 Intro
March 10, 2022
"The average car today has 60 to 100 sensors generating a terrifying amount of data that will increasingly make its way to the cloud."
Hugh DubberlyProblems with Problems: Reconsidering the Frame of Designing as Problem-Solving
June 19, 2019
"Your partners need to trust that you are going to make their goals your goals."
Jess GrecoClaiming your power: Practical tools for amplifying your unique voice
March 13, 2025
"Please read our code of conduct to ensure everyone can be their fullest selves while respecting others."
Bria AlexanderOpening Remarks
October 1, 2021
"If you had a magic wand, what would you do to create more safety for yourself?"
Alana WashingtonTheme 1: Introduction and Provocation
January 8, 2024
"You gotta write that charter to get clarity with your team."
Deanna Washington Bria Alexander Jon Fukuda Saara Kamppari-Miller Farid SabitovConnecting the Ops: Plenary Panel and Closing Circle
September 9, 2022
"Removing my position as a designer means creating space for residents and staff to do the real work and magic."
Ashley Cortez Devika Menon Nidhi Singh Rathore Danita J. Reese Mari NakanoShifting Toward Community-Led Innovation in Local Government
December 8, 2021
