RE: CFC - Changing Accessible Name in Change of Content

David,

I agree 1.1.1 does use “control” as a synonym for “user interface component”, but I don’t think that’s reason enough to not use the actual defined term for this SC, especially when it’s more often the case that “user interface component” is used throughout WCAG.  Consistency with 4.1.2 Name, Role, Value is very important here in my opinion.  The Understanding doc there even explicitly says they are the same thing.

As for going back to saying “visible label”, this misses the point of linking to the glossary there.  By definition (and consistent with the context where “label” is used in other SC like Headings and Labels), a “label” is always visible because it is “presented to all users”.  The backtrack below also misses the fact that a “label” does not always include text (or an image of text) – it could just be an icon or other graphic.

Steve

From: David MacDonald [mailto:david100@sympatico.ca]
Sent: Friday, September 29, 2017 12:44 PM
To: ALAN SMITH <alands289@gmail.com>
Cc: Andrew Kirkpatrick <akirkpat@adobe.com>; WCAG <w3c-wai-gl@w3.org>
Subject: Re: CFC - Changing Accessible Name in Change of Content

WCAG uses the word control in 1.1.1 which has been removed from the text of the SC based upon it not being consistent with existing WCAG language. I would say ithe use of "control" is consistent with WCAG.


Controls, Input: If non-text content is a ***control*** or accepts user input, then it has a name<https://www.w3.org/TR/WCAG20/#namedef> that describes its purpose. (Refer to Guideline 4.1<https://www.w3.org/TR/WCAG20/#ensure-compat> for additional requirements for ***controls*** and content that accepts user input.)
https://www.w3.org/TR/WCAG20/#text-equiv

​ ​

It is part of the definition of User Interface Component.
https://www.w3.org/TR/WCAG20/#user-interface-componentdef

​
A​
 User interface component is usually used in our standard as a group of code that is perceived as one control.

​I think this issue needs more revision.​ It will be easier to understand and more consistent with its meaning as something like this:

Where an active control has a visible <a>label</a>, the <a>name</a> for the control includes the text string used for its visible label.</p>

Note: A best practice is to place the text string
​ ​
that is visible to sighted users ​
at the start of the
​<a>name</a>​
​
.




Cheers,
David MacDonald



CanAdapt Solutions Inc.

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd<http://twitter.com/davidmacd>

GitHub<https://github.com/DavidMacDonald>

www.Can-Adapt.com<http://www.can-adapt.com/>



  Adapting the web to all users
            Including those with disabilities

If you are not the intended recipient, please review our privacy policy<http://www.davidmacd.com/disclaimer.html>

On Fri, Sep 29, 2017 at 12:18 PM, David MacDonald <david100@sympatico.ca<mailto:david100@sympatico.ca>> wrote:
I would accept it with one amendment

"For active user interface components with labels that include text <add>or images of text</add>, the name includes the text of the label."

The new wording dropped "visible label", and sometimes a visible label is an image, want to ensure this doesn't pass.  <img src="go.jpg"><input aria-label="search" ...>


Cheers,
David MacDonald



CanAdapt Solutions Inc.

Tel:  613.235.4902<tel:(613)%20235-4902>

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd<http://twitter.com/davidmacd>

GitHub<https://github.com/DavidMacDonald>

www.Can-Adapt.com<http://www.can-adapt.com/>



  Adapting the web to all users
            Including those with disabilities

If you are not the intended recipient, please review our privacy policy<http://www.davidmacd.com/disclaimer.html>

On Fri, Sep 29, 2017 at 11:46 AM, ALAN SMITH <alands289@gmail.com<mailto:alands289@gmail.com>> wrote:
+1

Alan Smith

From: Andrew Kirkpatrick<mailto:akirkpat@adobe.com>
Sent: Friday, September 29, 2017 10:13 AM
To: WCAG<mailto:w3c-wai-gl@w3.org>
Subject: CFC - Changing Accessible Name in Change of Content
Importance: High

Call For Consensus — ends Tuesday October 3rd at 10:30am Boston time.

The Working Group has discussed the issue of syncing the concept of “accessible name” in the Change of Content SC with the “name” concept used in WCAG 2.0’s 4.1.2 (Name, Role, Value). https://github.com/w3c/wcag21/issues/371


The specific changes are detailed in this pull request: https://github.com/w3c/wcag21/pull/377/files


Call minutes: https://www.w3.org/2017/09/28-ag-minutes.html#item02


If you have concerns about this proposed consensus position that have not been discussed already and feel that those concerns result in you “not being able to live with” this decision, please let the group know before the CfC deadline.

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

akirkpat@adobe.com<mailto:akirkpat@adobe.com>
http://twitter.com/awkawk