Required ARIA attributes must be provided
ARIA widget roles must have appropriate attributes describing the state or properties of the widget.
The Algorithm, in Simple Terms
Checks all elements with the
role attribute to ensure required attributes are defined.
Why this is Important
ARIA widget roles require additional attributes that describe the state of the widget. If a required attribute is not provided, the state of the widget will not be communicated to screen reader users.
Certain roles act as composite user interface widgets. As such, they typically act as containers that manage other, contained widgets. When an object inherits from multiple ancestors and one ancestor indicates that property is supported while another ancestor indicates that it is required, the property is required in the inheriting object. In some cases, default values are sufficient to meet ARIA attribute requirements.
When required state and property attributes for specific roles (and subclass roles) are not present, screen readers may not be able to convey the definition of what the element's role is to the users.
How to Fix the Problem
Add the missing ARIA state or property to the given element.
For more information about which ARIA role, state, and property attributes are allowed by role, see Accessible Rich Internet Applications (WAI-ARIA) 1.1 - Supported States and Properties.
Whether widget roles are mapped to platform accessibility API states, for access by assistive technologies, or are meant to be accessed directly from the DOM, any property or state attributes they require must be specified so that assistive technologies can convey the purpose of the element to users.
These properties and states apply to user interface objects like alert, alertdialog, menu, progressbar, tooltip, and other widgets.
For more information, see W3C WAI-ARIA 1.1 Required States and Properties in Characteristics of Roles.
- HTML 4