RE: CFC - Target Size (2 options)

I cannot live with either option 1 or 2

I’m sorry, but I objected to the prior CFC because of an illogical criterion and this continues down the same path.  I could have lived with 44x44 alone, but the introduction of the 26x26 option mixes things in a completely illogical way.

The first question is simply why would a person with a disability have more success hitting a target of 26x26 with 8 spacing (pass) than hitting a 43x43 target with 7 spacing (fail(?  No matter if it is visually styled to perceive the target boundary or the total, the latter still has much more going for it.  We do not have an answer for this question that I’ve seen.

It seems to me that in the final days we’ve doomed this by mixing goals.  My understanding of the original goal was to increase the user’s ability to hit a target, and that’s all about size of the target.  By introducing a spacing requirement, we’ve muddled in the goal of decreasing the chances of accidentally hitting an adjacent target.  Those are 2 very different goals and need to be 2 different criteria to ever make sense IMHO.

Steve

From: Andrew Kirkpatrick [mailto:akirkpat@adobe.com]
Sent: Wednesday, January 17, 2018 11:29 PM
To: WCAG <w3c-wai-gl@w3.org>
Subject: CFC - Target Size (2 options)
Importance: High

Call For Consensus — ends Friday January 19th at 11:30pm Boston time.

The Working Group has discussed a change to the Target Size SC in response to public comments.

The proposed SC text (Option 1):

The size of the target for pointer inputs is at least 44 by 44 CSS pixels or is at least 26 by 26 CSS pixels with 8 CSS pixels spacing between targets except when:

·       Equivalent - The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels pixels or is at least 28 by 28 CSS pixels with 8 CSS pixels spacing between targets;
·       Inline- The target is in a sentence or block of text;
·       User Agent Control - The size of the target is determined by the user agent and is not modified by the author.
·       Essential - A particular presentation of the target is essential to the information being conveyed
·       Viewport size: The viewport size has a length (height or width) of at least 1000 CSS pixels.

The proposed SC text (Option 2) – this is identical to option 1 but removes the exception for viewport size.

The size of the target for pointer inputs is at least 44 by 44 CSS pixels or is at least 26 by 26 CSS pixels with 8 CSS pixels spacing between targets except when:

·       Equivalent - The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels pixels or is at least 28 by 28 CSS pixels with 8 CSS pixels spacing between targets;
·       Inline- The target is in a sentence or block of text;
·       User Agent Control - The size of the target is determined by the user agent and is not modified by the author.
·       Essential - A particular presentation of the target is essential to the information being conveyed

Please indicate if you can:
Live with option 1 and not option 2
Live with option 2 and not option 1
Live with option 1 or option 2, but prefer option 1
Live with option 1 or option 2, but prefer option 2
Cannot live with either option 1 or 2


Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

akirkpat@adobe.com<mailto:akirkpat@adobe.com>
http://twitter.com/awkawk<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7C%7C54093524ef264326424008d51cd66c05%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446629619786436&sdata=c5UP0xiniJIppvd6Esu1XA%2FbX1ykpABkhgCCmBp%2Fht8%3D&reserved=0>