Scaling Accessibility Through Design Systems

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