From a35b1048b733f056ede1d33bb50fb487966ec28c Mon Sep 17 00:00:00 2001 From: Scott O'Hara Date: Thu, 3 Feb 2022 08:29:40 -0500 Subject: [PATCH 1/7] clarifying name, role, value closes #2142 In an attempt to add clarity that it's not just that a name, role and value are exposed but the **correct** name role and value are exposed, I have simply added the word "accurate" to two sentences. This will help imply that it's not just "information" that needs to be exposed to AT, but "accurate information" about what the control represents. If more modifications are necessary here, please let me know and I can make those changes, or the editors can make changes as they see fit. --- understanding/20/name-role-value.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/understanding/20/name-role-value.html b/understanding/20/name-role-value.html index 70a9fcc114..1cafa7fe70 100644 --- a/understanding/20/name-role-value.html +++ b/understanding/20/name-role-value.html @@ -14,18 +14,18 @@

Intent of Name, Role, Value

The intent of this Success Criterion is to ensure that Assistive Technologies (AT) - can gather information about, activate(or set) and keep up to date on the status of + can gather accurate information about, activate (or set) and keep up to date on the status of user interface controls in the content.

When standard controls from accessible technologies are used, this process is straightforward. If the user interface elements are used according to specification the conditions - of this provision will be met. (See examples of Success Criterion 4.1.2 below) + of this provision will be met. (See examples of Success Criterion 4.1.2 below)

If custom controls are created, however, or interface elements are programmed (in code or script) to have a different role and/or function than usual, then additional - measures need to be taken to ensure that the controls provide important information + measures need to be taken to ensure that the controls provide important and accurate information to assistive technologies and allow themselves to be controlled by assistive technologies.

@@ -35,7 +35,7 @@

Intent of Name, Role, Value

of user interface control state are whether or not a checkbox or radio button has been selected, or whether or not a collapsible tree or list node is expanded or collapsed.

- +

Success Criterion 4.1.2 requires a programmatically determinable name for all user From 3f768059d3be7d6ec40649766ca38f021a5f6298 Mon Sep 17 00:00:00 2001 From: Scott O'Hara Date: Thu, 3 Feb 2022 09:03:55 -0500 Subject: [PATCH 2/7] it's more accurate to be appropriate :) --- understanding/20/name-role-value.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/understanding/20/name-role-value.html b/understanding/20/name-role-value.html index 1cafa7fe70..99af1fe6ae 100644 --- a/understanding/20/name-role-value.html +++ b/understanding/20/name-role-value.html @@ -14,7 +14,7 @@

Intent of Name, Role, Value

The intent of this Success Criterion is to ensure that Assistive Technologies (AT) - can gather accurate information about, activate (or set) and keep up to date on the status of + can gather appropriate information about, activate (or set) and keep up to date on the status of user interface controls in the content.

@@ -25,7 +25,7 @@

Intent of Name, Role, Value

If custom controls are created, however, or interface elements are programmed (in code or script) to have a different role and/or function than usual, then additional - measures need to be taken to ensure that the controls provide important and accurate information + measures need to be taken to ensure that the controls provide important and appropriate information to assistive technologies and allow themselves to be controlled by assistive technologies.

