Re: CFC - Changes to Target Size for Issue 631

+1 to Kathy's latest revision of this SC:


"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;
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;"

On Thu, Jan 11, 2018 at 8:19 AM, Kathy Wahlbin <
kathy@interactiveaccessibility.com> wrote:

> Here is what I would propose:
>
> 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;
> 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;
>
>
> This is based on the Microsoft research that the MATF looked at.  I am
> travelling so I can't pull up the study paper.
>
> -----Original Message-----
> From: Detlev Fischer (TK) [mailto:detlev.fischer@testkreis.de]
> Sent: Thursday, January 11, 2018 7:55 AM
> To: w3c-wai-gl@w3.org
> Subject: Re: CFC - Changes to Target Size for Issue 631
>
> Hi Kathy,
>
> can you make a quick draft for this?
>
> I guess the problem is that it might be too late for another draft. And we
> still have the issue of lists of links, in dropdown menus and the like - we
> would need to have a number what spacing (or target height) we would
> consider sufficient, and might end up where we were (44x22). Or am I
> missing something?
>
> Detlev
>
> Am 11.01.2018 um 04:30 schrieb Kathy Wahlbin:
> >
> > -1  As mentioned on previous call, changing the SC to single dimension
> > is not meeting the needs of the end user.
> >
> > What if we went back to 44x44 CSS pixels and added an additional
> > exception that the minimum target size does not need to be met if
> > there is sufficient spacing between targets.  That would help users
> > with tremors and other mobility challenges to be more successful in
> > hitting the target area while allowing designers to have smaller
> > target regions.
> >
> > So the designer would have two options – meet the minimum requirements
> > for target size (keeping the current exceptions) or having a smaller
> > target size but making sure that targets have minimum spacing between
> > them.
> >
> > *From:*Andrew Kirkpatrick [mailto:akirkpat@adobe.com]
> > *Sent:* Wednesday, January 10, 2018 1:55 PM
> > *To:* WCAG <w3c-wai-gl@w3.org>
> > *Subject:* CFC - Changes to Target Size for Issue 631
> > *Importance:* High
> >
> > Call For Consensus — ends January 12 at 1:45pm Boston time.
> >
> > The Working Group has discussed a change to the Target Size SC in
> > response to issue 631 (https://github.com/w3c/wcag21/issues/631) and
> > discussion. This was discussed on the call
> > (https://www.w3.org/2018/01/10-ag-minutes.html#item06)
> > <https://www.w3.org/2018/01/10-ag-minutes.html#item06%29>.
> >
> > The specific changes are detailed in this pull request:
> > https://github.com/w3c/wcag21/pull/678 (see implemented at
> > http://rawgit.com/w3c/wcag21/Issue631/guidelines/index.html#target-siz
> > e)
> >
> > 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
> > <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitt
> > er.com%2Fawkawk&data=02%7C01%7C%7C54093524ef264326424008d51cd66c05%7Cf
> > a7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446629619786436&sdata=c5U
> > P0xiniJIppvd6Esu1XA%2FbX1ykpABkhgCCmBp%2Fht8%3D&reserved=0>
> >
>
> --
> ---------------------------------------------------------------
> Detlev Fischer PhD
> Testkreis
> http://testkreis.de
>
> Telefon: +49-40-43 18 75-25
> Mobile: +49-157 57 57 57 45
> Fax: +49-40-43 18 75-45
> E-Mail: detlev.fischer@testkreis.de
>
> Anschrift: Werderstr. 34, 20166 Hamburg
> Amtsgericht Hamburg HRB 58 167
> ---------------------------------------------------------------
>
>
>