Proposed ARIA required context role

Description

This rule checks that an element with an explicit semantic role exists inside its required context.

Applicability

This rule applies to any HTML or SVG element that is included in the accessibility tree and has a WAI-ARIA 1.2 explicit semantic role with a required context role, except if the element has an implicit semantic role that is identical to its explicit semantic role.

Expectation

Each test target is the child in the accessibility tree of an element that has a semantic role that is one of the required context roles of the target element.

Assumptions

The rule assumes that the explicit role of the applicable elements is appropriate for their element. I.e. A heading incorrectly marked up with role="cell" does not fail success criterion 1.3.1 Info and Relationships for not being in the context of a row. Having an inappropriate role is itself an issue under 1.3.1 Info and Relationships, so in either scenario a failure of this rule means this success criterion is not satisfied.

Accessibility Support

• User agents do not all have the same accessibility tree. This can lead to different results for this rule, depending on which accessibility tree is used as input.
• aria-owns has limited support in some user agents.
• There exist some combination of popular browsers and assistive technologies who do not announce correctly relationships based on a mix of implicit and explicit roles.

Background

The applicability of this rule is limited to the WAI-ARIA 1.2 Recommendation roles. The WAI-ARIA Graphics Module does not include any required context roles. The Digital Publishing WAI-ARIA Module (DPUB ARIA) 1.0 only has two roles with required context roles (doc-biblioentry and doc-endnote); both of them have issues with their use of role inheritance, and both of them are deprecated in the Digital Publishing WAI-ARIA Module (DPUB ARIA) 1.1 editor’s draft.

An example of an element that has an implicit semantic role that is identical to its explicit semantic role is a <li role="listitem"> element. These elements are not applicable because they have extra requirements and should thus be checked separately.

Being a child in the accessibility tree is different from being a child in the DOM tree. Some DOM nodes have no corresponding node in the accessibility tree (for example, because they are marked with role="presentation"). A child in the accessibility tree can thus correspond to a descendant in the DOM tree. Additionally, the use of aria-owns attribute can change the tree structure to something which is not a subtree of the DOM tree.

This rule is restricted to direct parent-child relation in the accessibility tree which is more strict than the definition of “owned element” in WAI-ARIA. This rule mimics, on the roles level, the content model of HTML.

Subclass roles of required context roles are not automatically included as possible required context roles. For example, the feed role is not a possible required context role for listitem, even though feed is a subclass role of the list role.

Some user agents try to correct missing required context roles or incorrect content model. This often results, for example, in an isolated list item being presented as part of a one-item list containing only itself. Therefore, most test cases contain several targets to try and circumvent these corrections in order to better demonstrate the issue.

Bibliography

• Understanding Success Criterion 1.3.1: Info and Relationships
• Required Context Role

Accessibility Requirements Mapping

• 1.3.1 Info and Relationships (Level A)

  • Learn more about 1.3.1 Info and Relationships
  • Required for conformance to WCAG 2.0 and later on level A and higher.
  • Outcome mapping:
    • Any failed outcomes: success criterion is not satisfied
    • All passed outcomes: success criterion needs further testing
    • An inapplicable outcome: success criterion needs further testing

Input Aspects

The following aspects are required in using this rule.

• Accessibility tree
• CSS styling
• DOM Tree

Test Cases

Passed

Passed Example 1

Open in a new tab

These elements with an explicit role of listitem are children in the accessibility tree of an element with their required context role, list, expressed as an explicit role.

<div role="list">
	<div role="listitem">List item 1</div>
	<div role="listitem">List item 2</div>
</div>

Passed Example 2

Open in a new tab

These elements with an explicit role of listitem are children in the accessibility tree of an element with their required context role, list, expressed as an implicit role of ul. Note that this test case does not satisfy Success Criterion 4.1.1 Parsing because the ul element does not respect its content model.

<ul>
	<div role="listitem">List item 1</div>
	<div role="listitem">List item 2</div>
