Ensures Attributes That Begin with aria- Are Valid ARIA Attributes

Any ARIA attributes starting with aria- must have valid names. Using attributes that are misspelled or do not exist will result in an invalid attribute and failure to comply with this rule.

Why It Matters

When a non-existent or incorrectly spelled ARIA attribute is used, it won’t be able to fulfill the necessary accessibility function. 

This means that assistive technology won’t be able to relay important information to users with disabilities and UI elements won’t work as intended. 

Fixing the Issue

Developers need to check for the presence of unrecognized ARIA attributes, ensure they are spelled correctly, and that they correspond to valid ARIA attribute meanings. 

For example, aria-hidden=”true” would pass, while aria-visible=”rute” would fail.

To ensure you are using recognized attribute names and that they are spelled correctly, refer to the following sections for complete details of each ARIA attribute:

• Widget Attributes
• Live Region Attributes
• Drag-and-Drop Attributes
• Relationship Attributes
• Definitions of States and Properties (all aria-* attributes)
• Role Attribute
• State and Property Attributes
• State and Property Attribute Processing
• WAI-ARIA Attributes Module
• WAI-ARIA Attributes XML Schema Module

Test Cases

For more examples, visit W3C’s GitHub’s ATC Rules library.