W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2018

RE: Problem with an implementation pass for Target Size

From: Alastair Campbell <acampbell@nomensa.com>
Date: Tue, 3 Apr 2018 23:50:23 +0000
To: "Abma, J.D. (Jake)" <Jake.Abma@ing.com>
CC: 'Andrew Kirkpatrick' <akirkpat@adobe.com>, WCAG <w3c-wai-gl@w3.org>, 'Michael Cooper' <cooper@w3.org>
Message-ID: <AM5PR0902MB20028A706C4B7000E18A317DB9A50@AM5PR0902MB2002.eurprd09.prod.outlook.com>
> In the call I heard that 2.5.3: Target Size was passed for the Lego site, can anyone explain to me why?

Hi Jake,

It wasn't easy to work out, but I couldn't get the buttons to be smaller than about 60px square.

It insists on being landscape, so a reasonable smallest width to test at would be  ~500px wide (i.e. the height of a phone screen), and then the buttons were around 60px. That seemed to give it some leeway as well.

I say "around" because it's a canvas app so I used a screen-capture tool to work out the size of the buttons rather than an inspector approach.

It isn't an ideal example as it basically scales in a non-reflowable way, but it does seem to have reasonably large hit sizes.

I added the CSS below [1] to my site, which is a bit of a hammer to the proverbial nut, but it worked for target size... anyone else fancy doing that?




a, input {
  display: inline-block;
  min-height: 44px !important;
  min-width: 44px !important;

NB: Time to work out CSS? 2 minutes.

Time to install SASS, get the right environment going and get the CSS onto my site? 45min.
Received on Tuesday, 3 April 2018 23:50:59 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:25 UTC