From 09edbd3199357f66f51467f85d9c4f4cf0193d31 Mon Sep 17 00:00:00 2001 From: Anne Thyme Date: Fri, 14 Sep 2018 21:40:08 +0200 Subject: [PATCH 1/5] Update accessible-name.md Adding new paragraph on comparing acc names, that has so far been note in these rules: https://auto-wcag.github.io/auto-wcag/rules/SC2-5-3-label-content-name-mismatch.html https://github.com/auto-wcag/auto-wcag/pull/220 https://github.com/auto-wcag/auto-wcag/pull/251 --- pages/algorithms/accessible-name.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/pages/algorithms/accessible-name.md b/pages/algorithms/accessible-name.md index 77c07603cac..20f5e1a2ae6 100644 --- a/pages/algorithms/accessible-name.md +++ b/pages/algorithms/accessible-name.md @@ -7,4 +7,8 @@ The programatically determined name of a user interface element that is exposed The accessible name is calculated using the [accessible name computation](https://www.w3.org/TR/accname). -For native markup languages, such as HTML and SVG, additional information on how to calculate the accessible name can be found in https://www.w3.org/TR/html-aam/#accessible-name-and-description-computation and https://www.w3.org/TR/svg-aam/#mapping_additional. +For native markup languages, such as HTML and SVG, additional information on how to calculate the accessible name can be found in [W3C +HTML Accessibility API Mappings 1.0, Accessible Name and Description Computation](https://www.w3.org/TR/html-aam/#accessible-name-and-description-computation] and [W3C +SVG Accessibility API Mappings, Name and Description](https://www.w3.org/TR/svg-aam/#mapping_additional). + +If deciding whether an accessible name should be considered the same as e.g. another accessible name or a visible name, leading and trailing whitespace and differences in case sensitivity should be ignored. From 20eb483ae70391555ca0b708b385cbf32b53483b Mon Sep 17 00:00:00 2001 From: Anne Thyme Date: Fri, 14 Sep 2018 21:46:54 +0200 Subject: [PATCH 2/5] Update SC2-5-3-label-content-name-mismatch.md Note about how to compare accessible names moved out since it's now in the definition of "accessible name" --- _rules/SC2-5-3-label-content-name-mismatch.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/_rules/SC2-5-3-label-content-name-mismatch.md b/_rules/SC2-5-3-label-content-name-mismatch.md index 3b5b9cfa7f0..2983e11460f 100644 --- a/_rules/SC2-5-3-label-content-name-mismatch.md +++ b/_rules/SC2-5-3-label-content-name-mismatch.md @@ -31,8 +31,6 @@ This rule applies to any element that has: The complete [visible text content](#visible-text-content) of the target element either matches or is contained within its [accessible name](#accessible-name). -**Note**: Leading and trailing whitespace and difference in case sensitivity should be ignored. - ## Assumptions _There are currently no assumptions_ @@ -131,4 +129,4 @@ Non-text content. ```html -``` \ No newline at end of file +``` From b9f879ac40919b39fb0def0ef4db9fbb7b255772 Mon Sep 17 00:00:00 2001 From: Anne Thyme Date: Wed, 3 Oct 2018 15:51:50 +0200 Subject: [PATCH 3/5] Editorial updates --- pages/algorithms/accessible-name.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/pages/algorithms/accessible-name.md b/pages/algorithms/accessible-name.md index 20f5e1a2ae6..1c95afa799a 100644 --- a/pages/algorithms/accessible-name.md +++ b/pages/algorithms/accessible-name.md @@ -5,10 +5,8 @@ key: accessible-name The programatically determined name of a user interface element that is exposed to assistive technologies. -The accessible name is calculated using the [accessible name computation](https://www.w3.org/TR/accname). +The accessible name is calculated using the [accessible name and description computation](https://www.w3.org/TR/accname). -For native markup languages, such as HTML and SVG, additional information on how to calculate the accessible name can be found in [W3C -HTML Accessibility API Mappings 1.0, Accessible Name and Description Computation](https://www.w3.org/TR/html-aam/#accessible-name-and-description-computation] and [W3C -SVG Accessibility API Mappings, Name and Description](https://www.w3.org/TR/svg-aam/#mapping_additional). +For native markup languages, such as HTML and SVG, additional information on how to calculate the accessible name can be found in [HTML Accessibility API Mappings 1.0, Accessible Name and Description Computation](https://www.w3.org/TR/html-aam/#accessible-name-and-description-computation] and [SVG Accessibility API Mappings, Name and Description](https://www.w3.org/TR/svg-aam/#mapping_additional). If deciding whether an accessible name should be considered the same as e.g. another accessible name or a visible name, leading and trailing whitespace and differences in case sensitivity should be ignored. From fb8e997402f1fad114c3764021be3aba2c9204ac Mon Sep 17 00:00:00 2001 From: Anne Thyme Date: Thu, 18 Oct 2018 09:36:55 +0200 Subject: [PATCH 4/5] Removed section on how to compare accessible names --- pages/algorithms/accessible-name.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/pages/algorithms/accessible-name.md b/pages/algorithms/accessible-name.md index 1c95afa799a..d74123e5684 100644 --- a/pages/algorithms/accessible-name.md +++ b/pages/algorithms/accessible-name.md @@ -8,5 +8,3 @@ The programatically determined name of a user interface element that is exposed The accessible name is calculated using the [accessible name and description computation](https://www.w3.org/TR/accname). For native markup languages, such as HTML and SVG, additional information on how to calculate the accessible name can be found in [HTML Accessibility API Mappings 1.0, Accessible Name and Description Computation](https://www.w3.org/TR/html-aam/#accessible-name-and-description-computation] and [SVG Accessibility API Mappings, Name and Description](https://www.w3.org/TR/svg-aam/#mapping_additional). - -If deciding whether an accessible name should be considered the same as e.g. another accessible name or a visible name, leading and trailing whitespace and differences in case sensitivity should be ignored. From bd61dcde93237b16447b3ffe40a29f43440cfe3c Mon Sep 17 00:00:00 2001 From: Anne Thyme Date: Thu, 18 Oct 2018 09:37:50 +0200 Subject: [PATCH 5/5] Put back note on how to compare names --- _rules/SC2-5-3-label-content-name-mismatch.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_rules/SC2-5-3-label-content-name-mismatch.md b/_rules/SC2-5-3-label-content-name-mismatch.md index 2983e11460f..fc0fa679237 100644 --- a/_rules/SC2-5-3-label-content-name-mismatch.md +++ b/_rules/SC2-5-3-label-content-name-mismatch.md @@ -31,6 +31,8 @@ This rule applies to any element that has: The complete [visible text content](#visible-text-content) of the target element either matches or is contained within its [accessible name](#accessible-name). +**Note**: Leading and trailing whitespace and difference in case sensitivity should be ignored. + ## Assumptions _There are currently no assumptions_