From f21392e706daf0f7cbc8d75a6f900ef897d83a82 Mon Sep 17 00:00:00 2001 From: Scott O'Hara Date: Thu, 3 Feb 2022 09:19:43 -0500 Subject: [PATCH 3/7] add in new paragraph largely pulling in [Alastair's new paragraph suggestion](https://github.com/w3c/wcag/issues/2142#issuecomment-1029016889), but I modified it a bit to try and use language similar to what ARIA and HTML use (e.g., what the control **represents** dictates its intended semantics and thus the important accessibility information that would be appropriate to convey). Also, noticed the use of the word "must" in a note in this informative document. so, changed that to "needs to" to keep the intent. --- understanding/20/name-role-value.html | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/understanding/20/name-role-value.html b/understanding/20/name-role-value.html index 99af1fe6ae..9cde9066db 100644 --- a/understanding/20/name-role-value.html +++ b/understanding/20/name-role-value.html @@ -28,6 +28,13 @@

Intent of Name, Role, Value

measures need to be taken to ensure that the controls provide important and appropriate information to assistive technologies and allow themselves to be controlled by assistive technologies.

+ +

What roles and states are appropriate to convey to assistive technology will be determined + by what the control represents. Specifics about such information are defined by other + specifications, such as WAI-ARIA, or the + appropriate platform standards. Another factor to consider is whether there is sufficient + support in assistive technologies to convey the information as specified. +

A particularly important state of a user interface control is whether or not it has focus. The focus state of a control can be programmatically determined, and notifications @@ -39,8 +46,8 @@

Intent of Name, Role, Value

Success Criterion 4.1.2 requires a programmatically determinable name for all user - interface components. Names may be visible or invisible. Occasionally, the name must - be visible, in which case it is identified as a label. Refer to the definition of + interface components. Names may be visible or invisible. Occasionally, the name needs + to be visible, in which case it is identified as a label. Refer to the definition of name and label in the glossary for more information.

From 4e721b661ec4ac6fc5a9900b139b360dd9e20ba9 Mon Sep 17 00:00:00 2001 From: Scott O'Hara Date: Fri, 22 Dec 2023 17:53:08 -0500 Subject: [PATCH 4/7] Update understanding/20/name-role-value.html Co-authored-by: Patrick H. Lauke --- understanding/20/name-role-value.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/name-role-value.html b/understanding/20/name-role-value.html index c97e8bd36a..0fa63152c9 100644 --- a/understanding/20/name-role-value.html +++ b/understanding/20/name-role-value.html @@ -29,7 +29,7 @@

Intent of Name, Role, Value

to assistive technologies and allow themselves to be controlled by assistive technologies.

-

What roles and states are appropriate to convey to assistive technology will be determined +

What roles and states are appropriate to convey to assistive technology will depend by what the control represents. Specifics about such information are defined by other specifications, such as WAI-ARIA, or the appropriate platform standards. Another factor to consider is whether there is sufficient From 0f7907578b4b7066c57938df0272b185e57d29f7 Mon Sep 17 00:00:00 2001 From: Scott O'Hara Date: Fri, 22 Dec 2023 17:53:21 -0500 Subject: [PATCH 5/7] Update understanding/20/name-role-value.html Co-authored-by: Patrick H. Lauke --- understanding/20/name-role-value.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/name-role-value.html b/understanding/20/name-role-value.html index 0fa63152c9..1facd3e90f 100644 --- a/understanding/20/name-role-value.html +++ b/understanding/20/name-role-value.html @@ -30,7 +30,7 @@

Intent of Name, Role, Value

What roles and states are appropriate to convey to assistive technology will depend - by what the control represents. Specifics about such information are defined by other + on what the control represents. Specifics about such information are defined by other specifications, such as WAI-ARIA, or the appropriate platform standards. Another factor to consider is whether there is sufficient support in assistive technologies to convey the information as specified. From 4e7f11d0fbeedcafd1918f15584e23bb04ede979 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Fri, 19 Jan 2024 08:24:12 -0800 Subject: [PATCH 6/7] Update understanding/20/name-role-value.html --- understanding/20/name-role-value.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/understanding/20/name-role-value.html b/understanding/20/name-role-value.html index 1facd3e90f..00cb003ad5 100644 --- a/understanding/20/name-role-value.html +++ b/understanding/20/name-role-value.html @@ -32,7 +32,7 @@

Intent of Name, Role, Value

What roles and states are appropriate to convey to assistive technology will depend on what the control represents. Specifics about such information are defined by other specifications, such as WAI-ARIA, or the - appropriate platform standards. Another factor to consider is whether there is sufficient + relevant platform standards. Another factor to consider is whether there is sufficient support in assistive technologies to convey the information as specified.

From 137cc93ea0e4e98964bf6df5d9407066313c4838 Mon Sep 17 00:00:00 2001 From: Scott O'Hara Date: Fri, 19 Jan 2024 11:43:53 -0500 Subject: [PATCH 7/7] add link to def of a11y supported --- understanding/20/name-role-value.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/understanding/20/name-role-value.html b/understanding/20/name-role-value.html index 00cb003ad5..afcd45f8af 100644 --- a/understanding/20/name-role-value.html +++ b/understanding/20/name-role-value.html @@ -33,7 +33,8 @@

Intent of Name, Role, Value

on what the control represents. Specifics about such information are defined by other specifications, such as WAI-ARIA, or the relevant platform standards. Another factor to consider is whether there is sufficient - support in assistive technologies to convey the information as specified. + accessibility support + with assistive technologies to convey the information as specified.

A particularly important state of a user interface control is whether or not it has