ARIA attribute is valid

  • Rule Typeatomic
  • Rule ID: 5f99a7
  • Last modified: Aug 21, 2019
  • Accessibility Requirements Mapping
    • This rule is not required for conformance
  • Input Aspects

Description

This rule checks that each aria- attribute specified is defined in ARIA 1.1.

Applicability

Any attribute that starts with aria-.

Expectation

Each target attribute is defined in WAI ARIA 1.1.

Assumptions

There are currently no assumptions

Accessibility Support

There are no major accessibility support issues known for this rule.

Background

Test Cases

Passed

Passed Example 1

A valid ARIA 1.1 attribute aria-atomic is used on element article.

<article aria-atomic="true">This is a decription of something cool...</article>

Passed Example 2

A valid ARIA 1.1 attribute aria-modal on element div with role dialog

<div role="dialog" aria-modal="true">Contains modal content...</div>

Passed Example 3

A valid ARIA 1.1 attribute aria-live on element div with role alert

<div role="alert" aria-live="assertive">
	Your session will expire in 60 seconds.
</div>

Passed Example 4

Muliple valid ARIA 1.1 attributes aria-* are specified on element input with role spinbutton

<input role="spinbutton" aria-valuemax="100" aria-valuemin="0" aria-valuenow="25" type="number" value="25" />

Failed

Failed Example 1

aria-not-checked is not a defined attribute in ARIA 1.1.

<li role="menuitemcheckbox" aria-not-checked="true">List Item</li>

Failed Example 2

aria-labelled is not a defined attribute in ARIA 1.1.

<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

Element without aria-* attribute.

<canvas> </canvas>

Glossary

Outcome

key: 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 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: Implementers 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.


Changelog

Aug 21, 2019fix: update links to WCAG21 resources (#776)
Aug 21, 2019Editorial changes (#725)
Jul 29, 2019Fix citation of work in progress AAMs (#716)
Jul 19, 2019chore: run prettier (#688)
Jul 1, 2019Map ARIA rules to ARIA instead of WCAG 4.1.2 (#607)
Jun 24, 2019fix: Make "auto" rules consistent with their SC (#587)
May 9, 2019Chore: Adapt site to ACT Rules CR format (#547)
May 7, 2019Template update - ARIA attribute is valid (#495)
Apr 29, 2019chore: rename files and update associations (#489)
Apr 16, 2019chore: add unique id to all rules (#478)
Apr 15, 2019chore: WCAG ACT RULES CG Website Update (#437)
Mar 2, 2019fix: add assumptions to rules (#402)
Oct 30, 2018Rule: SC4-1-2-aria-attr-valid (#231)

Useful Links


Implementations

Tool NameCreated ByReport
AlfaSiteimproveView Report

Acknowledgements