Escape the Office: Designing Interfaces for Other Developers
summary
Design shows concrete changes: TypeScript enforces an interface for a Dojo button so icon-only buttons require alt text, then an enum icon types plus a presentation=true flag prevents duplicate or missing labels; splitting rendering into protected getContent and renderIcon methods with generics lets extensions add ponies without overwriting core logic; an aria bucket provides opt‑in advanced semantics. Examples include SVG title/aria‑label fixes and reduced screen‑reader silence, and the component adjustments demonstrably catch real accessibility failures.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:25Who am I
- 1:13Design challenges
- 1:54Designing for other developers
- 2:26Designing for consumers
- 4:12Early requirements
- 5:20Caveman
- 7:31Email
- 10:50Flexibility Control
- 19:03Extending Properties
- 20:02Accessibility
- 22:31Requirements
related talks
37mDesigning Accessibility for Other Developers
25mAccessibility in the Age of Components
27mMaking Interactions Accessible to All Users
30mDesign Systems are a Carnival! One Accessible Component, Many Pretty Masks
40mAccessibility-flavored React components make your design system delicious
30mScaling Accessibility in the Age of Components
16mDemystifying accessibility in React apps
30mDesign in an Age of inclusivity