Proposed ARIA attribute is defined in WAI-ARIA
Description
This rule checks that each aria- attribute specified is defined in ARIA 1.2.
Applicability
This rule applies to any attribute that starts with aria-.
Expectation
Each target attribute is defined in WAI-ARIA Specifications.
Background
The presence of unknown ARIA attributes is often the result of a typo or other developer error. These attributes are ignored by browsers and other assistive technologies. This often means that a state or property which should exist is missing.
Assumptions
There are no assumptions.
Accessibility Support
There are no accessibility support issues known.
Bibliography
- ARIA in HTML
- WAI ARIA Supported States and Properties
- G108: Using markup features to expose the name and role
- Understanding Success Criterion 1.3.1: Info and Relationships
- Understanding Success Criterion 4.1.2: Name, Role, Value
- Semantics and ARIA
Accessibility Requirements Mapping
Secondary Requirements
This rule is related to the following accessibility requirements, but was not designed to test this requirements directly. These secondary requirements can either be stricter than the rule requires, or may be satisfied in ways not tested by the rule:
- 1.3.1 Info and Relationships (Level A): This success criterion is less strict than this rule. This is because the rule does not ignore irrelevant ARIA properties. Some of the failed examples satisfy this success criterion.
- 4.1.2 Name, Role, Value (Level A): This success criterion is less strict than this rule. This is because the rule does not ignore irrelevant ARIA properties. Some of the failed examples satisfy this success criterion.
Input Aspects
The following aspects are required in using this rule.
Test Cases
Passed
Passed Example 1
This article element has an aria-atomic attribute which is defined in WAI-ARIA Specifications.
<article aria-atomic="true">This is a description of something cool...</article>
Passed Example 2
This div element with a role of dialog has an aria-modal attribute which is defined in WAI-ARIA Specifications.
<div role="dialog" aria-modal="true">Contains modal content...</div>
Passed Example 3
This div element with a role of textbox has multiple aria- attributes which are defined in WAI-ARIA Specifications.
<div
role="textbox"
contenteditable="true"
aria-multiline="true"
aria-label="Enter your hobbies"
aria-required="true"
></div>
Passed Example 4
This input element with a type of number has multiple aria- attributes specified which are all defined in WAI-ARIA Specifications.
<label for="spinbutton">Enter a number between 0 and 100:</label>
<input id="spinbutton" aria-valuemax="100" aria-valuemin="0" aria-valuenow="25" type="number" value="25" />
Failed
Failed Example 1
This div element with a role of checkbox has an aria-not-checked attribute which is not defined in WAI-ARIA Specifications.
<div role="checkbox" aria-not-checked="true">All conditions are met</div>
Failed Example 2
This div element with a role of searchbox has an aria-labelled attribute (instead of aria-labelledby) which is not defined in WAI-ARIA Specifications.
<span id="label">Birthday:</span>
<div contenteditable role="searchbox" aria-labelled="label" aria-placeholder="MM-DD-YYYY">
01-01-2019
</div>
Inapplicable
Inapplicable Example 1
This canvas element does not have an aria- attribute specified.
<canvas> </canvas>
Glossary
Outcome
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 five 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
- cantTell: Whether the rule is applicable, or not all expectations were met could not be fully determined by the tester.
- Untested: The tester has not attempted to evaluate the test subject.
Note: A rule has one passed or failed outcome for every test target. When a tester evaluates a test target it can also be reported as cantTell if the rule cannot be tested in its entirety. For example, when applicability was automated, but the expectations have to be evaluated manually.
When there are no test targets the rule has one inapplicable outcome. If the tester is unable to determine whether there are test targets there will be one cantTell outcome. And when no evaluation has occurred the test target has one untested outcome. This means that each test subject always has one or more outcomes.
Outcomes used in ACT Rules can be expressed using the outcome property of the [EARL10-Schema][].
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
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 (fully automated) 0.80.0 | Automated tool | Consistent |  |
| Alfa (semi-automated) 0.80.0 | Semi-automated tool | Consistent | |
| Axe DevTools Pro 4.37.1 | Semi-automated tool | Consistent | |
| Axe-core 4.8.3 | Automated tool | Consistent | |
| Equal Access Accessibility Checker 3.1.42-rc.0 | Automated tool | Consistent | |
| QualWeb 3.0.0 | Automated tool | Consistent | |
| SortSite 6.45 | Automated tool | Consistent | |
| Total Validator 17.4.0 | Linter | Consistent | |
| Total Validator (+Browser) 17.4.0 | Automated tool | Consistent | |
| ember-template-lint 5.5.1 | Linter | Partial | |