Accessibility Tree Inspection
You'll learn how to use DevTools to view and audit the accessibility information browsers expose to assistive technologies.
What Is the Accessibility Tree?
When you build a web page, the browser creates two parallel representations of your content: the DOM tree (Document Object Model) that you're familiar with, and the accessibility tree—a simplified version containing only the information assistive technologies like screen readers need. Think of it as a "translated menu" optimized for users who rely on keyboard navigation or screen reading software.
The accessibility tree strips away purely visual elements and focuses on semantic meaning: roles (is this a button? a heading?), names (what's the accessible label?), states (is it checked? expanded?), and properties (is it required?).
Inspecting Accessibility Information
In the Elements panel, you'll find an Accessibility pane (often alongside Computed, Layout, and Event Listeners tabs). When you select any element, this pane displays:
- Computed Properties: The final accessibility role, name, description, and value the browser exposes
- ARIA Attributes: Which
aria-*attributes are applied and their current values - Accessibility Tree: A hierarchical view showing how this element fits into the tree structure, including its parent and children nodes
This lets you verify whether your semantic HTML and ARIA labels are working as intended—before ever testing with a real screen reader.
Why This Matters
You can visually inspect that a custom dropdown looks like a dropdown, but only the accessibility tree reveals whether assistive technologies understand it as one. Mismatched roles, missing labels, or incorrect ARIA properties become immediately visible.
Key Takeaway: The accessibility tree inspection tools let you audit how browsers translate your markup into information for assistive technologies, ensuring your semantic HTML and ARIA implementation actually work.