The Coming FAD: Future of Accessibility for Developers
summary
The talk explains the Accessibility Object Model (AOM), a proposed API that lets JavaScript add real accessibility data and events into the browser accessibility tree. It covers AOM support for Shadow DOM and Web Components, making HTML5 Canvas accessible, demos of browser experiments (Chrome, Edge, Safari work in progress), new accessibility properties/events, and a devtools validation workflow; the proposal claims up to ~20 million people could benefit if implemented.
AI-written summary · about
chapters (7)
- 0:00Welcome
- 3:56Who benefits
- 7:50Accessibility in web components
- 13:31Extending events for assistive tech
- 17:24Web components and accessibility trees
- 21:01Validating in Chrome DevTools
- 23:50Future impact and call to action
related talks
22mWeb Components and the AOM
43mBeyond the DOM: what’s in the accessibility tree for you?
27mTime Traveller's Guide to Accessibility Mechanics
01h 04mAccessibility API 101
30mAccessible.JS
15mAccess-what? why and how. A11Y for all
40mAccessibility: What If We Let Users Customize ...
12mHarnessing the Accessibility Tree