# axe-core aria-treeitem-name error: treeitem missing accessible name - how to fix it

## TL;DR

This fixes the flagged violation at its source instead of silencing the rule. A treeitem in a tree widget has no accessible name, so keyboard and screen-reader users cannot tell nodes apart. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

## The error, verbatim

```text
axe-core aria-treeitem-name error: treeitem missing accessible name
```

## Fix it step by step

### Step 1

Give each treeitem its name from its visible text content first; that is the cleanest fix.

Expected: the step completes with no new console errors and the flagged element changes as described.

### Step 2

For icon-only tree nodes, add an aria-label that matches the node's purpose.

Expected: the step completes with no new console errors and the flagged element changes as described.

### Step 3

Check child nodes too; the rule flags every nameless treeitem, not just parents.

Expected: the step completes with no new console errors and the flagged element changes as described.

### Step 4

Re-run axe and arrow through the tree with a screen reader to confirm each node announces its name.

Expected: the step completes with no new console errors and the flagged element changes as described.

## When to use this skill

- Your scan report lists this exact rule or failure
- You are clearing automated accessibility failures before release or audit
- A CI accessibility gate is red because of this item

## When NOT to use this skill

- Grouping elements like tree or group do not need names under this rule; only the treeitem leaves and parents do.
- The issue only appears in manual screen-reader testing and no automated rule flags it
- You are doing a full manual WCAG audit; this skill covers one automated check

## Compatibility

axe-core 4.8+ (rule aria-treeitem-name, WCAG 4.1.2).

## Variant phrasings

### axe aria-treeitem-name: tree node has no name

Same underlying issue and the same fix. Searchers phrase it different ways; the remediation does not change.

## Why it happens

A treeitem in a tree widget has no accessible name, so keyboard and screen-reader users cannot tell nodes apart. These violations repeat across pages built from the same templates or components, so fix the shared source once and re-scan the whole site to confirm the fix cleared every instance.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_mgL5YdTMovlreIY4W4zIGA