Interface Core A1 · Official standard

Tree View

A tree view is a list with levels. Parent rows open or close to show the child items inside them.

Try an example
You might call it treeoutline viewfolder tree

Try an example

Tree View
Product
  • Research
  • Prototype
  • Production

A real example

A file browser opens src to show components. Keyboard focus stays on the active row.

Main parts

  1. 01Current location
  2. 02Destination labels
  3. 03Focus order
  4. 04Responsive behavior

Use it when

Use it for compact navigation or selection when the levels have a clear meaning.

Do not use it when

Avoid it when there are few levels or when levels change often. Separate pages may be easier to understand.

Name used in code

role="tree" / role="treeitem"

Before you ship

Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.

Request you can copy

Outcome: Use Tree View to solve this user need without losing the current context. User context: A file browser opens src to show components. Keyboard focus stays on the active row. Recommended pattern: Tree View. Why it fits: Use it for compact navigation or selection when the levels have a clear meaning. Do not use it when: Avoid it when there are few levels or when levels change often. Separate pages may be easier to understand. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.

Check this request

Review the current use of Tree View. Definition: A tree view is a list with levels. Parent rows open or close to show the child items inside them. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.

A1
How official is this term?

Official standard

A named standard sets the rules described on this page.

The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example.

Scope
ARIA tree semantics
Document status
recommendation
Checked on
2026-07-30

Evidence sources & scope

Authority source + Term reference · W3C · recommendation Accessible Rich Internet Applications (WAI-ARIA) 1.2 — tree role tree role Scope: Web accessibility semantics; direct scope: tree role Role here: Direct term reference Source covers: canonical name, definition, semantics, implementation Authority source · W3C · recommendation Accessible Rich Internet Applications (WAI-ARIA) 1.2 Scope: Web accessibility semantics Role here: Authority within stated scope Source covers: canonical name, definition, semantics, implementation Authority source · W3C WAI · stable ARIA Authoring Practices Guide Scope: Accessible web interaction patterns Role here: Authority within stated scope Source covers: canonical name, definition, interaction, keyboard behavior, accessibility

Copy it yourself

The browser could not copy this. Select the request below and copy it yourself.