From 2317ecf9c2bd3c11af094f62c80350fa2d4b2495 Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Fri, 10 May 2024 22:12:09 +0200 Subject: [PATCH 01/23] Create aria-required-accessible-name-gp8n89.md --- .../aria-required-accessible-name-gp8n89.md | 278 ++++++++++++++++++ 1 file changed, 278 insertions(+) create mode 100644 _rules/aria-required-accessible-name-gp8n89.md diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md new file mode 100644 index 0000000000..d86faa25e6 --- /dev/null +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -0,0 +1,278 @@ +--- +id: gp8n89 +name: ARIA required accessible name +rule_type: atomic +description: | + This rule checks that WAI-ARIA accessible name is available when required. +accessibility_requirements: + aria12:accessible_name_required: + title: ARIA 1.2, Accessible Name Required + forConformance: true + failed: not satisfied + passed: satisfied + inapplicable: satisfied + wcag20:1.3.1: # Info and Relationships (A) + secondary: This success criterion is **less strict** than this rule. Unlike WCAG, which might not mandate accessible names for certain elements like table elements, this rule requires them. Consequently, some of the failed examples satisfy this success criterion. + wcag20:2.4.4: # Link Purpose (In Context) (A) + secondary: This success criterion is **related** to this rule. This is because elements assigned the ARIA role of `link` necessitate an accessible name according to WCAG standards. Some of the examples that both passed and failed overlap with this success criterion. + wcag20:2.4.9: # Link Purpose (Link Only) (AAA) + secondary: This success criterion is **related** to this rule. This is because elements assigned the ARIA role of `link` necessitate an accessible name according to WCAG standards. Some of the examples that both passed and failed overlap with this success criterion. + wcag20:4.1.2: # Name, Role, Value (A) + secondary: This success criterion is **related** to this rule. This is because elements assigned an ARIA role corresponding to a user interface component necessitate an accessible name according to WCAG standards. Some of the examples that both passed and failed overlap with this success criterion. +input_aspects: + - Accessibility Tree + - CSS styling + - DOM Tree + - ARIA +acknowledgments: + authors: + - Giacomo Petri +--- + +## Applicability + +This rule applies to any [HTML or SVG element][] that is [included in the accessibility tree][] and has a [WAI-ARIA 1.2][aria 1.2] [explicit semantic role][] that requires an [accessible name][] either from the [author](https://www.w3.org/TR/wai-aria-1.2/#namefromauthor) or the [content](https://www.w3.org/TR/wai-aria-1.2/#namefromcontent), unless the element [implicit semantic role][] matches its [explicit semantic role][]. + +## Expectation + +Each target element has an [accessible name][] that is not empty (`""`). + +## Assumptions + +There are no assumptions. + +## Accessibility Support + +Elements with [explicit semantic role][] of `heading` and with no [accessible name][] seem to be consistently ignored by assistive technologies. Nonetheless, in the context of this rule, they fail since [WAI-ARIA 1.2][aria 1.2] mandates the presence of an [accessible name][]. + +The [accessible name and description computation][] suggests that if an `aria-labelledby` attribute refers to an existing but empty element, the computation should stop and return an empty name without defaulting to the next steps. Several user agents and assistive technologies chose to use the next step in the computation in this case (ultimately defaulting to the content). + +## Background + +The applicability of this rule is limited to elements that have an [explicit semantic role][] that is not identical to their [implicit semantic role][]. Both [WAI-ARIA 1.2][aria 1.2] and [ARIA in HTML](https://www.w3.org/TR/html-aria/#docconformance) discourage authors from using ARIA when the host language provides a fetaure with equivalent role semantics and values. + +An example of an element that has an [implicit semantic role][] that is identical to its [explicit semantic role][] is a `` element. These elements are not applicable because they have extra requirements and should thus be checked separately. + +Elements subjected to the [Presentational Roles Conflict Resolution][] are not covered by this rule, since their [explicit semantic role][] of `none` or `presentation` do not require an accessible name. However, if the [Presentational Roles Conflict Resolution][] is invoked, although the rule doesn't apply, an accessible name might still be necessary. + +### Bibliography + +- [WAI-ARIA 1.2][aria 1.2] +- [ARIA in HTML](https://www.w3.org/TR/html-aria/#docconformance) +- [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) +- [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) + +## Test Cases + +### Passed + +#### Passed Example 1 + +The `div` element with role `button` has an [accessible name][] provided by its content. + +```html +
Submit +``` + +#### Passed Example 2 + +The `div` element with role `img` has an [accessible name][] provided by the `aria-label` [attribute value][]. + +```html +
+ +
+``` + +#### Passed Example 3 + +The `div` element with role `checkbox` has an [accessible name][] provided thanks to the `aria-labelledby` attribute. + +```html +
+
I agree with terms and conditions
+``` + +#### Passed Example 4 + +The `div` element with role `dialog` has an [accessible name][] provided by the `aria-labelledby` attribute. + +```html +
+

Terms

+

These are our terms.

+
+``` + +#### Passed Example 5 + +The `div` element with role `heading` has an [accessible name][] provided by its content. + +```html +

Terms

