diff --git a/__tests__/spelling-ignore.yml b/__tests__/spelling-ignore.yml index e7d0c16864..6bcbc5f441 100644 --- a/__tests__/spelling-ignore.yml +++ b/__tests__/spelling-ignore.yml @@ -90,6 +90,7 @@ - rfc - webauthn - customizable +- selectable # spell checker checks against strict casing & hence some repeated words here - Autocomplete diff --git a/_rules/role-required-states-and-properties-4e8ab6.md b/_rules/role-required-states-and-properties-4e8ab6.md index 5a25dc2b3d..08a7d93d1c 100755 --- a/_rules/role-required-states-and-properties-4e8ab6.md +++ b/_rules/role-required-states-and-properties-4e8ab6.md @@ -12,7 +12,7 @@ accessibility_requirements: passed: further testing needed inapplicable: further testing needed aria12:requiredState: - title: ARIA 1.2, 5.2.2 Required States and Properties + title: ARIA 1.3, 5.2.2 Required States and Properties forConformance: true failed: not satisfied passed: satisfied @@ -41,7 +41,7 @@ For each test target, the [WAI-ARIA required states and properties][] for the ro ## Background -Omitting [WAI-ARIA required states and properties][] is often the result of a developer error. When required properties are missing and a default value is not specified by [WAI-ARIA Specifications][], the behavior is not defined. For [WAI-ARIA 1.2][], the only [explicit semantic roles][explicit semantic role] with a required property with a default value are the `option` and `tabs roles` for the `aria-selected` property. +Omitting [WAI-ARIA required states and properties][] is often the result of a developer error. When required properties are missing and a default value is not specified by [WAI-ARIA Specifications][], the behavior may be not defined. For example, per [WAI-ARIA 1.3][], for the `aria-selected` property, only the `option`, `tab` and `treeitem` roles permit user agents to provide an implicit value when specified conditions are met. For all other roles that support the `aria-selected` property (`gridcell`, `row`, `columnheader`, and `columnheader`), the value for the `aria-selected` property, if not specified by the developer, is `undefined`, indicating the element is not selectable. This rule is testing author built components that specify [explicit semantic roles][explicit semantic role] and not components that keep their [implicit semantic role][]. For components that keep their [implicit semantic role][], all native HTML and SVG elements have native attributes that are mapped to all of the [WAI-ARIA required states and properties](https://www.w3.org/TR/wai-aria/#requiredState). Most of these mappings are defined in the [HTML Accessibility API Mappings, Attribute State and Property Mappings][html aam]. @@ -58,7 +58,7 @@ This rule relies on browsers and assistive technologies to support leaving out [ ### Other Resources - [ARIA5: Using WAI-ARIA state and property attributes to expose the state of a user interface component](https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA5) -- [WAI-ARIA required states and properties](https://www.w3.org/TR/wai-aria-1.2/#requiredState) +- [WAI-ARIA required states and properties](https://www.w3.org/TR/wai-aria-1.3/#requiredState) - [RFC 3986](https://www.ietf.org/rfc/rfc3986.txt) ## Examples @@ -86,7 +86,7 @@ This `checkbox` has the required `aria-checked` property. #### Passed Example 3 -This `scrollbar` has the required properties `aria-controls` and `aria-valuenow`. `aria-valuemin` has a default value of 0 and `aria-valuemax` of 100. +This `scrollbar` has the required property `aria-valuenow`. The optional `aria-controls` refers to the element with "content" as ID. Also, `aria-valuemin` has a default value of 0 and `aria-valuemax` of 100. ```html
@@ -95,7 +95,7 @@ This `scrollbar` has the required properties `aria-controls` and `aria-valuenow` #### Passed Example 4 -These `option` nodes do not need the required `aria-selected` property because it has a default value of `false`. +These `option` nodes do not need the `aria-selected` property because it has a default value of `false`. ```html