Re: Pointer target spacing issues

Hi All,

I reviewed the three issues re: pointer target spacing and closed one. The
other two bring up a good point of allowing smaller targets with relatively
large inactive areas around them. For example, in figure 2 in the
understanding document
<https://www.w3.org/WAI/WCAG22/Understanding/pointer-target-spacing.html>,
if the buttons were 10 px instead of 38 px, with a spacing of 34 px between
them, it would pass the SC.

Touchscreen heuristics can vary largely depending on capacitive sensitivity
of the material and OEM level design decisions. What is likely confusing is
the difference between padding (interactive area around the element) and
margins (non-interactive spacing).

There is a note in the SC that mentions increasing the hit-area of smaller
targets, which the group might want to consider. My proposal would be at
least 40X40 density independent pixels for mobile/ css pixels for web or 7
mmX7mm for level AA. Below are the mobile guidelines from Android, iOS,
Microsoft and BBC that informed this number.

Google (48X48 dp) :
https://developer.android.com/guide/topics/ui/accessibility/apps#large-controls


Apple (44X44 pt):
https://developer.apple.com/design/human-interface-guidelines/ios/visual-design/adaptivity-and-layout/
Microsoft (40X40 epx) :
https://docs.microsoft.com/en-us/windows/uwp/design/input/guidelines-for-targeting#target-size
BBC (7mmX7mm) :
https://www.bbc.co.uk/guidelines/futuremedia/accessibility/mobile/design/touch-target-size

Please let me know if I missed anything, and next steps I can help with to
resolve these issues. Thank you!

Best,
Sukriti

On Wed, Aug 19, 2020 at 4:48 PM Sukriti Chadha <sukriti1408@gmail.com>
wrote:

> Hi Alastair.
>
> I will review and send proposals by Sunday. Thank you.
>
> Best,
> Sukriti
>
> On Wed, Aug 19, 2020 at 4:26 PM Alastair Campbell <acampbell@nomensa.com>
> wrote:
>
>> Hi folks,
>>
>>
>>
>> Is anyone available to look at the public comments on target spacing?
>>
>>
>> https://github.com/w3c/wcag/issues?q=is%3Aissue+is%3Aopen+label%3A%222.5.8+Pointer+Target+Spacing%22
>>
>>
>>
>> It would be very helpful if someone could:
>>
>>    - Review each of the issues (3 so far);
>>    - Propose an update and/or response;
>>    - Add the label ‘Survey, read for’ when that’s done.
>>
>>
>>
>> They look fairly straightforward so far, I think it will be responses
>> rather than changes.
>>
>>
>>
>> Kind regards,
>>
>>
>>
>> -Alastair
>>
>>
>>
>> --
>>
>>
>>
>> www.nomensa.com
>> tel: +44 (0)117 929 7333 / 07970 879 653
>> follow us: @we_are_nomensa or me: @alastc
>> Nomensa Ltd. King William House, 13 Queen Square, Bristol BS1 4NT
>>
>>
>>
>> Company number: 4214477 | UK VAT registration: GB 771727411
>>
>>
>>
>