Rule: role must be valid

• Elements with role attributes describe the sections of a document (i.e landmarks) or the types of interactive elements (i.e. widgets) to users of assistive technologies, especially screen reader users.

Success Criterion 4.1.2 Name, Role, Value

Other Related Success Criterion:

• Success Criterion 1.3.1 Info and Relationships
• Success Criterion 3.3.2 Labels or Instructions

• Use ARIA landmark roles to describe the sections of a web page.
• Use ARIA widget roles to describe interactive elements on a web page
• Note: DPUB roles are designed to be used for digital books and not the web. If you use DPUB roles on your web pages verify that they add the functionality you intend by testing with the assistive technologies that support DPUB.

• Accessible Rich Internet Applications (WAI-ARIA) 1.2 Specification: Widget Roles
• Accessible Rich Internet Applications (WAI-ARIA) 1.2 Specification: Landmark Roles
• W3C Digital Publishing WAI-ARIA Module 1.1
• W3C WAI-ARIA Graphics Module (Working Draft)
• G108: Using markup features to expose the name and role, allow user-settable properties to be directly set, and provide notification of changes
• ARIA4: Using a WAI-ARIA role to expose the role of a user interface component
• ARIA19: Using ARIA role=alert or Live Regions to Identify Errors
• ARIA Authoring Practices
• MDN Web Docs: ARIA
• Web Fundamentals: Introduction to ARIA