- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 30 Jan 2019 23:00:16 +0000
- To: Jim Allan <jimallan@tsbvi.edu>, Wayne Dick <wayneedick@gmail.com>, MATF <public-mobile-a11y-tf@w3.org>
- Cc: Alastair Campbell <acampbell@nomensa.com>, Jonathan Avila <jon.avila@levelaccess.com>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
The topics might be related, but I'd caution not to mix the intents here:
- ensuring that controls etc can be comfortably and confidently
activated with a pointer (touch, mouse, stylus, ...)
- ensuring that adjacent controls are visually distinguishable
On 30/01/2019 15:46, Jim Allan wrote:
[...]
> one caveat - the articles all point back to google/android specs. Most
> other articles related to target spacing are vague ("reasonable space",
> "a good amount of space", etc.) and are not helpful.
This is probably because other articles (and even the
Google/Apple/Microsoft/etc guidelines) have the luxury of not having to
set a binary pass/fail threshold. They're recommendations that stem from
nuanced interpretations (and worth noting that even
Google/Apple/Microsoft/etc break their own guidelines on this in their
own products/apps on occasion for controls that are not deemed
"essential / primary" - a concept which could not be sufficiently
clearly defined for the purposes of WCAG SCs)
P
--
Patrick H. Lauke
www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Wednesday, 30 January 2019 23:00:40 UTC