</ul>

Passed Example 3

Open in a new tab

These elements with an explicit role of listitem are children in the accessibility tree of an element with their required context role even though they are not its children in DOM. The presentational node is not included in the accessibility tree.

<div role="list">
	<div role="presentation">
		<div role="listitem">List item 1</div>
		<div role="listitem">List item 2</div>
	</div>
</div>

Passed Example 4

Open in a new tab

These elements with an explicit role of listitem are children in the accessibility tree of an element with their required context role even though they are not its DOM descendants. The aria-owns attribute is used to alter the accessibility tree and place the target elements in their required context role.

<div role="list" aria-owns="item1 item2"></div>
<div id="item1" role="listitem">List item 1</div>
<div id="item2" role="listitem">List item 2</div>

Passed Example 5

Open in a new tab

These elements with an explicit role of listitem are children in the accessibility tree of an element with their required context role even though they are not its DOM children. The aria-owns attribute is used to alter the accessibility tree and place the target elements in their required context role.

<div role="list" aria-owns="item1 item2">
	<div role="listitem">
		<div id="item1" role="listitem">List item 1</div>
		<div id="item2" role="listitem">List item 2</div>
	</div>
</div>

Passed Example 6

Open in a new tab

These elements with an explicit role of listitem are children in the accessibility tree of an element with their required context role because the accessibility tree mimics the DOM tree across shadow boundaries.

<div id="host" role="list"></div>

<script>
	const host = document.querySelector('#host')
	const root = host.attachShadow({ mode: 'open' })
	root.innerHTML = '<div role="listitem">List item 1</div> <div role="listitem">List item 2</div>'
</script>

Failed

Failed Example 1

Open in a new tab

This element with an explicit role of listitem is not a child in the accessibility tree of an element with its required context role.

<div role="listitem">List item 1</div>

Failed Example 2

Open in a new tab

These elements with an explicit role of listitem are not children in the accessibility tree of an element with their required context role, but of an element with the tabpanel role.

<div role="list">
	<div role="tabpanel">
		<div role="listitem">List item 1</div>
		<div role="listitem">List item 2</div>
	</div>
</div>

Failed Example 3

Open in a new tab

These elements with an explicit role of listitem are not children in the accessibility tree of an element with their required context role. They are instead children in the accessibility tree of the div with an aria-live attribute; even though this div has no role, it has a global ARIA attribute and is thus included in the accessibility tree.

<div role="list">
	<div aria-live="polite">
		<div role="listitem">List item 1</div>
		<div role="listitem">List item 2</div>
	</div>
</div>

Failed Example 4

Open in a new tab

These elements with an explicit role of listitem are not children in the accessibility tree of an element with their required context role because explicit parent-child relation in the accessibility tree (set by aria-owns) does not cross shadow boundaries.

<div role="list" aria-owns="item1 item2"></div>

<div id="host"></div>

<script>
	const host = document.querySelector('#host')
	const root = host.attachShadow({ mode: 'open' })
	root.innerHTML = '<div id="item1" role="listitem">List item 1</div> <div id="item2" role="listitem">List item 2</div>'
</script>

Inapplicable

Inapplicable Example 1

Open in a new tab

This element with an explicit role of listitem is not included in the accessibility tree.

<div role="listitem" style="display:none;">List item 1</div>

Inapplicable Example 2

Open in a new tab

There is no element with an explicit role.

<ul>
	<li>List item 1</li>
</ul>

Inapplicable Example 3

Open in a new tab

This section element with an explicit role of doc-abstract has a role from the Digital Publishing WAI-ARIA Module (DPUB ARIA) 1.0, not the WAI-ARIA 1.2 Recommendation.

<section role="doc-abstract" aria-label="Abstract">
	<p>Accessibility of web content requires semantic information about widgets, structures, and behaviors …</p>
</section>

Inapplicable Example 4

