aria-* attributes must be valid names with valid values

Rule aria-valid-attr · ARIA · impact serious · Static + live

↩ Back to the rules index · WCAG cross-reference

Why it matters#

A misspelled aria-* attribute (e.g. aria-lable) is silently ignored, and an out-of-range value (e.g. aria-expanded="yes") is treated as undefined — either way the intended state never reaches assistive tech.

How to fix#

Check the attribute name against WAI-ARIA, and give it a value of the correct type (true/false, a token, an integer, etc.).

Example#

<button aria-expanded="yes">Menu</button>

<button aria-expanded="true">Menu</button>

WCAG success criteria#

4.1.2 Name, Role, Value — Level A#

Every UI component must expose a correct name, role, and (where relevant) state/value to assistive technology.

Understanding 4.1.2

Standards#

This rule contributes to the following standards:

WCAG A EN 301 549

References#

• WAI-ARIA — States & Properties