Re: CFC - Purpose of Controls SC

-1 
I agree with Michael Cooper’s and Michael Gower’s concerns and feel as uncomfortable as Denis regarding the practical implications of communicating this SC to developers. I fear that asking them to furnish additional metadata conveying purpose for a wide range of controls without any clear immediate benefit (in the absence of coga IT,  brower pliugins etc. that would actually use these data) will be met with skepicism at best. 
 And as a tester, I am not sure how one could comprehensively vet all labels, links, button names in sites under test etc against this list.

Detlev

> On 11 Aug 2017, at 05:21, Andrew Kirkpatrick <akirkpat@adobe.com> wrote:
> 
> Call For Consensus — ends Monday August 14th at 11:30pm Boston time.
> 
> The Working Group has reviewed and approved two new related Success Criteria for inclusion in the Editor’s Draft: Purpose of Controls and Contextual Information, at AA and AAA respectively, with the goal of obtaining additional input external to the working group. This CFC is for the AA version of the SC.
> 
> Call minutes: https://www.w3.org/2017/08/10-ag-minutes.html#item02
> 
> The new SC can be reviewed here, in the context of the full draft: 
> https://rawgit.com/w3c/wcag21/support-personalization_ISSUE-6/guidelines/#purpose-of-controls <https://rawgit.com/w3c/wcag21/support-personalization_ISSUE-6/guidelines/#purpose-of-controls>
> 
> Please note that an editor’s note will be added to this SC to gather feedback on the lengthy list of conventional names before it is published.
> 
> 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 <http://twitter.com/awkawk>
>