Scaling Accessibility Through Design Systems
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
"Agile was built for speed and recovery but often misses depth, purpose, and vision needed for design."
Dave MaloufClosing Keynote: Amplify. Not Optimize.
October 24, 2019
"Dashboards in the DP&M system let design leads visualize all screens, components, templates, and content types in context, identifying inconsistencies or opportunities."
Ellie Krysl Jon FukudaPlanned Right. Managed Right. Designed Right.
June 6, 2023
"Weave in great user stories that exemplify your key points to maximize engagement."
Bruce GillespieLearning from journalism: Balancing impactful communication with compassionate storytelling
March 13, 2025
"Take breaks, use chill zones, and create safe spaces within research and workplace settings."
Matt Bernius Sarah Fathallah Hera Hussain Jessica Zéroual-KaraTrauma-informed Research: A Panel Discussion
October 7, 2021
"Field usability testing showed stakeholders immediately how much value UX can add by catching issues before deployment."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"We have to meet them where they are. Designers need to learn the language of business. That’s a very, very important lesson."
Robert SchwartzWe're Here for the Humans
June 9, 2017
"We want to increase trust and engagement among end users by helping non-technical stakeholders participate in model evaluation."
Joel BranchHumanizing AI: Filling the Gaps with Multi-faceted Research
March 11, 2021
"Bria is the bringer of dad jokes and the glue of the conference."
Louis Rosenfeld Bria AlexanderOpening Remarks
March 27, 2023
"Design annotations provide clear developer guidance and reduce guesswork during handoff."
Gabriela BarnevaOperationalizing Inclusive Design in Design Ops
September 11, 2025
