Assembling a network of accessibility advocacy through UX design
summary
A UX team builds an accessibility program by turning a design system into enforceable requirements, starting with color and type then adding ARIA labels, keyboard support, alt text, ASL and audio description; engineers bake components into code, content teams fix a pervasive language-code bug (wrong ISO 639 variant), and policy allies fund tooling. Automated checks with XMonitor scores move from single-digit baselines to ~30–40% coverage; progress is incremental, measurable, five years in, and driven by small wins and cross‑team networks.
AI-written summary · about
chapters (13)
- 0:00Introduction and background
- 1:43Defining the problem
- 2:56Organizational structures
- 3:56Strategic network building
- 4:31Grassroots advocacy
- 5:30Building an accessibility program
- 15:11Expanding influence
- 17:59Lessons and takeaways
- 22:40Q&A session introduction
- 23:00Systematic design approach
- 24:27Content and accessibility
- 29:24Advanced advocacy and metrics
- 44:41Closing thoughts
related talks
49mScaling Accessibility An Accessibility Design Manager’s Tale
59mAccessibility in UX: A panel discussion
39mAccessibility for Design Systems
44mDesigning with Accessibility in Mind
01h 00mAccessible UX: Design for the rest of us
21mBuilding an Accessibility Culture
53mAccessing Accessible Accessibility
43mPM-led Accessibility: Shepherding project teams into accessible design and developmen...