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
"Outage caused by technical debt between Boneyard’s VT100 era system and E-Toy’s cloud infrastructure."
Ted NewardTheme 4: Enterprise Organizational Journey
June 4, 2019
"Linear notes are fixed hierarchically and chronologically, making it hard to find patterns across ideas."
Jorge ArangoExploding the Notebook: How to Unlock the Power of Linked Notes (2nd of 3 seminars)
April 19, 2024
"Our insights became pillars of the 2020 product strategy and qualitative research earned a reserved seat at the table."
Katy MogalBut Do Your Insights Scale?
March 12, 2021
"After four years we were able to see in a concrete way what happened, the changes that we have been able to do for the organization."
Benjamin RealMaturity Models: A Core Tool for Creating a DesignOps Strategy
October 1, 2021
"We’re not probing for interesting anecdotes or seating quotes for a slide deck. We’re answering real questions to provide actionable guidance."
Deirdre Hirschtritt Cesar Paredes Marie PerrotResearch is Only as Good as the Relationships You Build
November 17, 2022
"Recruiters have become conditioned to treat demographic criteria as flexible or optional, and I want to say they shouldn't be."
Megan CamposWhat Did I Miss? The Hidden Costs of Deprioritizing Diversity in User Research
March 12, 2021
"The chatbot method is very transactional: user asks, system responds, and that is pretty much it."
Ren PopeBuilding Experiences for Knowledge Systems
June 6, 2023
"AI moves the practitioner into an editorial or supervisory role, which often signals de-skilling."
Sheryl Cababa Ethan Marcotte Milena PribicDay 2 Panel
June 5, 2024
"Gatekeepers expect compliance, whereas servant leaders want to make the vision smarter with the team."
Kevin BethuneReimagining Design: Unlocking Strategic Innovation
June 8, 2022
