ARIA state or property is permitted

Rule Type:
atomic
Rule ID:
5c01ea
Last Modified:
June 14, 2021
Accessibility Requirements Mapping:
ARIA5: Using WAI-ARIA state and property attributes to expose the state of a user interface component
  • Not required to conformance to any W3C accessibility recommendation.
  • Outcome mapping:
    • Any failed outcomes: technique is not satisfied
    • All passed outcomes: technique needs further testing
    • An inapplicable outcome: technique needs further testing
ARIA 1.1, 7.6 State and Property Attribute Processing
  • Required for conformance to WAI-ARIA 1.1 author requirements
  • Outcome mapping:
    • Any failed outcomes: WAI-ARIA requirement is not satisfied
    • All passed outcomes: WAI-ARIA requirement is satisfied
    • An inapplicable outcome: WAI-ARIA requirement is satisfied
Input Aspects:
Accessibility Tree
CSS styling
DOM Tree

Description

This rule checks that WAI-ARIA states or properties are allowed for the element they are specified on.

Applicability

This rule applies to any WAI-ARIA state or property that is specified on an HTML or SVG element that is included in the accessibility tree.

Expectation

Each test target is either an inherited, supported, or required state or property of the semantic role of the element on which the attribute is specified. If the element has no semantic role, the attribute must be a global state or property.

Note: Assessing the value of the attribute is out of scope for this rule.

Assumptions

There are currently no assumptions

Accessibility Support

Implementation of Presentational Roles Conflict Resolution varies from one browser or assistive technology to another. Depending on this, some elements can have a semantic role of none and their attributes fail this rule with some technologies but users of other technology would not experience any accessibility issue.

Background

Test Cases

Passed

Passed Example 1

The aria-pressed state is supported for the semantic role button, which is the implicit role for button elements.

<button aria-pressed="false">My button</button>

Passed Example 2

The aria-pressed state is supported for the semantic role button, which is the explicit role of this div element.

<div role="button" aria-pressed="false">My button</div>

Passed Example 3

The aria-busy state is a global state that is supported by all elements, even without any semantic role.

<div aria-busy="true">My busy div</div>

Passed Example 4

The aria-label property is a global property and thus inherited for all semantic role.

<div role="button" aria-label="OK">✓</div>

Passed Example 5

The aria-checked state is required for the semantic role checkbox.

<div role="checkbox" aria-checked="false">My checkbox</div>

Passed Example 6

The aria-controls property is required for the semantic role combobox.

<div role="combobox" aria-controls="id1" aria-expanded="false">My combobox</div>

Passed Example 7

The aria-controls property is required for the semantic role combobox. WAI-ARIA states and properties with empty value are still applicable to this rule.

<div role="combobox" aria-expanded="false" aria-controls>My combobox</div>

Passed Example 8

The aria-controls property is required for the semantic role combobox. WAI-ARIA states and properties with empty value (specified as an empty string) are still applicable to this rule.

<div role="combobox" aria-expanded="false" aria-controls="">My combobox</div>

Passed Example 9

The aria-label property is global and thus inherited for all semantic role, including the ones from the WAI-ARIA Graphics Module. This rule is also applicable to SVG elements.

<svg xmlns="http://www.w3.org/2000/svg" role="graphics-object" width="100" height="100" aria-label="yellow circle">
	<circle cx="50" cy="50" r="40" fill="yellow"></circle>
</svg>

Passed Example 10

This button element has an explicit role of none. However, it is focusable (by default). Thus it has a semantic role of button due to Presentational Roles Conflict Resolution. The aria-pressed state is supported for the button role.

<button role="none" aria-pressed="false">ACT rules are cool!</button>

Failed

Failed Example 1

The aria-sort property is neither inherited, supported, nor required for the semantic role button, which is the implicit role for the button element.

<button aria-sort="">Sort by year</button>

Inapplicable

Inapplicable Example 1

This div element has no WAI-ARIA state or property.

<div role="region">A region of content</div>

