From 4184e81aa44c8879077146f158fd93426516d294 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Thu, 22 Jun 2023 09:47:42 -0400 Subject: [PATCH 1/2] Update-from-survey-heading-non-empty-accessible-name-changes Per review of survey heading non-empty task force conclusions, edited the following: * Pass ex 3, have the acc name be consistent with the text * Set 1.3.1 as a secondary requirement * Removed sentence on accessible name spec not being clear on whitespace * Removed inapp example 1 --- _rules/heading-non-empty-accessible-name-ffd0e9.md | 12 +++--------- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/_rules/heading-non-empty-accessible-name-ffd0e9.md b/_rules/heading-non-empty-accessible-name-ffd0e9.md index 091074332cb..c52579e26fb 100755 --- a/_rules/heading-non-empty-accessible-name-ffd0e9.md +++ b/_rules/heading-non-empty-accessible-name-ffd0e9.md @@ -10,6 +10,8 @@ accessibility_requirements: failed: not satisfied passed: further testing needed inapplicable: further testing needed +secondary_requirements: +wcag20:1.3.1: # Info and Relationships (A) wcag-technique:H42: # Using h1-h6 to identify headings forConformance: false failed: not satisfied @@ -40,7 +42,7 @@ There are no assumptions. ## Accessibility Support -- Some assistive technologies may hide headings with empty [accessible name][] from the users. This depends on the user agent, on how the [accessible name][] was computed (the [accessible name and description computation][] is not clear concerning which characters should be trimmed), and on the assistive technology itself. Hence, there are cases where the outcome of this rule is _failed_, but users of certain assistive technology and browser combinations will not experience an issue. +- Some assistive technologies may hide headings with empty [accessible name][] from the users. This depends on the user agent, on how the [accessible name][] was computed (the [accessible name and description computation][] and on the assistive technology itself. Hence, there are cases where the outcome of this rule is _failed_, but users of certain assistive technology and browser combinations will not experience an issue. - Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some [semantic][semantic role] `heading` elements can fail this rule with some technology but users of other technologies would not experience any accessibility issue because the same elements would have a [semantic role][] of `presentation` and be hidden for these users. @@ -173,14 +175,6 @@ This `h1` element has an [explicit role][] of `none`. However, the [global][] [p #### Inapplicable Example 1 -There is no [semantic][semantic role] `heading` element. - -```html -
-``` - -#### Inapplicable Example 2 - This `h1` element is not [included in the accessibility tree][]. ```html From 7fb7a37b54b81d40a7f5be3e0d87326c5e7b3ea1 Mon Sep 17 00:00:00 2001 From: Chris Loiselle <3275560+ChrisLoiselle@users.noreply.github.com> Date: Thu, 20 Jul 2023 10:15:20 -0400 Subject: [PATCH 2/2] Update _rules/heading-non-empty-accessible-name-ffd0e9.md Co-authored-by: Jean-Yves Moyen --- _rules/heading-non-empty-accessible-name-ffd0e9.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_rules/heading-non-empty-accessible-name-ffd0e9.md b/_rules/heading-non-empty-accessible-name-ffd0e9.md index c52579e26fb..010776085f6 100755 --- a/_rules/heading-non-empty-accessible-name-ffd0e9.md +++ b/_rules/heading-non-empty-accessible-name-ffd0e9.md @@ -42,7 +42,7 @@ There are no assumptions. ## Accessibility Support -- Some assistive technologies may hide headings with empty [accessible name][] from the users. This depends on the user agent, on how the [accessible name][] was computed (the [accessible name and description computation][] and on the assistive technology itself. Hence, there are cases where the outcome of this rule is _failed_, but users of certain assistive technology and browser combinations will not experience an issue. +- Some assistive technologies may hide headings with empty [accessible name][] from the users. This depends on the user agent, on how the [accessible name][] was computed and on the assistive technology itself. Hence, there are cases where the outcome of this rule is _failed_, but users of certain assistive technology and browser combinations will not experience an issue. - Implementation of [Presentational Roles Conflict Resolution][] varies from one browser or assistive technology to another. Depending on this, some [semantic][semantic role] `heading` elements can fail this rule with some technology but users of other technologies would not experience any accessibility issue because the same elements would have a [semantic role][] of `presentation` and be hidden for these users.