+``` + +#### Passed Example 6 + +This `div` element with role `heading` is not [visible][], but is still [included in the accessibility tree][]. It has a non-empty [accessible name][] provided by its content. + +```html +
ACT rules
+``` + +#### Passed Example 7 + +The `div` element with role `link` has an [accessible name][] provided by its content. + +```html +
ACT Rules +``` + +### Failed + +#### Failed Example 1 + +The `div` element with role `button` doesn't have an [accessible name][]. + +```html +
+``` + +#### Failed Example 2 + +The `div` element with role `img` doesn't have an [accessible name][]. + +```html +
+ +
+``` + +#### Failed Example 3 + +The `div` element with role `checkbox` doesn't have an [accessible name][]. + +```html +
+
I agree with terms and conditions
+``` + +#### Failed Example 4 + +The `dialog` role accept an [accessible name][] only from the author and not from its content. Therefore, the `div` element with role `dialog` doesn't have an [accessible name][]. + +```html +
+

Terms

+

These are our terms.

+
+``` + +#### Failed Example 5 + +The `div` element with role `heading` doesn't an [accessible name][] due to the empty `aria-label` [attribute value][]. + +```html +
Terms +``` + +#### Failed Example 6 + +The `div` element with role `heading` has an empty [accessible name][] given by its `aria-labelledby` attribute. + +```html + +

ACT Rules

