Re: Pointer target spacing issues

For mobile devices, it seems like a miss even for AA if users with mobility
or vision limitations aren't able to identify or reasonably tap an element
due to small size. It doesn't have to be 44 px, but something reasonable
that allows for design choices.
While most designers won't make the choice to have unreasonably small tap
targets, it seems the larger community is concerned and we might want to
gather more opinions in the group to see if setting a floor is an option
for AA.

The other option could be - like text resizing, if there is a mechanism to
magnify tap targets (eg. Pinch and zoom), we don't need to specify a
certain pixel minimum. I'll wait to respond or put in a PR until more input
from you and the group. Thank you.

Best,
Sukriti


On Sun, Aug 23, 2020, 8:24 PM Patrick H. Lauke <redux@splintered.co.uk>
wrote:

> On 24/08/2020 00:39, Sukriti Chadha wrote:
> > Thank you Patrick. Makes sense about BBC, added those in addition to the
> > most relevant ones just in case. Thank you for pointing that out.
> >
> > The question is about 2.5.5 being AAA and 2.5.8 AA - should we discuss
> > with the group having an AA for target size, or would adding a reference
> > to 2.5.5 to the 2.5.8 understanding document suffice?
>
> AA: no minimum target size, but at least make sure that users are not
> likely to accidentally activate the wrong target if they're crowded too
> close together.
> AAA: make sure targets are large enough so they can be confidently
> activated.
>
> Seems a reasonable escalation of priorities.
>
> P
> --
> Patrick H. Lauke
>
> https://www.splintered.co.uk/ | https://github.com/patrickhlauke
> https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>