Re: CFC - Purpose of Controls SC

+0 
I have concerns that authors anxious to meet this SC will add all sorts of
additional custom tooltips, title attributes etc everywhere, even on elements
that are already conventionally (and accessibly) named. This would decrease
usability.

So I am not really in favour, but I won't stand in the way of getting this into
the editors' draft.

Detlev

--
Detlev Fischer
testkreis c/o feld.wald.wiese
Thedestr. 2, 22767 Hamburg

Mobil +49 (0)157 57 57 57 45
Fax +49 (0)40 439 10 68-5

http://www.testkreis.de
Beratung, Tests und Schulungen für barrierefreie Websites

Andrew Kirkpatrick schrieb am 18.08.2017 00:33:

> Call For Consensus — ends Monday August 21st at 7:00pm Boston time.
> 
> 
> The Working Group has reviewed and approved a new Success Criteria for inclusion in the Editor’s Draft: Purpose of Controls, at AA, with the goal of obtaining additional input external to the working group.
> 
> 
> Call minutes: https://www.w3.org/2017/08/15-ag-minutes.html 
> 
> 
> 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>  
> 
> 
> 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> 
> 
>

Received on Friday, 18 August 2017 15:18:47 UTC