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
"A society that is designed is better than one that is simply built."
Bob BaxleyTheme 4: Intro
January 8, 2024
"We don’t have to try and do it all at once — build prioritized pillars of knowledge by business focus."
Kate Towsey Jake BurghardtResearchOps AMA with Kate Towsey & Jake Burghardt
October 16, 2025
"Visibility is the most vital thing for UX leaders to be focused on."
John Calhoun Rachel PosmanMeters, Miles, and Madness: New Frameworks to Measure the (Elusive) Value of DesignOps
September 24, 2024
"Designers must learn code fundamentals to use AI effectively, akin to becoming apprentices to the world’s greatest software developers."
Erika FlowersThe Handoff is Dead: Design-Led Engineering with AI Agents
March 4, 2026
"We’re building a community of craft right now, and craft relies on honesty and vulnerability."
Bud CaddellTheme 2 Intro
September 30, 2021
"We are the fix — everything online is made by people, so we can change it together."
Lisa WelchmanCleaning Up Our Mess: Digital Governance for Designers
June 14, 2018
"Meeting stakeholders where they are means using language and concepts they understand, not just tech jargon."
Magdalena ZadaraZero Hour: How to Get Far Quickly When Starting Your Digital Service Unit Late
November 16, 2022
"We send out surveys weekly, but respondents have two weeks to answer, accommodating different time zones and bandwidth."
Wyatt HaymanGlobal Research Panels
August 8, 2020
"You can’t have a hackathon without free food."
Shelby SwitzerMaking Space for Community Knowledge-sharing in a Distributed World
December 10, 2021
