Re: CFC - Changes to Target Size for Issue 631

Can anyone share a pointer to the Microsoft research that Kathy references?   My initial searching this morning hasn't revealed it.

The spacing requirement is important, and I'd like to see empirical evidence to back the 8 CSS pixel minimum.


On 1/11/18, 8:20 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag21%2Fissues%2F631&data=02%7C01%7Cmhakkinen%40ets.org%7Cc0f28b5dd5f54d77c27508d558f61620%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C1%7C636512736323906594&sdata=aBPRUnntGbWYLhKWSCYiksCoIN%2F0%2FCdEsikHcjEscYY%3D&reserved=0) and
    > discussion. This was discussed on the call
    > (https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2018%2F01%2F10-ag-minutes.html%23item06&data=02%7C01%7Cmhakkinen%40ets.org%7Cc0f28b5dd5f54d77c27508d558f61620%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C1%7C636512736323906594&sdata=Sn%2FFrIst7JTzYQmr3fxfCP55BNfMG9gLNzMMV3Nlg3A%3D&reserved=0)
    > <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2018%2F01%2F10-ag-minutes.html%23item06%2529&data=02%7C01%7Cmhakkinen%40ets.org%7Cc0f28b5dd5f54d77c27508d558f61620%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C1%7C636512736323906594&sdata=IIL3%2Ba2Dq%2F93u6egGzJNUUgp6tEK2u%2B8ehsAiCYU6VA%3D&reserved=0>.
    >
    > The specific changes are detailed in this pull request:
    > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag21%2Fpull%2F678&data=02%7C01%7Cmhakkinen%40ets.org%7Cc0f28b5dd5f54d77c27508d558f61620%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C1%7C636512736323906594&sdata=K8Tj0UWsSCqrJOGqPHvTzRXSTWW8394AeWt0B7CRV%2FQ%3D&reserved=0 (see implemented at
    > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frawgit.com%2Fw3c%2Fwcag21%2FIssue631%2Fguidelines%2Findex.html%23target-siz&data=02%7C01%7Cmhakkinen%40ets.org%7Cc0f28b5dd5f54d77c27508d558f61620%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C1%7C636512736323906594&sdata=xOzNE7DPm%2FJqNNIRWVJy71mcWj2p1%2B6aYhT%2ByJqZtlY%3D&reserved=0

    > 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>
    >
    > https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7Cmhakkinen%40ets.org%7Cc0f28b5dd5f54d77c27508d558f61620%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C1%7C636512736323906594&sdata=8a%2FyxU67KT6MfTfWl%2FTUGSSLn5KiJTrDWst8Rn2PUQg%3D&reserved=0

    > <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
    https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftestkreis.de&data=02%7C01%7Cmhakkinen%40ets.org%7Cc0f28b5dd5f54d77c27508d558f61620%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C1%7C636512736323906594&sdata=nHsl50WZvgQ2jDWaSJwVWXTMQ4tg29yZy9t6%2BLMGMR4%3D&reserved=0


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





________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________

Received on Thursday, 11 January 2018 14:23:29 UTC