Open in a new tab

There is no element whose role has required context role because the header role does not have one.

<div role="header" aria-level="1">Hello!</div>
<p>Welcome to my homepage!</p>

Inapplicable Example 5

Open in a new tab

There is no element with an explicit role different from its implicit role. This li element has an explicit role of listitem which is identical to its implicit role.

<ul>
	<li role="listitem">List item 1</li>
</ul>

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

An element is focusable if one or both of the following are true:

• the element is part of sequential focus navigation; or
• the element has a tabindex value that is not null.

Exception: Elements that lose focus during a period of up to 1 second after gaining focus, without the user interacting with the page the element is on, are not considered focusable.

Notes:

• The 1 second time span is an arbitrary limit which is not included in WCAG. Given that scripts can manage the focus state of elements, testing the focusability of an element consistently would be impractical without a time limit.
• The tabindex value of an element is the value of the tabindex attribute parsed using the rules for parsing integers. For the tabindex value to be different from null, it needs to be parsed without errors.

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 are exposed to assistive technologies. This allows users of assistive technology to access the elements in a way that meets 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.

Programmatically hidden elements are removed from the accessibility tree. However, some browsers will leave focusable elements with an aria-hidden attribute set to true in the accessibility tree. Because they are hidden, these elements are considered not included in the accessibility tree. This may cause confusion for users of assistive technologies because they may still be able to interact with these focusable elements using sequential keyboard navigation, even though the element should not be included in the accessibility tree.

Marked as decorative

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

• it has an explicit role of none or presentation; or
• it is an img element with an alt attribute whose value is the empty string (alt=""), and with no explicit role.

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 they are programmatically hidden. This is different from marking the element as decorative and does not convey the same intention. Notably, being programmatically hidden 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.

Namespaced Element

An element with a specific namespaceURI value from HTML namespaces. For example an “SVG element” is any element with the “SVG namespace”, which is http://www.w3.org/2000/svg.

Namespaced elements are not limited to elements described in a specification. They also include custom elements. Elements such as a and title have a different namespace depending on where they are used. For example a title in an HTML page usually has the HTML namespace. When used in an svg element, a title element has the SVG namespace instead.

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:

• Inapplicable: No part of the test subject matches the applicability
• Passed: A test target meets all expectations
• Failed: A test target does not meet all expectations

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.

Programmatically Hidden

An HTML element is programmatically hidden if either it has a computed CSS property visibility whose value is not visible; or at least one of the following is true for any of its inclusive ancestors in the flat tree:

• has a computed CSS property display of none; or
• has an aria-hidden attribute set to true

Note: Contrary to the other conditions, the visibility CSS property may be reverted by descendants.

Note: The HTML standard suggests setting the CSS display property to none for elements with the hidden attribute. While not required by HTML, all modern browsers follow this suggestion. Because of this the hidden attribute is not used in this definition. In browsers that use this suggestion, overriding the CSS display property can reveal elements with the hidden attribute.

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 it is not programmatically hidden, 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.

This definition can be used in expressions such as “semantic button” meaning any element with a semantic role of button.

WAI-ARIA specifications

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

• Accessible Rich Internet Applications (WAI-ARIA) 1.2
• WAI-ARIA Graphics Module 1.0
• Digital Publishing WAI-ARIA Module 1.0

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

Rule Versions

This is the first version of this ACT rule.

Implementations

This section is not part of the official rule. It is populated dynamically and not accounted for in the change history or the last modified date.

Implementation	Type	Consistency	Report
Alfa 0.56.0	Automated tool	Consistent
Axe DevTools Pro 4.37.1	Semi-automated tool	Consistent
Axe-core 4.6.0	Automated tool	Consistent
Equal Access Accessibility Checker 3.1.42-rc.0	Automated tool	Partial
QualWeb 3.0.0	Automated tool	Partial
SortSite 6.45	Automated tool	Partial