Elements must only use allowed ARIA attributes.

Who might be affected


The first claim in the WAI-ARIA Authoring Practices 1.1 document, immediately after the introduction, says "No ARIA is better than Bad ARIA", and it explains: "Incorrect ARIA misrepresents visual experiences, with potentially devastating effects on their corresponding non-visual experiences". The ARIA spec explicitly defines a list of roles, states, and properties. Some require to be part of a larger structure, others require specific additional attributes, or their state should be programmatically managed. Make sure you use only valid ARIA attributes and that all their additional requirements, if any, are satisfied.

Quick Fixes

Read more about aria roles and their required and allowed attributes on Document conformance requirements for use of ARIA attributes in HTML.

How Users Are Affected

Users that are dependent on screen readers, or other assistive technology that uses text parsing to convey the content to the user, will not be able to correctly perceive and interact with the content.

WCAG Success criteria

This issue might cause elements to fail one or more of the following Success criteria:
4.1.2 Name, Role, Value (A)

Recommended Reading