Accessibility & Media Players

on YouTube ↗20m

" summary

Claim: making browser media players accessible is tractable by focusing on concrete controls not content. Steps: enforce solid keyboard navigation (navigation focus control), apply explicit ARIA roles and labels (button vs switch, aria-checked, aria-valuetext), and validate with built‑in browser audits plus VoiceOver. Implementation: a player‑agnostic set of components (Media Chrome) applies live region for loading, time as a progressbar, percent volume and seek times, and demos show screen‑reader interaction working; playback‑rate as a spinbutton is explored but has keyboard edge cases.

AI-written summary · about

" chapters (9)

1. 0:00Intro
2. 1:00Keyboard Interaction
3. 2:50ARIA
4. 6:05Screen Reader
5. 6:30Accessibility Tools
6. 7:40Accessibility Design
7. 9:35Media Chrome
8. 10:50Physical Design
9. 16:10Other Components

" related talks

• 01h 00mAccessibility starts with UXHenny Swan · Inclusive Design 24 2014
• 35mAccelerating accessibility in webHidde de Vries · Git Commit Show 2021
• 33mAccessibility needs to be the future of better technologyEsther Tham · XConf Singapore 2022
• 33mAccessibility Done RightMichelle Sanver · PHP UK Conference 2015
• 41mTechnologic (Human After All): Accessibility remixLéonie Watson · ffconf 2016
• 27mTime Traveller's Guide to Accessibility MechanicsLéonie Watson · DevDays Europe 2019
• 49mAccessibility and PerformanceMarcy Sutton Todd · performance.now() 2025
• 31mHow to Program with Accessibility in MindChandra Carney · RailsConf 2015