W3C home > Mailing lists > Public > public-mobile-a11y-tf@w3.org > January 2018

Re: MATF Minutes 25 January 2018

From: Patrick H. Lauke <plauke@paciellogroup.com>
Date: Thu, 25 Jan 2018 17:45:35 +0000
To: public-mobile-a11y-tf@w3.org
Message-ID: <996d593b-e391-ca80-1e91-9bee3a39b637@paciellogroup.com>
On 25/01/2018 17:13, Kim Patch wrote:
> <Kathy> 
> <http://codepen.io/patrickhlauke/pen/aBNREe>http://codepen.io/patrickhlauke/pen/aBNREe
> Kathy: this example might've been 48, but it's close
> ... it doesn't go around the whole area, just the link itself
> This example to fly because the low-vision task force didn't like it

I seem to remember discussions about people not understanding that the 
green used there was for illustrative purposes only (to show to 
developers where the actual hit target was), and not "this is how a 
website would present it to its users". Do we have a reference to their 
not liking it?

Also, as noted many times: the understanding will have the unenviable 
task of somehow addressing this particularly confusing (some may say 
nonsensical) part of the normative language:

"User Agent Control
The size of the target is determined by the user agent and is not 
modified by the author."

It is still my contention that a strict reading of this means that it 
would practically never be applicable as an exception, as the size given 
by the user agent to a target depends on a huge number of factors 
(including things like the font size of the target, the size/dimensions 
of the element's parent/ancestor elements, etc). Again, strictly reading 
this, I could argue that as soon as an author does anything 
styling-wise, like even just changing the overall document's font size a 
tiny shade from its default, the author has in essence "modified the 
size of the target".

body { font-size: 0.99em; } or even body ( font-size: 1.01em; } or 
whatever will influence all font sizes throughout the document, 
including the font size of links/buttons/etc - resulting in a change in 
the target size due to author modification.

Limiting this in understanding to something like "CSS applied directly 
to the element in question, and only limited to changes in dimensions, 
padding, margin, font-size" may work to an extent, but then an author 
can simply avoid setting those on the actual element, and instead put a 
<span> wrapper or whatever around it...nominally being able to claim 
that they adhered to the above limiting clause...but in effect still 
modifying exactly what this seemed to intend not to allow modification of.

I did comment about this exception on many occasions on list and on 
github, but sadly it was never even aknowledged. Now it'll fall to the 
understanding document to somehow square this circle, sadly.

Patrick H. Lauke
Senior Accessibility Engineer
The Paciello Group
A VFO™ Company http://www.vfo-group.com/
This message is intended to be confidential and may be legally 
privileged. It is intended solely for the addressee. If you are not the 
intended recipient, please delete this message from your system and 
notify us immediately. Any disclosure, copying, distribution or action 
taken or omitted to be taken by an unintended recipient in reliance on 
this message is prohibited and may be unlawful.
Received on Thursday, 25 January 2018 17:45:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:29:42 UTC