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
"We needed to revise our plan; we couldn’t just keep adding talented folks and hope everything falls into place."
Sarah Kinkade Mariana Ortiz-ReyesDesign Management Models in the Face of Transformation
June 8, 2022
"Assume good intent, start with empathy — we’re all doing hard things we can't do well alone."
Rich MironovHow Can Product Managers and UXers Help Each Other (and Why are Product Folks so Annoying Sometimes)?
December 6, 2022
"We have weekly meetings with implementation teams to design APIs, discuss progress, and address issues to ensure alignment."
PJ Buddhari Nate BaldwinMeet Spectrum, Adobe’s Design System
June 9, 2021
"Those of us who do not understand history are doomed to repeat it."
Sam ProulxTo Boldly Go: The New Frontiers of Accessibility
November 18, 2022
"Right here problems are the questions your PM asks you to fix this quarter to move forward."
Peter LevinSolve a Problem Here, Transform a Strategy There: Research as an Occasion for Expanding Organizational Possibility
March 25, 2024
"During discovery, it’s important to identify which features require exploration versus those that just need validation or small fixes."
Aditi Ruiz Christian Crumlish Farid SabitovA PM State of Mind: Empathy Mapping Your Product Manager, Pt. 1
December 6, 2022
"It’s not about old versus new. It’s about trust and deeply rooted habits."
Maria SkaadenContinuous Design: One eye on the horizon and the other on the next wave
November 8, 2018
"If you skip iterative testing, you risk building features nobody really wants."
Prayag Narula Hannah HudsonEmpowering Designers to do Good Research
March 11, 2022
"Page limits will help equity and focus and level the playing field for small and large firms."
Emily LessardRFPs Without Tears: Writing Inclusive RFPS that Don't Scare Away Talent
December 9, 2021