Inapplicable Example 2

This div element is not included in the accessibility tree, hence its WAI-ARIA state or property is not checked.

<div role="button" aria-sort="" style="display:none;"></div>

Glossary

Explicit Semantic Role

The explicit semantic role of an element is determined by its role attribute (if any).

The role attribute takes a list of tokens. The explicit semantic role is the first valid role in this list. The valid roles are all non-abstract roles from WAI-ARIA Specifications. If the element has no role attribute, or if it has one with no valid role, then this element has no explicit semantic role.

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.

Focusable

Elements that can become the target of keyboard input as described in the HTML specification of focusable and can be focused.

Hidden State

An HTML element’s hidden state is “true” if at least one of the following is true for itself or any of its ancestors in the flat tree:

In any other case, the element’s hidden state is “false”.

Implicit Semantic Role

The implicit semantic role of an element is a pre-defined value given by the host language which depends on the element and its ancestors.

Implicit roles for HTML and SVG, are documented in the HTML accessibility API mappings (working draft) and the SVG accessibility API mappings (working draft).

Included in the accessibility tree

Elements included in the accessibility tree of platform specific accessibility APIs. Elements in the accessibility tree are exposed to assistive technologies, allowing users to interact with the elements in a way that meet the requirements of the individual user.

The general rules for when elements are included in the accessibility tree are defined in the core accessibility API mappings. For native markup languages, such as HTML and SVG, additional rules for when elements are included in the accessibility tree can be found in the HTML accessibility API mappings (working draft) and the SVG accessibility API mappings (working draft).

For more details, see examples of included in the accessibility tree.

Note: Users of assistive technologies might still be able to interact with elements that are not included in the accessibility tree. An example of this is a focusable element with an aria-hidden attribute with a value of true. Such an element could still be interacted using sequential keyboard navigation regardless of the assistive technologies used, even though the element would not be included in the accessibility tree.

Marked as decorative

An element is marked as decorative if one of the following conditions is true:

Elements are marked as decorative as a way to convey the intention of the author that they are pure decoration. It is different from the element actually being pure decoration as authors may make mistakes. It is different from the element being effectively ignored by assistive technologies as rules such as presentational roles conflict resolution may overwrite this intention.

Elements can also be ignored by assistive technologies if their hidden state is true. This is different from marking the element as decorative and does not convey the same intention. Notably, the hidden state of an element may change as users interact with the page (showing and hiding elements) while being marked as decorative should stay the same through all states of the page.

Outcome

An outcome is a conclusion that comes from evaluating an ACT Rule on a test subject or one of its constituent test target. An outcome can be one of the three following types:

Note: A rule has one passed or failed outcome for every test target. When there are no test targets the rule has one inapplicable outcome. This means that each test subject will have one or more outcomes.

Note: Implementations using the EARL10-Schema can express the outcome with the outcome property. In addition to passed, failed and inapplicable, EARL 1.0 also defined an incomplete outcome. While this cannot be the outcome of an ACT Rule when applied in its entirety, it often happens that rules are only partially evaluated. For example, when applicability was automated, but the expectations have to be evaluated manually. Such “interim” results can be expressed with the incomplete outcome.

Semantic Role

The semantic role of an element is determined by the first of these cases that applies:

  1. Conflict If the element is marked as decorative, but the element is included in the accessibility tree; or would be included in the accessibility tree when its hidden state is false, then its semantic role is its implicit role.
  2. Explicit If the element has an explicit role, then its semantic role is its explicit role.
  3. Implicit The semantic role of the element is its implicit role.

WAI-ARIA specifications

The WAI ARIA Specifications group both the WAI ARIA W3C Recommendation and ARIA modules, namely:

Note: depending on the type of content being evaluated, part of the specifications might be irrelevant and should be ignored.

Acknowledgements

This rule was written in the ACT Rules community group, with the support of the EU-funded WAI-Tools Project.

Authors

Changelog

This is the first version of this ACT rule.

Back to Top