Re: Target size proposal

I would +1 it with the last exception included...

If the last exception has trouble passing I would be OK with swapping it
with

"the target is in a menu or disclosure"

referring to the aria authoring doc

https://www.w3.org/TR/wai-aria-practices-1.1/#menu
https://www.w3.org/TR/wai-aria-practices-1.1/#disclosure

I could also live with patrick's suggestion

Exception no coarse pointer: no touchscreen or coarse pointer was detected
when using a technology supported query"




Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Tue, Jan 16, 2018 at 5:47 PM, Alastair Campbell <acampbell@nomensa.com>
wrote:

> Hi Everyone,
>
> >From the call, Kathy's proposal was:
>
> 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 26 by 26 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
>
> And (possibly) another exception such as:
> -       Viewport size: The viewport size has a length (height or width) of
> at least 1000 CSS pixels.
>
> Kind regards,
>
> -Alastair
>
> --
>
> www.nomensa.com
> @alastc
>
>