Designing Accessibility for Other Developers

on YouTube ↗37m

" summary

Describes building an accessible Dojo widget library using TypeScript, SVG icons, ARIA attributes and WCAG patterns, showing concrete fixes: icon-only buttons use <svg> + aria-labelledby instead of icon fonts, avoid aria-haspopup on tooltips, distinguish ARIA menu vs navigation, and how a text input had to be retrofitted to support combo box ARIA (aria-controls, aria-activedescendant). Advocates an API that reserves control over semantics while still letting components accept arbitrary child content and allow visual theming for layout.

AI-written summary · about

" chapters (13)

1. 0:00Start
2. 1:03Designing Accessibility for Other Developers
3. 2:09Ed Roberts and the Rolling Quads
4. 4:37High Contrast Mode
5. 8:10Simplest Version of a Button without an Icon
6. 9:41Aria Label
7. 10:08Icon Fonts
8. 17:11Visual Styles
9. 23:44Material Design Chip
10. 24:07User Interaction
11. 26:00The Limits of a Framework
12. 30:06Difference between a Navigation Menu and an Aria Menu
13. 31:18Things Not To Control

" related talks

• 24mEscape the Office: Designing Interfaces for Other DevelopersSarah Higley · TSConf 2018
• 28mDeveloper's Guide to Accessibility MechanicsLéonie Watson · You Gotta Love Frontend 2016
• 25mAccessibility in the Age of ComponentsAyesha Mazumdar · React Boston 2019
• 49mHow to create accessible JavaScript widgets with basic HTML componentsJoshua Muheim · HelloA11Y Global Accessibility Awareness Day 2021
• 16mDemystifying accessibility in React appsKateryna Porshnieva · React Conf 2024
• 52mInclusive design challenges with UI widgetsPrem Nawaz Khan · Meta Refresh 2013
• 48mBeyond Default Boundaries: Designing Accessible Non‑Standard ComponentsDiana Bernabei · Accessibility Days 2025
• 41mDemystifying Accessibility in React AppsKateryna Porshnieva · React Paris 2025