Role has required states and properties
Elements that have an explicit role must also specify all required states and properties
This conformance rule relates to:
Note: This rule does not test whether the required states and properties have correct values, only that the attributes are present and non-empty.
Note: The required states and properties with implicit values can be found in the Core Accessibility API Mappings 1.1 Overview of default values for missing required attributes.
Element has required states (no properties required for this role)
Implicit value for roles: ´option´ role has an implicit value (´false´) specified for the required state ´aria-selected´
Implicit value for roles: ´option´ role has an implicit value (´false´) specified for the required state ´aria-selected´, here defined without value
Implicit value for roles: ´option´ role has an implicit value (´false´) specified for the required state ´aria-selected´, here defined with only whitespace instead of a value
Element has required properties, and required state
aria-expanded has an implicit value
Element has required properties, but with incorrect value since no element with with the given id(s) exists in the document
Element does not list required states and properties (´aria-controls´ is required property for ´combobox´)
Required states and properties does not have non-empty value
Element does not have a semantic role
Element does not have an explicit semantic role
Element has an implicit semantic role that is identical to the explicit semantic role
A semantic role is a semantic association that indicates an object’s type. This allows tools to present and support interaction with the object in a manner that is consistent with user expectations about other objects of that type.
The role attribute takes a list of tokens. The semantic role is the first valid role in this list. If none of the tokens are valid, the implicit role will be used instead.
Non-abstract roles defined in the following specifications are considered valid:
Other roles may be added as they become available. Not all roles will be supported in all assistive technologies. Testers are encouraged to adjust which roles are allowed according to the accessibility support base line. For the purposes of executing test cases in all rules, it should be assumed that all roles are supported by assistive technologies so that none of the roles fail due to lack of accessibility support.
Note: For HTML elements the implicit roles are documented in ARIA in HTML.
A string of characters (text) is considered “non-empty” if it contains 1 or more characters that are contained within any of the following unicode categories:
For more details on unicode categories, check out www.fileformat.info/info/unicode/category/
Contributing is open to anyone. We welcome any new issues or pull requests for changes. Auto WCAG Rules has conference calls every 4 weeks. If you are interested in becoming an active contributor or reviewer, we ask that you join the Auto WCAG Rules community group through the W3C Website. This requires setting up a W3C account, may require approval by the organization you work for if they are a W3C member.Learn more about contributing to Auto WCAG Rules Join the Auto WCAG Rules community group now!