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
"Enough content is when your audience feels confident enough to act."
Margot BloomsteinFostering Trust in Your Brand and Beyond
March 12, 2020
"Improving developer experience starts with understanding users and their technical contexts."
Ed MullenDesigning the Unseen: Enabling Institutions to Build Public Trust
November 16, 2022
"The most successful programs meet stakeholders at their highest point of motivation to participate in research."
Trisha TerharEmpathizing with the Empowered: Non-Researcher Responses to Democratization
March 10, 2022
"The ultimate goal in conflict is to engage with the tension while reducing the friction between humans."
Laura WeissTurn Down the Heat: 3 Ways to Handle Conflict in the Moment
November 20, 2024
"Upskilling customer success managers and others to help with testing meant we could do far more research than I alone could manage."
Dr Chloe SharpUsing Evidence and Collaboration for Setting and Defending Priorities
November 29, 2023
"It’s like sending around the Rolls Royce with the champagne bottle – a white glove, concierge service for recruiting partners."
Tracy McGoldrickIBM User Experience Program—The What, Why and How
October 15, 2021
"Having a repo isn’t the same as having a strategy for socializing and evangelizing the research."
Brigette Metzler Dana ChrisfieldResearch Repositories: A global project by the ResearchOps Community
August 27, 2020
"A society that is designed is better than one that is simply built."
Bob BaxleyTheme 4: Intro
January 8, 2024
"Alternative navigation users pick different tools based on the task and how they feel at that moment, not just one technology."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
