ARIA treeitem nodes should have an accessible name
Accessibility isn’t only about avoiding violations — it’s about ensuring your product can be used confidently by everyone. This guide explains the principle of this rule, shows what goes wrong in real-world code, and provides a verified fix that meets WCAG and the European Accessibility Act (EAA).
Why this matters and how to fix it
Why this matters
Assistive technologies rely on accurate names, roles, states, and relationships. Incorrect ARIA makes controls confusing or silent.
How to fix this issue
Prefer native HTML elements. When using ARIA, use valid roles/attributes, required parent/child relationships, and provide accessible names.
Developer guidance
Codify ARIA usage in your design system with required props and unit tests for valid roles/relationships.
Code examples
Incorrect Implementation
<div role="button" aria-pressed="maybe"></div>Correct Implementation
<div role="button" aria-pressed="true"></div>
Trusted by organizations across Europe working toward WCAG and EAA conformance