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
"Allow people to tell you how trauma extraction feels; don’t assume based on your cultural lens."
Matt Bernius Sarah Fathallah Hera Hussain Jessica Zéroual-KaraTrauma-informed Research: A Panel Discussion
October 7, 2021
"Our principle is that whatever we build must help researchers avoid becoming a silo."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"Good UX is good business."
Product and Design at Bloomberg: A 15-year Evolution
December 6, 2022
"Having conversations with stakeholders before presenting AI-generated recommendations helps validate and refine them."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"The trust gap stems from being repeatedly failed by a system, not innate risk aversion or imposter syndrome."
Mansi GuptaDrawing from Feminist Practice to Make Inclusive Design Operational
September 9, 2022
"We created a UX Club to talk shop, share struggles, and build ideas across teams."
Rob Mitzel Sébastien MaloThe Tale of Two Companies: Building a Successful UX Practice in a Century-Old Enterprise
January 8, 2024
"You should not try to deliver your playbook from the ivory tower of design ops. It just will not be successful."
Gabrielle VerderberDocumentation Your Team Will Actually Use
October 3, 2023
"What are your assumed greatest strengths, and how might they prevent you from moving into new spaces?"
Alana WashingtonTheme 1: Introduction and Provocation
January 8, 2024
"I am swimming in a sea of information, like a little fish, and eating all the stuff."
Sam LadnerHow Research Can Drive Strategic Foresight
March 9, 2022
