Required ARIA attributes must be provided

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 support for one property while another ancestor indicates that the same property is required, the property becomes required on 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.

Fixing 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.

• Properties
  • aria-autocomplete
  • aria-haspopup
  • aria-label
  • aria-level
  • aria-multiline
  • aria-multiselectable
  • aria-orientation
  • aria-readonly
  • aria-required
  • aria-sort
  • aria-valuemax
  • aria-valuemin
  • aria-valuenow
  • aria-valuetext
• States
  • aria-checked
  • aria-disabled
  • aria-expanded
  • aria-hidden
  • aria-invalid
  • aria-pressed
  • aria-selected

For more information, see W3C WAI-ARIA 1.1 Required States and Properties in Characteristics of Roles.