Skip to content
BENIBIX Learn

Accessibility Tree

Design♿ AccessibilitySemantic Structure

Also known as A11y Tree, Browser Accessibility Tree

The page as assistive tools see it. Each part has a role, a name and a state.

Think of it like

It is like a list of every room in a house, with its name and its use. A guide reads the list, not the walls.

Example

Jack opens his browser's DevTools on a menu. The tree shows "button, Menu, collapsed", so a screen reader will say just that.

Why it matters

It is what screen readers and voice control really use. Fixing a page for them means fixing what lands here.

Definition

The accessibility tree is a plain copy of a page that the browser builds for assistive tools. It comes from the page's code, the DOM. Each part gets a role, like button or heading. It also gets a name, like Send, and a state, like checked. A screen reader reads this tree, not the page you see. If a button is missing from the tree, it does not exist for that user.
The middle column is the tree. The screen reader reads that, not the page.

Common mistake

Building a button from a plain div. It looks right, but the tree sees no button at all.

Key takeaways

  1. 1
    Role, name, state. Three facts for every part.
  2. 2
    Built from code. Good HTML makes a good tree.
  3. 3
    Look at it. Browser DevTools can show it.