Beyond the DOM: what’s in the accessibility tree for you?
summary
Explains what actually lives in the accessibility tree and how browsers expose it: Chrome shows per‑element computed name/role since Chrome 65 while Firefox exposes the whole tree in DevTools (around Firefox 61). Lists test tools NVDA VoiceOver TalkBack Orca and Windows Inspect plus the axe extension which auto‑checks a subset of WCAG. Describes the experimental Accessible Object Model phases 1–4 (set properties handle events create virtual nodes inspect tree) and notes privacy concerns and the demoed DevTools pane working end to end.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:33In this presentation: . How do screen readers interact with web browsers? • What information do screen readers need to function?
- 3:18Accessibility APIs
- 6:31Getting data from the browser
- 6:59Virtual model • User can read the web page like a document by using the
- 7:49Demo: simple web page interaction
- 10:41Basic information on elements
- 12:49Actions
- 14:01Inspecting the accessibility tree
- 16:06Common free screen readers
- 17:59With browser devtools
- 18:56Chrome
- 27:17Phases
- 28:21Browser support
- 30:31Phase 1
- 32:36Phase 2
- 34:57Privacy
- 36:07Phase 3
- 38:03Conclusions
- 38:14Questions?
related talks
12mHarnessing the Accessibility Tree
13mDebugging accessibility with Chrome DevTools
24mAccessibility: The Land Time to Interactive Forgot
35mWhat are accessible names and why should you care?
26mThe Coming FAD: Future of Accessibility for Developers
34mAccessibility: the land that time to interactive forgot
52mUsing the aViewer accessibility object inspection tool
13mDebugging accessibility with Chrome DevTools - American Sign Language