Harnessing the Accessibility Tree
summary
Explains that the accessibility tree is a render-time, filtered DOM exposed to assistive tech and shows how to view it in DevTools (Edge toggle, Firefox Accessibility tab, Chrome tree or bottom view, Safari node inspector). Demonstrates concrete fixes: replace div-with-click with a native button instead of adding tabindex+role+keydown, use ARIA-hidden and aria-expanded properly, and check nodes for role name focusable. Notes Lighthouse only catches ~30% of issues.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:41What is accessibility
- 1:25Accessibility tree explained
- 2:28Dev tools accessibility tree
- 4:15Semantic HTML tags
- 5:19ARIA attributes
- 6:03Bad button example
- 7:49Why use semantic tags
- 8:30Finding the tree in browsers
- 9:14Key takeaways
- 9:57Q&A session
related talks
43mBeyond the DOM: what’s in the accessibility tree for you?
13mDebugging accessibility with Chrome DevTools
32mUnleashing the Power of Developer Tools for Web Accessibility Testing
13mDebugging accessibility with Chrome DevTools - American Sign Language
16mDemystifying accessibility in React apps
01h 04mAccessibility API 101
24mAccessibility: The Land Time to Interactive Forgot
41mWhat If We Talked About Web Accessibility?
