Designing APIs: How to ensure Accessibility in Design System
summary
Spotify’s design system family (oncore / enor) provides reusable components that merge slot labels into one accessibility label, expose buttons as UIAccessibility custom actions, and supply accessibility user input labels for Voice Control; SwiftUI uses accessibilityElement(children: .combine) to group content automatically. Live demos show VoiceOver, Voice Control and Switch Control on iOS 18, the list row and Box components switch to a narrow layout at large text sizes, and the approach reduces developer work while keeping grouped, efficient screen‑reader navigation.
AI-written summary · about
chapters (13)
- 0:00Introduction and personal story
- 3:57What is a design system
- 7:37Accessibility in design systems
- 12:58Visual grouping and screen readers
- 15:48Balancing developer and user needs
- 18:40Out-of-the-box accessibility solutions
- 21:30Explicit accessibility APIs
- 24:19Custom components and guidelines
- 25:00Live demo setup
- 26:28Testing with VoiceOver
- 29:45Testing with Voice Control
- 32:12Testing with Switch Control
- 36:40Summary and key takeaways
related talks
31mAccessibility for the App You're About to Ship
50mAccessibility-flavored React components...
30mDesign Systems are a Carnival! One Accessible Component, Many Pretty Masks
40mAccessibility-flavored React components make your design system delicious
49mDesigning Accessible Apps
39mAccessibility for Design Systems
40mBuilding Accessible Reusable Components
44mCrafting Great Accessible Experiences