Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Removing 1.3.1 mapping from role attribute rule #1854

Closed
wants to merge 3 commits into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 2 additions & 9 deletions _rules/role-attribute-valid-value-674b10.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,6 @@ rule_type: atomic
description: |
This rule checks that each `role` attribute has a valid value.
accessibility_requirements:
wcag20:1.3.1: # Info and Relationship (A)
forConformance: true
failed: not satisfied
passed: further testing needed
inapplicable: further testing needed
wcag-technique:ARIA4: # Using a WAI-ARIA role to expose the role of a user interface component
forConformance: false
failed: not satisfied
Expand Down Expand Up @@ -44,8 +39,7 @@ Each test target has at least one token which is a valid value corresponding to
## Assumptions

- This rule assumes that the `role` attribute is used to provide an ARIA [semantic role][] to the elements. If it is used for other purposes, this rule shouldn't be used.
- This rule assumes that elements with a `role` attribute have their intended structure and relationship conveyed through some sort of presentation. If it is not the case, it is possible to fail this rule while still satisfying [Success Criterion 1.3.1 Info and Relationship][sc131].
- This rule assumes that the intended role of the element is not its [implicit role][]. If no token is valid, User Agents will default to the [implicit role][] for the element; if that role is the intended one, it is possible to fail this rule but still satisfy [Success Criterion 1.3.1 Info and Relationship][sc131].
- This rule assumes that the intended role of the element is not its [implicit role][]. If no token is valid, User Agents will default to the [implicit role][] for the element; if that role is the intended one, it is possible to fail this rule without creating accessibility issues.

## Accessibility Support

Expand Down Expand Up @@ -78,7 +72,7 @@ This `role` attribute contains one token, and this token is a valid [WAI-ARIA ro

#### Passed Example 2

This `role` attribute contains two tokens, and these tokens are both valid [WAI-ARIA roles][wai-aria role].
This `role` attribute contains two tokens, where the first is a valid [DPUB ARIA Role](https://www.w3.org/TR/dpub-aria-1.0/#role_definitions) and the second is a valid [WAI-ARIA role][wai-aria role].

```html
<style>
Expand Down Expand Up @@ -181,7 +175,6 @@ This `role` attribute is specified on an element which is [programmatically hidd
[implicit role]: #implicit-role 'Definition of Implicit Role'
[programmatically hidden]: #programmatically-hidden 'Definition of Programmatically Hidden'
[role attribute]: https://www.w3.org/TR/role-attribute/ 'Specification of the Role attribute'
[sc131]: https://www.w3.org/TR/WCAG21/#info-and-relationships 'Success Criterion 1.3.1 Info and Relationship'
[semantic role]: #semantic-role 'Definition of Semantic Role'
[space separated tokens]: https://html.spec.whatwg.org/multipage/common-microsyntaxes.html#space-separated-tokens 'Definition of space separated tokens'
[wai-aria role]: https://www.w3.org/TR/wai-aria-1.1/#role_definitions 'List of WAI-ARIA roles'
Expand Down