Re: 48px vs 44px target sizing

I agree if we get larger than the 50px range, we'll be looking at AAA and
fancy toggle accessibility mode options, etc... otherwise corporate
stakeholders just won't accept our standard.


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 Mon, Sep 5, 2016 at 11:36 AM, Alastair Campbell <acampbell@nomensa.com>
wrote:

> > “Buttons in study were 20mm = 75px with spacing of   6.35mm = 24 px
>  (conversion here https://css-tricks.com/the-lengths-of-css/ ) This was
> based on research listed below.“
>
> You have to be careful converting from physical to CSS units when you
> don’t have the digital sizing specified.
>
> They were using a 10.1 inch tablet, with 1200x800 resolution.  For the
> Galaxy Tab 10.1 the device-pixels = CSS pixels, so ~150 pixels per inch.
> http://dpi.lv/#800×1280@10.1″
>
> As 1 inch=25.4mm, so 6px per mm on the tablet, although that is 2D which I
> think means 2.5px per non-square mm.
>
> Therefore 20mm wide = 50px on that device.
>
> It is a shame they don’t actually specify the sizing from a programming
> point of view, but I think 50px is more realistic and wouldn’t look odd.
>
> I’ve some (expensive?) reading to do, but presumably it is a sliding scale
> kind of thing? Obviously bigger is easier, but then you get to the point of
> having one button on a screen, where do we draw the line?
>
> I suspect that if we specified more than the platform guidelines, we’re
> looking at a triple-A level criterial that might be better done on the
> user-agent side anyway...
>
> Cheers,
>
> -Alastair
>
>
>