Time Traveller's Guide to Accessibility Mechanics
summary
Explains concrete mechanics: builds a toggle button from a span then from a custom element, shows how aria-pressed and tabindex plus keyboard handlers reproduce native behavior, and demonstrates that ARIA leaks from shadow DOM. Describes the Accessibility Object Model roadmap — aria reflection, user-action events, virtual accessibility nodes, computed accessibility tree — notes Chrome behind a flag and warns that AOM makes screen‑reader use detectable (fingerprinting/privacy). Practical demos and implementation caveats determine value.
AI-written summary · about
chapters (15)
- 0:00Start
- 4:35Form accessibility APIs
- 8:01mo: the button element
- 9:579 ARIA
- 10:54aria- attributes
- 11:29span element
- 11:51role attribute
- 12:23tabindex attribute
- 20:38essibility Object Model (AOM)
- 21:32A: ARIA reflection
- 22:15se 1B: Custom Element semantics
- 22:54User action events
- 23:38Virtual accessibility nodes
- 24:15Computed accessibility tree
- 26:30a time traveller
related talks
28mDeveloper's Guide to Accessibility Mechanics
30mAccessible.JS
41mTechnologic (Human After All): Accessibility remix
26mDemystifying Accessibility in React Apps
41mWhat If We Talked About Web Accessibility?
26mAccessibleJS
28mYou're only supposed to blow the bloody doors off!
26mAccessibility Is a Marathon, not a Sprint