- From: Laura Carlson <laura.lee.carlson@gmail.com>
- Date: Fri, 18 Nov 2016 10:45:26 -0600
- To: Alastair Campbell <acampbell@nomensa.com>
- Cc: "public-low-vision-a11y-tf@w3.org" <public-low-vision-a11y-tf@w3.org>
Hi Alastair, All good points. Thank you. In one of the early versions [1] we had "Simply Put: Do not rely on tool tips alone" in the description. The SC text was: "Metadata in a webpage that is shown on hover does not include information necessary to perceive content. " So we are going full circle :-) Kindest regards, Laura [1] https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/index.php?title=Metadata_On_Hover&oldid=1978 On 11/18/16, Alastair Campbell <acampbell@nomensa.com> wrote: > Hi Laura, > > That example wouldn’t be covered by either of the proposed “metadata on > hover” wordings because it is not triggered by hover. (It was triggered by > deleting email, onclick on or keypress.) > It also isn’t “informational content” because it has links, and isn’t > meta-data… so it really isn’t covered here! > > Also, if something is already covered by an SC, I thought we would try and > avoid overlap? It is clearly covered by the Resize content one. > > Also, I’m still not clear how the ‘fully visible’ definition would cover the > mouse cursor aspect? > As there is no author controlled way to affect the mouse cursor (except > hiding it!), we really have to go with “not conveying information” that > way. > > Cheers, > > -Alastair > > > On 18/11/2016, 16:13, "Laura Carlson" <laura.lee.carlson@gmail.com> wrote: > > Hi Alastair, > > That's where the "not clipped or truncated" part of the "fully > visible" definition may be able to help if we go the route. > > Thanks. > > Kindest Regards, > Laura > > On 11/18/16, Alastair Campbell <acampbell@nomensa.com> wrote: > >> Question for #4: To address Wayne's use case where the popup covers > >> content in gmail and won't go away > > > > I think that fails 1.4.4 Resize text now, and if it doesn’t then it > will > > fail Resize content. > > > > It is not triggered by hover, it was based on a user-action, it is > just that > > the dismiss button is hidden due to the resizing. > > > > I think we can remove that as an example from this one, but it could > be > > added to resize content. > > > > -Alastair > > > > > > > > > -- > Laura L. Carlson > > > -- Laura L. Carlson
Received on Friday, 18 November 2016 16:46:00 UTC