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
"Bringing something to market quickly at scale is time-consuming and expensive—failing early is key to saving resources."
Mike OrenWhy Pharmaceutical's Research Model Should Replace Design Thinking
March 28, 2023
"Pro-social gaming is about designing for positive social interactions that contribute to thriving communities."
Cheryl PlatzEmbrace Your Fun Factor: Game Development Best Practices for Product Design
January 9, 2026
"Over-enforced design system adoption bred resentment and low morale, despite good adoption metrics."
Rachael Greene Alison DavisBuilding a Design Ops Practice that Really Works (Most of the Time)
October 2, 2025
"Research leadership is about adding value to the entire organization, not just your small corner."
Gregg BernsteinOpportunistic Research with Gregg Bernstein
July 11, 2019
"If you can’t measure it, it doesn’t exist is hubris in medicine and science."
Kristen Honey"Let’s Talk About Data and Crisis”: Public Digital Service Delivery = Open Data + Human Centered Design
November 18, 2021
"No one just wakes up and decides to climb a mountain; every step is intentional and planned."
Neema MahdaviOperationalizing DesignOps
November 7, 2018
"Accessibility is not just one person’s responsibility; it must be distributed through the whole product team."
Sam ProulxDesigning For Screen Readers: Understanding the Mental Models and Techniques of Real Users
December 10, 2021
"Our engineering days let engineers pick up smaller ideas from research or bugs and improve the product incrementally."
Smitha Papolu Nova Wehman-Brown Melissa Schmidt Adam MenterTheme 3 Discussion
June 4, 2019
"Say no relentlessly. If you say yes to too much, you’ll fail at what you promised to deliver."
Jose CoronadoFrom Zero to Hero
September 8, 2022
