RE: Problem with an implementation pass for Target Size

Hi Alastair,

I wasn't talking about the round buttons, but the 'previous / next' bars, see attachments.
In the attachments you'll see a landscape Android version and a small browser window.
Both fail the 44X44 for these 'buttons'.
And as it is a canvas 'widget' it all, also the 'previous / next' bars when clicked on a round button, belong to the page, see my previous mail.

Regards,
Jake

Copy of my previous mail:

Hi Michael / all,

In the call I heard that 2.5.3: Target Size was passed for the Lego site, can anyone explain to me why?

https://www.w3.org/WAI/GL/WCAG21/CR/evaluate_central?implementation_id=138

My comment was: It fails smaller viewports where the next / previous buttons  (in the canvas) are clearly less than 44X44 (check mobile or make viewport small)

As far as I know Conformance is like this:


1.       Full pages: Conformance (and conformance level) is for full Web page(s) only, and cannot be achieved if part of a Web page is excluded.

2.       Web page: a non-embedded resource obtained from a single URI using HTTP plus any other resources that are used in the rendering or intended to be rendered together with it by a user agent

a.       Note 1: Although any "other resources" would be rendered together with the primary resource, they would not necessarily be rendered simultaneously with each other.

b.      Note 2: For the purposes of conformance with these guidelines, a resource must be "non-embedded" within the scope of conformance to be considered a Web page.

3.       As we can see the Lego site only has 1 URI and an embedded canvas element which needs to be fully accessible and doesn't contain it's own URIs.

So we have a fail and not a pass.

It's just like we have a page / 1 URI with a collapsible, or accordion, or modal or whatever component / element and when you click on it, it opens or reveals other content.
That complete component / widget / structure needs to be accessible because it's on the page, and not only the loading / beginning state and not "not what's in the collapsed content".

It's the same for the canvas, just as it is when you'll get a keyboard trap when clicking on the canvas buttons and you're stuck we don't say, "well, if you don't click on the canvas element than you're save so we pass it".

So even though 4 people pass it I think they're still wrong or please tell me otherwise.




From: Alastair Campbell [mailto:acampbell@nomensa.com]
Sent: woensdag 4 april 2018 1:50
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>
Subject: RE: Problem with an implementation pass for Target Size

> 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?



Cheers,



-Alastair



1]

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.

-----------------------------------------------------------------
ATTENTION:
The information in this e-mail is confidential and only meant for the intended recipient. If you are not the intended recipient, don't use or disclose it in any way. Please let the sender know and delete the message immediately.
-----------------------------------------------------------------