W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2017

Re: CFC: Target Size and Target Size (no exception) SC

From: Gregg C Vanderheiden <greggvan@umd.edu>
Date: Tue, 23 May 2017 21:58:00 -0400
Message-Id: <4C2B33E2-B42A-4CB5-BA14-24BF6C2ABEC5@umd.edu>
Cc: Andrew Kirkpatrick <akirkpat@adobe.com>, "w3c-waI-gl@w3. org" <w3c-wai-gl@w3.org>
To: Glenda Sims <glenda.sims@deque.com>
I still continue to have concerns about this.     40px is a non-defined size.   on ever device it is a different size — yet we are saying it MUST be this big or larger —  when  THIS   is some arbitrary size on different screens.  

Also — if this applies to text links - then it demands that the text be a certain size — when this is not necessary.  

If it does NOT apply to text — then why do these elements need to be large when text does not. 

Finally — why do controls need to be large for everyone when a person who needs them to be larger can zoom to make them larger — as large as they need them to be.   I do not see the need for an SC to do something that is solvable so easily by the few who need this — and can be solved better than 40 x40 px


I don’t think this has been thought out well.   Or at least I have not seen the arguments that would convince me.    

If these issues have been covered and I missed them  (there is such a blizzard of emails from all the different working groups/task forces  that I may have missed it)  then please send to me off list and I will be sure to see it and re-consider. 



g 

Gregg C Vanderheiden
greggvan@umd.edu




> On May 23, 2017, at 6:00 PM, Glenda Sims <glenda.sims@deque.com> wrote:
> 
> +1
> 
> glenda sims    |   team a11y lead   |    deque.com <http://deque.com/>    |    512.963.3773      
> 
> web for everyone. web on everything. -  w3 goals
> 
> On Tue, May 23, 2017 at 11:46 AM, Andrew Kirkpatrick <akirkpat@adobe.com <mailto:akirkpat@adobe.com>> wrote:
> Call For Consensus — ends Thursday May 25rd at 1:00pm Boston time.
> 
> The Working Group has reviewed and approved two new Success Criteria for inclusion in the Editor’s Draft: Target Size and Target Size (no exception), at AA and AAA respectively, with the goal of obtaining additional input external to the working group.
> 
> Survey results: https://www.w3.org/2002/09/wbs/35422/SCreview_May_17/#wbsq4/results <https://www.w3.org/2002/09/wbs/35422/SCreview_May_17/#wbsq4/results> 
> Call minutes: https://www.w3.org/2017/05/23-ag-minutes.html#item04 <https://www.w3.org/2017/05/23-ag-minutes.html#item04> 
> 
> The new SC can be reviewed here, in the context of the full draft: 
> https://rawgit.com/w3c/wcag21/target-size_ISSUE-60/guidelines/#target-size <https://rawgit.com/w3c/wcag21/target-size_ISSUE-60/guidelines/#target-size>
> https://rawgit.com/w3c/wcag21/target-size_ISSUE-60/guidelines/#target-size-no-exception <https://rawgit.com/w3c/wcag21/target-size_ISSUE-60/guidelines/#target-size-all>
> 
> 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, Standards and Accessibility
> Adobe 
> 
> akirkpat@adobe.com <mailto:akirkpat@adobe.com>
> http://twitter.com/awkawk <http://twitter.com/awkawk>
> 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 Wednesday, 24 May 2017 01:58:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:48 UTC