+``` + +#### Failed Example 7 + +The `div` element with role `button` has an empty [accessible name][] because the `value` attribute does not count in the computation of the [accessible name][]. + +```html +
+``` + +#### Failed Example 8 + +This `div` element with role `button` is not [visible][], but is still [included in the accessibility tree][]. It doesn't have an [accessible name][], therefore failing the rule. + +```html +
+``` + +#### Failed Example 9 + +The `div` element with role `link` has an empty [accessible name][]. + +```html +
+``` + +### Inapplicable + +#### Inapplicable Example 1 + +This `button` element has no [explicit semantic role][]. + +```html + +``` + +#### Inapplicable Example 2 + +This `div` element is not [included in the accessibility tree][], hence its [explicit semantic role][] is not relevant. + +```html +
+``` + +#### Inapplicable Example 3 + +This `table` element has an [explicit semantic role][] of `table`, that is identical to its [implicit semantic role][]. + +```html +
+ + + + + + + + + + + + + + + + +
Table Header 1Table Header 2
Some content 1Some content 2
Some content 3Some content 4
+``` + +#### Inapplicable Example 4 + +This `div` element has an [explicit semantic role][] of `group`, which does not require an [accessible name][]. + +```html +
Some content
+``` + +#### Inapplicable Example 5 + +This `button` element has an [explicit semantic role][] of `none`. Although the [Presentational Roles Conflict Resolution][] requires the author to provide an [accessible name][], the [explicit semantic role][] does not require an [accessible name][] for this rule. + +```html + +``` + +[accessible name]: #accessible-name 'Definition of accessible name' +[attribute value]: #attribute-value 'Definition of attribute value' +[explicit semantic role]: #explicit-role 'Definition of Explicit Role' +[implicit semantic role]: #implicit-role 'Definition of Implicit Role' +[included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of Included in the Accessibility Tree' +[presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' +[wai-aria 1.2]: https://www.w3.org/TR/wai-aria-1.2/ +[html or svg element]: #namespaced-element From 60faf62c20a3494779d2e1d8f7da194d66e78e68 Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Fri, 10 May 2024 22:25:30 +0200 Subject: [PATCH 02/23] Update aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index d86faa25e6..7e087431e0 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -31,7 +31,7 @@ acknowledgments: ## Applicability -This rule applies to any [HTML or SVG element][] that is [included in the accessibility tree][] and has a [WAI-ARIA 1.2][aria 1.2] [explicit semantic role][] that requires an [accessible name][] either from the [author](https://www.w3.org/TR/wai-aria-1.2/#namefromauthor) or the [content](https://www.w3.org/TR/wai-aria-1.2/#namefromcontent), unless the element [implicit semantic role][] matches its [explicit semantic role][]. +This rule applies to any [HTML or SVG element][] that is [included in the accessibility tree][] and has a [WAI-ARIA 1.2][wai-aria 1.2] [explicit semantic role][] that requires an [accessible name][] either from the [author](https://www.w3.org/TR/wai-aria-1.2/#namefromauthor) or the [content](https://www.w3.org/TR/wai-aria-1.2/#namefromcontent), unless the element [implicit semantic role][] matches its [explicit semantic role][]. ## Expectation @@ -43,13 +43,13 @@ There are no assumptions. ## Accessibility Support -Elements with [explicit semantic role][] of `heading` and with no [accessible name][] seem to be consistently ignored by assistive technologies. Nonetheless, in the context of this rule, they fail since [WAI-ARIA 1.2][aria 1.2] mandates the presence of an [accessible name][]. +Elements with [explicit semantic role][] of `heading` and with no [accessible name][] seem to be consistently ignored by assistive technologies. Nonetheless, in the context of this rule, they fail since [WAI-ARIA 1.2][wai-aria 1.2] mandates the presence of an [accessible name][]. The [accessible name and description computation][] suggests that if an `aria-labelledby` attribute refers to an existing but empty element, the computation should stop and return an empty name without defaulting to the next steps. Several user agents and assistive technologies chose to use the next step in the computation in this case (ultimately defaulting to the content). ## Background -The applicability of this rule is limited to elements that have an [explicit semantic role][] that is not identical to their [implicit semantic role][]. Both [WAI-ARIA 1.2][aria 1.2] and [ARIA in HTML](https://www.w3.org/TR/html-aria/#docconformance) discourage authors from using ARIA when the host language provides a fetaure with equivalent role semantics and values. +The applicability of this rule is limited to elements that have an [explicit semantic role][] that is not identical to their [implicit semantic role][]. Both [WAI-ARIA 1.2][wai-aria 1.2] and [ARIA in HTML](https://www.w3.org/TR/html-aria/#docconformance) discourage authors from using ARIA when the host language provides a fetaure with equivalent role semantics and values. An example of an element that has an [implicit semantic role][] that is identical to its [explicit semantic role][] is a `` element. These elements are not applicable because they have extra requirements and should thus be checked separately. @@ -57,7 +57,7 @@ Elements subjected to the [Presentational Roles Conflict Resolution][] are not c ### Bibliography -- [WAI-ARIA 1.2][aria 1.2] +- [WAI-ARIA 1.2][wai-aria 1.2] - [ARIA in HTML](https://www.w3.org/TR/html-aria/#docconformance) - [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) - [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) From 524d73d2853c4a2c2796d900eb9c049e9a3435ba Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Fri, 10 May 2024 22:41:10 +0200 Subject: [PATCH 03/23] Update aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index 7e087431e0..e40a4bc896 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -71,7 +71,7 @@ Elements subjected to the [Presentational Roles Conflict Resolution][] are not c The `div` element with role `button` has an [accessible name][] provided by its content. ```html -
Submit +
Submit
``` #### Passed Example 2 @@ -125,7 +125,7 @@ This `div` element with role `heading` is not [visible][], but is still [include The `div` element with role `link` has an [accessible name][] provided by its content. ```html -
ACT Rules +
ACT Rules
``` ### Failed @@ -173,7 +173,7 @@ The `dialog` role accept an [accessible name][] only from the author and not fro The `div` element with role `heading` doesn't an [accessible name][] due to the empty `aria-label` [attribute value][]. ```html -
Terms +
Terms
``` #### Failed Example 6 @@ -206,7 +206,7 @@ This `div` element with role `button` is not [visible][], but is still [included The `div` element with role `link` has an empty [accessible name][]. ```html -
+
``` ### Inapplicable From 89f24bf95882342f5fb741f92712d799322b708c Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Fri, 10 May 2024 22:53:26 +0200 Subject: [PATCH 04/23] Update aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index e40a4bc896..afac006d8c 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -49,7 +49,7 @@ The [accessible name and description computation][] suggests that if an `aria-la ## Background -The applicability of this rule is limited to elements that have an [explicit semantic role][] that is not identical to their [implicit semantic role][]. Both [WAI-ARIA 1.2][wai-aria 1.2] and [ARIA in HTML](https://www.w3.org/TR/html-aria/#docconformance) discourage authors from using ARIA when the host language provides a fetaure with equivalent role semantics and values. +The applicability of this rule is limited to elements that have an [explicit semantic role][] that is not identical to their [implicit semantic role][]. Both [WAI-ARIA 1.2][wai-aria 1.2] and [ARIA in HTML](https://www.w3.org/TR/html-aria/#docconformance) discourage authors from using ARIA when the host language provides a feature with equivalent role semantics and values. An example of an element that has an [implicit semantic role][] that is identical to its [explicit semantic role][] is a `
` element. These elements are not applicable because they have extra requirements and should thus be checked separately. From 8e99705545be419011615218fb9553f249f5b977 Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Thu, 23 May 2024 14:07:53 +0200 Subject: [PATCH 05/23] Apply suggestions from code review Co-authored-by: Jean-Yves Moyen --- _rules/aria-required-accessible-name-gp8n89.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index afac006d8c..5658aa1520 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -14,11 +14,11 @@ accessibility_requirements: wcag20:1.3.1: # Info and Relationships (A) secondary: This success criterion is **less strict** than this rule. Unlike WCAG, which might not mandate accessible names for certain elements like table elements, this rule requires them. Consequently, some of the failed examples satisfy this success criterion. wcag20:2.4.4: # Link Purpose (In Context) (A) - secondary: This success criterion is **related** to this rule. This is because elements assigned the ARIA role of `link` necessitate an accessible name according to WCAG standards. Some of the examples that both passed and failed overlap with this success criterion. + secondary: This success criterion is **related** to this rule. This is because elements assigned the ARIA role of `link` necessitate an accessible name according to WCAG standards. Some of the examples that either pass or fail overlap with this success criterion. wcag20:2.4.9: # Link Purpose (Link Only) (AAA) - secondary: This success criterion is **related** to this rule. This is because elements assigned the ARIA role of `link` necessitate an accessible name according to WCAG standards. Some of the examples that both passed and failed overlap with this success criterion. + secondary: This success criterion is **related** to this rule. This is because elements assigned the ARIA role of `link` necessitate an accessible name according to WCAG standards. Some of the examples that either pass or fail overlap with this success criterion. wcag20:4.1.2: # Name, Role, Value (A) - secondary: This success criterion is **related** to this rule. This is because elements assigned an ARIA role corresponding to a user interface component necessitate an accessible name according to WCAG standards. Some of the examples that both passed and failed overlap with this success criterion. + secondary: This success criterion is **related** to this rule. This is because elements assigned an ARIA role corresponding to a user interface component necessitate an accessible name according to WCAG standards. Some of the examples that either pass or fail overlap with this success criterion. input_aspects: - Accessibility Tree - CSS styling @@ -159,7 +159,7 @@ The `div` element with role `checkbox` doesn't have an [accessible name][]. #### Failed Example 4 -The `dialog` role accept an [accessible name][] only from the author and not from its content. Therefore, the `div` element with role `dialog` doesn't have an [accessible name][]. +The `dialog` role accepts an [accessible name][] only from the author and not from its content. Therefore, the `div` element with role `dialog` doesn't have an [accessible name][]. ```html
@@ -170,7 +170,7 @@ The `dialog` role accept an [accessible name][] only from the author and not fro #### Failed Example 5 -The `div` element with role `heading` doesn't an [accessible name][] due to the empty `aria-label` [attribute value][]. +The `div` element with role `heading` has an empty [accessible name][] due to the empty `aria-label` [attribute value][]. ```html
Terms
From 6d0c31773f6bdcedfca9390b827aaf0b576b2bf9 Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Thu, 23 May 2024 14:55:23 +0200 Subject: [PATCH 06/23] Update _rules/aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 1 - 1 file changed, 1 deletion(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index 5658aa1520..d151217077 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -23,7 +23,6 @@ input_aspects: - Accessibility Tree - CSS styling - DOM Tree - - ARIA acknowledgments: authors: - Giacomo Petri From 5385c710b519d448eab94839db8b07eb84c42c37 Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Thu, 23 May 2024 15:13:32 +0200 Subject: [PATCH 07/23] Update _rules/aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index d151217077..eff820737f 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -108,7 +108,7 @@ The `div` element with role `dialog` has an [accessible name][] provided by the The `div` element with role `heading` has an [accessible name][] provided by its content. ```html -

Terms

+
Terms
``` #### Passed Example 6 From 520a8169163011ed0d4c493b393152fb3b672c25 Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Thu, 23 May 2024 15:14:15 +0200 Subject: [PATCH 08/23] Update _rules/aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index eff820737f..8ebcf1b8ae 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -181,7 +181,7 @@ The `div` element with role `heading` has an empty [accessible name][] given by ```html -

ACT Rules

+
ACT Rules
``` #### Failed Example 7 From 704bc4d7262b59156e445537f462a14217224508 Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Thu, 23 May 2024 15:17:46 +0200 Subject: [PATCH 09/23] Update aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index 8ebcf1b8ae..03ac51391f 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -259,13 +259,14 @@ This `div` element has an [explicit semantic role][] of `group`, which does not
Some content
``` -#### Inapplicable Example 5 + + [accessible name]: #accessible-name 'Definition of accessible name' [attribute value]: #attribute-value 'Definition of attribute value' From ee45f070b25b3ec18c16c0b912e3433c86e60bc8 Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Thu, 23 May 2024 15:32:03 +0200 Subject: [PATCH 10/23] Update aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index 03ac51391f..1378923901 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -11,6 +11,8 @@ accessibility_requirements: failed: not satisfied passed: satisfied inapplicable: satisfied + wcag20:1.1.1: # Non-text Content (A) + secondary: This success criterion is **related** to this rule. This is because elements assigned the ARIA role of `img` or `image` necessitate an accessible name according to WCAG standards. Some of the examples that either pass or fail overlap with this success criterion. wcag20:1.3.1: # Info and Relationships (A) secondary: This success criterion is **less strict** than this rule. Unlike WCAG, which might not mandate accessible names for certain elements like table elements, this rule requires them. Consequently, some of the failed examples satisfy this success criterion. wcag20:2.4.4: # Link Purpose (In Context) (A) From 5968b5c8815745d5f33b25d79326004eaff62c66 Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Thu, 23 May 2024 15:35:41 +0200 Subject: [PATCH 11/23] Update aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index 1378923901..28fd10518b 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -60,7 +60,10 @@ Elements subjected to the [Presentational Roles Conflict Resolution][] are not c - [WAI-ARIA 1.2][wai-aria 1.2] - [ARIA in HTML](https://www.w3.org/TR/html-aria/#docconformance) +- [Understanding Success Criterion 1.1.1: Non-text Content](https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html) - [Understanding Success Criterion 1.3.1: Info and Relationships](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) +- [Understanding Success Criterion 2.4.4 Link Purpose (In Context)]([https://www.w3.org/WAI/WCAG22/Understanding/name-role-value](https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-context.html)) +- [Understanding Success Criterion 2.4.9 Link Purpose (Link Only)](https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-link-only.html) - [Understanding Success Criterion 4.1.2: Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value) ## Test Cases From 26a9dd0162805713d8613dcae3fc197ca73b4598 Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Thu, 23 May 2024 15:38:20 +0200 Subject: [PATCH 12/23] Update aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index 28fd10518b..bbf8b79930 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -93,8 +93,8 @@ The `div` element with role `img` has an [accessible name][] provided by the `ar The `div` element with role `checkbox` has an [accessible name][] provided thanks to the `aria-labelledby` attribute. ```html -
-
I agree with terms and conditions
+
+
I agree with terms and conditions
``` #### Passed Example 4 @@ -102,8 +102,8 @@ The `div` element with role `checkbox` has an [accessible name][] provided thank The `div` element with role `dialog` has an [accessible name][] provided by the `aria-labelledby` attribute. ```html -
-

Terms

+
+

Terms

These are our terms.

``` @@ -185,8 +185,8 @@ The `div` element with role `heading` has an empty [accessible name][] due to th The `div` element with role `heading` has an empty [accessible name][] given by its `aria-labelledby` attribute. ```html - -
ACT Rules
+ +
ACT Rules
``` #### Failed Example 7 From 929e3fc8abea0eb216a049713cde7bd08c5acda6 Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Thu, 23 May 2024 20:43:56 +0200 Subject: [PATCH 13/23] Update _rules/aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index bbf8b79930..135f1a8c31 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -32,7 +32,7 @@ acknowledgments: ## Applicability -This rule applies to any [HTML or SVG element][] that is [included in the accessibility tree][] and has a [WAI-ARIA 1.2][wai-aria 1.2] [explicit semantic role][] that requires an [accessible name][] either from the [author](https://www.w3.org/TR/wai-aria-1.2/#namefromauthor) or the [content](https://www.w3.org/TR/wai-aria-1.2/#namefromcontent), unless the element [implicit semantic role][] matches its [explicit semantic role][]. +Elements subjected to the [Presentational Roles Conflict Resolution][] are not part of this rule and must be tested separately. ## Expectation From 29103936674adb5afd513a08ac4ff7c4aa31291a Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Thu, 23 May 2024 20:45:40 +0200 Subject: [PATCH 14/23] Update aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index 135f1a8c31..c8bda31371 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -54,7 +54,7 @@ The applicability of this rule is limited to elements that have an [explicit sem An example of an element that has an [implicit semantic role][] that is identical to its [explicit semantic role][] is a `
` element. These elements are not applicable because they have extra requirements and should thus be checked separately. -Elements subjected to the [Presentational Roles Conflict Resolution][] are not covered by this rule, since their [explicit semantic role][] of `none` or `presentation` do not require an accessible name. However, if the [Presentational Roles Conflict Resolution][] is invoked, although the rule doesn't apply, an accessible name might still be necessary. +Elements subjected to the [Presentational Roles Conflict Resolution][] are not part of this rule and must be tested separately. ### Bibliography From a5a4b62cedd65389a10df301a58dc9a59ecc4667 Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Thu, 23 May 2024 20:46:23 +0200 Subject: [PATCH 15/23] Update aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index c8bda31371..e56ce0e0bb 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -32,7 +32,7 @@ acknowledgments: ## Applicability -Elements subjected to the [Presentational Roles Conflict Resolution][] are not part of this rule and must be tested separately. +This rule applies to any [HTML or SVG element][] that is [included in the accessibility tree][] and has a [WAI-ARIA 1.2][wai-aria 1.2] [explicit semantic role][] that requires an [accessible name][] either from the [author](https://www.w3.org/TR/wai-aria-1.2/#namefromauthor) or the [content](https://www.w3.org/TR/wai-aria-1.2/#namefromcontent), unless the element [implicit semantic role][] matches its [explicit semantic role][]. ## Expectation From 08c35965a9bb86bff99863915f28dadedd0922d6 Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Fri, 24 May 2024 11:47:07 +0200 Subject: [PATCH 16/23] Update aria-required-accessible-name-gp8n89.md --- .../aria-required-accessible-name-gp8n89.md | 90 +++++++++---------- 1 file changed, 41 insertions(+), 49 deletions(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index e56ce0e0bb..ab8659430e 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -32,7 +32,7 @@ acknowledgments: ## Applicability -This rule applies to any [HTML or SVG element][] that is [included in the accessibility tree][] and has a [WAI-ARIA 1.2][wai-aria 1.2] [explicit semantic role][] that requires an [accessible name][] either from the [author](https://www.w3.org/TR/wai-aria-1.2/#namefromauthor) or the [content](https://www.w3.org/TR/wai-aria-1.2/#namefromcontent), unless the element [implicit semantic role][] matches its [explicit semantic role][]. +This rule applies to any [HTML or SVG element][] that is [included in the accessibility tree][] and has a [WAI-ARIA 1.2][wai-aria 1.2] [semantic role][] that requires an [accessible name][] either from the [author](https://www.w3.org/TR/wai-aria-1.2/#namefromauthor) or the [content](https://www.w3.org/TR/wai-aria-1.2/#namefromcontent), unless the element has a presentational [explicit semantic role][] leading to a conflict resolved by [Presentational Roles Conflict Resolution][]. ## Expectation @@ -44,15 +44,15 @@ There are no assumptions. ## Accessibility Support -Elements with [explicit semantic role][] of `heading` and with no [accessible name][] seem to be consistently ignored by assistive technologies. Nonetheless, in the context of this rule, they fail since [WAI-ARIA 1.2][wai-aria 1.2] mandates the presence of an [accessible name][]. +Elements with a [semantic role][] of `heading` and with no [accessible name][] seem to be consistently ignored by assistive technologies. Nonetheless, in the context of this rule, they fail since [WAI-ARIA 1.2][wai-aria 1.2] mandates the presence of an [accessible name][]. The [accessible name and description computation][] suggests that if an `aria-labelledby` attribute refers to an existing but empty element, the computation should stop and return an empty name without defaulting to the next steps. Several user agents and assistive technologies chose to use the next step in the computation in this case (ultimately defaulting to the content). ## Background -The applicability of this rule is limited to elements that have an [explicit semantic role][] that is not identical to their [implicit semantic role][]. Both [WAI-ARIA 1.2][wai-aria 1.2] and [ARIA in HTML](https://www.w3.org/TR/html-aria/#docconformance) discourage authors from using ARIA when the host language provides a feature with equivalent role semantics and values. +Although this ARIA rule mandates authors to ensure an [accessible name][] for each [HTML or SVG element][] [included in the accessibility tree][] and possessing a [WAI-ARIA 1.2][wai-aria 1.2] [semantic role][] requiring an [accessible name][], it does not automatically constitute a WCAG accessibility violation. -An example of an element that has an [implicit semantic role][] that is identical to its [explicit semantic role][] is a `
` element. These elements are not applicable because they have extra requirements and should thus be checked separately. +For instance, consider a `search` landmark comprising a `form` element with a search label, search input, and search submit button. According to ARIA specifications, both the `search` role and the `form` role necessitate an [accessible name][]. However, adhering strictly to this rule may lead to repetitive announcements by assistive technologies like screen readers, overwhelming users. Therefore, while this might technically breach ARIA specs, it does not necessarily translate to a violation of WCAG accessibility standards. Elements subjected to the [Presentational Roles Conflict Resolution][] are not part of this rule and must be tested separately. @@ -72,13 +72,21 @@ Elements subjected to the [Presentational Roles Conflict Resolution][] are not p #### Passed Example 1 +This `button` element with an [implicit semantic role] of `button` has an [accessible name][] provided by its content. + +```html + +``` + +#### Passed Example 2 + The `div` element with role `button` has an [accessible name][] provided by its content. ```html
Submit
``` -#### Passed Example 2 +#### Passed Example 3 The `div` element with role `img` has an [accessible name][] provided by the `aria-label` [attribute value][]. @@ -88,7 +96,7 @@ The `div` element with role `img` has an [accessible name][] provided by the `ar ``` -#### Passed Example 3 +#### Passed Example 4 The `div` element with role `checkbox` has an [accessible name][] provided thanks to the `aria-labelledby` attribute. @@ -97,7 +105,7 @@ The `div` element with role `checkbox` has an [accessible name][] provided thank
I agree with terms and conditions
``` -#### Passed Example 4 +#### Passed Example 5 The `div` element with role `dialog` has an [accessible name][] provided by the `aria-labelledby` attribute. @@ -108,7 +116,7 @@ The `div` element with role `dialog` has an [accessible name][] provided by the ``` -#### Passed Example 5 +#### Passed Example 6 The `div` element with role `heading` has an [accessible name][] provided by its content. @@ -116,7 +124,7 @@ The `div` element with role `heading` has an [accessible name][] provided by its
Terms
``` -#### Passed Example 6 +#### Passed Example 7 This `div` element with role `heading` is not [visible][], but is still [included in the accessibility tree][]. It has a non-empty [accessible name][] provided by its content. @@ -124,7 +132,7 @@ This `div` element with role `heading` is not [visible][], but is still [include
ACT rules
``` -#### Passed Example 7 +#### Passed Example 8 The `div` element with role `link` has an [accessible name][] provided by its content. @@ -144,6 +152,14 @@ The `div` element with role `button` doesn't have an [accessible name][]. #### Failed Example 2 +This `button` element with an [implicit semantic role] of `button` doesn't have an [accessible name][]. + +```html + +``` + +#### Failed Example 3 + The `div` element with role `img` doesn't have an [accessible name][]. ```html @@ -152,7 +168,7 @@ The `div` element with role `img` doesn't have an [accessible name][]. ``` -#### Failed Example 3 +#### Failed Example 4 The `div` element with role `checkbox` doesn't have an [accessible name][]. @@ -161,7 +177,7 @@ The `div` element with role `checkbox` doesn't have an [accessible name][].
I agree with terms and conditions
``` -#### Failed Example 4 +#### Failed Example 5 The `dialog` role accepts an [accessible name][] only from the author and not from its content. Therefore, the `div` element with role `dialog` doesn't have an [accessible name][]. @@ -172,7 +188,7 @@ The `dialog` role accepts an [accessible name][] only from the author and not fr ``` -#### Failed Example 5 +#### Failed Example 6 The `div` element with role `heading` has an empty [accessible name][] due to the empty `aria-label` [attribute value][]. @@ -180,7 +196,7 @@ The `div` element with role `heading` has an empty [accessible name][] due to th
Terms
``` -#### Failed Example 6 +#### Failed Example 7 The `div` element with role `heading` has an empty [accessible name][] given by its `aria-labelledby` attribute. @@ -189,7 +205,7 @@ The `div` element with role `heading` has an empty [accessible name][] given by
ACT Rules
``` -#### Failed Example 7 +#### Failed Example 8 The `div` element with role `button` has an empty [accessible name][] because the `value` attribute does not count in the computation of the [accessible name][]. @@ -197,7 +213,7 @@ The `div` element with role `button` has an empty [accessible name][] because th
``` -#### Failed Example 8 +#### Failed Example 9 This `div` element with role `button` is not [visible][], but is still [included in the accessibility tree][]. It doesn't have an [accessible name][], therefore failing the rule. @@ -205,7 +221,7 @@ This `div` element with role `button` is not [visible][], but is still [included
``` -#### Failed Example 9 +#### Failed Example 10 The `div` element with role `link` has an empty [accessible name][]. @@ -217,51 +233,26 @@ The `div` element with role `link` has an empty [accessible name][]. #### Inapplicable Example 1 -This `button` element has no [explicit semantic role][]. +This `div` element is not [included in the accessibility tree][], hence its [semantic role][] is not relevant. ```html - +
``` #### Inapplicable Example 2 -This `div` element is not [included in the accessibility tree][], hence its [explicit semantic role][] is not relevant. +This `div` element has an [semantic role][] of `group`, which does not require an [accessible name][]. ```html -
+
Some content
``` #### Inapplicable Example 3 -This `table` element has an [explicit semantic role][] of `table`, that is identical to its [implicit semantic role][]. - -```html -
- - - - - - - - - - - - - - - - -
Table Header 1Table Header 2
Some content 1Some content 2
Some content 3Some content 4
-``` - -#### Inapplicable Example 4 - -This `div` element has an [explicit semantic role][] of `group`, which does not require an [accessible name][]. +This `button` element has an [explicit semantic role][] of `none`. leading to a conflict resolved by [Presentational Roles Conflict Resolution][], which is not covered by this rule. ```html -
Some content
+ ``` @@ -275,8 +266,9 @@ This `button` element has an [explicit semantic role][] of `none`. Although the [accessible name]: #accessible-name 'Definition of accessible name' [attribute value]: #attribute-value 'Definition of attribute value' -[explicit semantic role]: #explicit-role 'Definition of Explicit Role' +[semantic role]: #semantic-role 'Definition of Semantic Role' [implicit semantic role]: #implicit-role 'Definition of Implicit Role' +[explicit semantic role]: #explicit-role 'Definition of Explicit Role' [included in the accessibility tree]: #included-in-the-accessibility-tree 'Definition of Included in the Accessibility Tree' [presentational roles conflict resolution]: https://www.w3.org/TR/wai-aria-1.2/#conflict_resolution_presentation_none 'Presentational Roles Conflict Resolution' [wai-aria 1.2]: https://www.w3.org/TR/wai-aria-1.2/ From f58441265722b7beaac42ec237b3454c03e02b8d Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Mon, 22 Jul 2024 10:32:02 +0200 Subject: [PATCH 17/23] Update _rules/aria-required-accessible-name-gp8n89.md Co-authored-by: Wilco Fiers --- _rules/aria-required-accessible-name-gp8n89.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index ab8659430e..924d8504fb 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -32,7 +32,9 @@ acknowledgments: ## Applicability -This rule applies to any [HTML or SVG element][] that is [included in the accessibility tree][] and has a [WAI-ARIA 1.2][wai-aria 1.2] [semantic role][] that requires an [accessible name][] either from the [author](https://www.w3.org/TR/wai-aria-1.2/#namefromauthor) or the [content](https://www.w3.org/TR/wai-aria-1.2/#namefromcontent), unless the element has a presentational [explicit semantic role][] leading to a conflict resolved by [Presentational Roles Conflict Resolution][]. +This rule applies to any [HTML or SVG element][] that is [included in the accessibility tree][] and has a [semantic role][] that has the "Accessible Name Required: True" [characteristic][], unless the element has a [explicit][explicit semantic role] presentational role. + +[characteristic]: https://www.w3.org/TR/wai-aria-1.2/#Properties ## Expectation From 3d638276fbcd8091bca40d494eb693697b865a88 Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Mon, 22 Jul 2024 11:23:44 +0200 Subject: [PATCH 18/23] Update _rules/aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index 924d8504fb..ac0096c293 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -14,7 +14,7 @@ accessibility_requirements: wcag20:1.1.1: # Non-text Content (A) secondary: This success criterion is **related** to this rule. This is because elements assigned the ARIA role of `img` or `image` necessitate an accessible name according to WCAG standards. Some of the examples that either pass or fail overlap with this success criterion. wcag20:1.3.1: # Info and Relationships (A) - secondary: This success criterion is **less strict** than this rule. Unlike WCAG, which might not mandate accessible names for certain elements like table elements, this rule requires them. Consequently, some of the failed examples satisfy this success criterion. + secondary: This success criterion is **related** to this rule. Unlike WCAG, which might not mandate accessible names for certain elements like table elements, this rule requires them. On the other hand, there are situations where information is not visually presented and is not required by WCAG, but is still required to have an accessible name according to ARIA requirements. wcag20:2.4.4: # Link Purpose (In Context) (A) secondary: This success criterion is **related** to this rule. This is because elements assigned the ARIA role of `link` necessitate an accessible name according to WCAG standards. Some of the examples that either pass or fail overlap with this success criterion. wcag20:2.4.9: # Link Purpose (Link Only) (AAA) From f6eb37c08280c877e7b244e5e1ed41b46ff7033c Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Mon, 22 Jul 2024 11:39:38 +0200 Subject: [PATCH 19/23] Update _rules/aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index ac0096c293..16500caef3 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -192,10 +192,10 @@ The `dialog` role accepts an [accessible name][] only from the author and not fr #### Failed Example 6 -The `div` element with role `heading` has an empty [accessible name][] due to the empty `aria-label` [attribute value][]. +The `div` element with role `heading` has an empty [accessible name][] due to the `display: none` CSS property set to its content. ```html -
Terms
+
Terms
``` #### Failed Example 7 From 9dc8c7f9dfe466abbee8b7988184765b07adf588 Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Mon, 22 Jul 2024 11:44:19 +0200 Subject: [PATCH 20/23] Update _rules/aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index 16500caef3..0e010981ef 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -54,7 +54,7 @@ The [accessible name and description computation][] suggests that if an `aria-la Although this ARIA rule mandates authors to ensure an [accessible name][] for each [HTML or SVG element][] [included in the accessibility tree][] and possessing a [WAI-ARIA 1.2][wai-aria 1.2] [semantic role][] requiring an [accessible name][], it does not automatically constitute a WCAG accessibility violation. -For instance, consider a `search` landmark comprising a `form` element with a search label, search input, and search submit button. According to ARIA specifications, both the `search` role and the `form` role necessitate an [accessible name][]. However, adhering strictly to this rule may lead to repetitive announcements by assistive technologies like screen readers, overwhelming users. Therefore, while this might technically breach ARIA specs, it does not necessarily translate to a violation of WCAG accessibility standards. +For instance, consider a `search` landmark comprising an element with the `form` role, a search label, a search input, and a search submit button. According to ARIA specifications, the `searchbox` role necessitate an [accessible name][]. However, adhering strictly to this rule may lead to repetitive announcements by assistive technologies like screen readers, overwhelming users. Therefore, while this might technically breach ARIA specs, it does not necessarily translate to a violation of WCAG accessibility standards. Elements subjected to the [Presentational Roles Conflict Resolution][] are not part of this rule and must be tested separately. From 33dcdd70c783f163324c9f1461bf55a2670157bd Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Thu, 1 Aug 2024 18:28:51 +0200 Subject: [PATCH 21/23] Update aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index 0e010981ef..de5efb131a 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -200,11 +200,11 @@ The `div` element with role `heading` has an empty [accessible name][] due to th #### Failed Example 7 -The `div` element with role `heading` has an empty [accessible name][] given by its `aria-labelledby` attribute. +The `button` element has an empty [accessible name][] given by its `aria-labelledby` attribute. ```html -
ACT Rules
+ ``` #### Failed Example 8 From c5e2431e62acc40c6f1f69f968ac56cab5b79585 Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Thu, 1 Aug 2024 18:30:30 +0200 Subject: [PATCH 22/23] Update _rules/aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index de5efb131a..0742427546 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -257,14 +257,6 @@ This `button` element has an [explicit semantic role][] of `none`. leading to a ``` - - [accessible name]: #accessible-name 'Definition of accessible name' [attribute value]: #attribute-value 'Definition of attribute value' From 678fd8409e7f87a5197259c9d685765c4895d9ca Mon Sep 17 00:00:00 2001 From: Giacomo Petri Date: Thu, 1 Aug 2024 18:31:02 +0200 Subject: [PATCH 23/23] Update aria-required-accessible-name-gp8n89.md --- _rules/aria-required-accessible-name-gp8n89.md | 1 - 1 file changed, 1 deletion(-) diff --git a/_rules/aria-required-accessible-name-gp8n89.md b/_rules/aria-required-accessible-name-gp8n89.md index 0742427546..825116090f 100644 --- a/_rules/aria-required-accessible-name-gp8n89.md +++ b/_rules/aria-required-accessible-name-gp8n89.md @@ -257,7 +257,6 @@ This `button` element has an [explicit semantic role][] of `none`. leading to a ``` - [accessible name]: #accessible-name 'Definition of accessible name' [attribute value]: #attribute-value 'Definition of attribute value' [semantic role]: #semantic-role 'Definition of Semantic Role'