ACT Rule 5c01ea · proposed
ARIA state or property is permitted
Every role supports a particular set of ARIA attributes. This rule checks that the attributes on an element are ones its role actually supports, rather than ones a different role would have understood.
A tool can decide this one on its own, which is why it turns up in scanner output. The rule is proposed, so it has not yet been implemented in full by a tool and reviewed by a W3C working group, and the wording can still change.
Why passing this rule settles nothing about WCAG
W3C's requirements mapping for this rule names no WCAG success criterion as a conformance requirement. That is the position of 24 of the 87 live rules and this is one of them, which is why a scanner can flag it while an auditor leaves it out of the findings. Both of them are reading the same page correctly.
The requirement is WAI-ARIA's, not WCAG's. Unsupported attributes are dropped, so what looks like extra information is usually no information. W3C lists 1.3.1 and 4.1.2 as related and less strict, and says some of the failing examples satisfy them.
Where W3C files this rule
W3C's index lists this rule under the criteria below, which is how most readers arrive here. The rule's own page names none of them as a conformance requirement, so treat the grouping as a signpost rather than as a verdict.
- 1.3.1 Info and Relationships Level A
- 4.1.2 Name, Role, Value Level A
The ARIA requirement this rule answers to
This rule maps to ARIA 1.2, section 8.6 State and Property Attribute Processing. WAI-ARIA is a separate specification with its own author requirements, so a result here is measured against ARIA rather than against WCAG. A law that names WCAG does not name this.
The normative rule text lives at W3C
What the rule applies to, and exactly what it expects, is published by W3C and can change. We link to it rather than restate it, so nothing here can quietly fall out of date against the source. Read rule 5c01ea at W3C.
ARIA attributes have rules that must be followed
ARIA lets you tell assistive technology what something is. That only works if what you tell it is true and complete. A role often carries obligations. Some need particular states set, some need a specific parent, some need particular children.
A tab has to live in a tablist. A checkbox has to say whether it is checked. Leave those out and you have described something that does not exist. That is worse than describing nothing.
Half-finished ARIA is the pattern. Someone adds role="tablist" to get the semantics and stops there. The tabs never announce their state and the widget becomes unusable by voice.
Fixes that satisfy it
If this rule fails on your site, these are the techniques that put it right.
Other rules W3C files under the same criteria
Each of these asks a different question about the same part of the standard. Passing all of them is still not the same as satisfying the criterion.
- Image button has non-empty accessible name A tool can check this
- Link has non-empty accessible name A tool can check this
- ARIA attribute is defined in WAI-ARIA A tool can check this
- ARIA state or property has valid value A tool can check this
- Element with role attribute has required states and properties A tool can check this
- Form field has non-empty accessible name A tool can check this
All 87 ACT rules are grouped by the criteria they test, and 24 of them decide nothing about WCAG on their own. Run a free scan to see which of these your own pages trip.