RE: Metadata On Hover SC Text

Laura,

I see your point. What about this language?

Content that is necessary for understanding which appears on hover, must be:
* discernible,
* not obscured by other content, and
* available via any input method

​​​​​



* katie *
 
Katie Haritos-Shea 
Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)
 
Cell: 703-371-5545 | ryladog@gmail.com | Oakton, VA | LinkedIn Profile | Office: 703-371-5545 | @ryladog


-----Original Message-----
From: Laura Carlson [mailto:laura.lee.carlson@gmail.com] 
Sent: Thursday, November 17, 2016 10:10 AM
To: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
Cc: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>; Alastair Campbell <acampbell@nomensa.com>; Rochford, John <john.rochford@umassmed.edu>; Wayne Dick <wayneedick@gmail.com>
Subject: Re: Metadata On Hover SC Text

Hi Katie,

Thanks. We can certainly can do that. Any thoughts on the following combined text?

Content that is necessary for understanding and appears on hover:
* is discernible,
* does not obscure other content, and
* is available by any input method.

Maybe that is too much for one SC? If so, I can separate Into two SCs.

Kindest Regards,
Laura

On 11/17/16, Katie Haritos-Shea GMAIL <ryladog@gmail.com> wrote:
> Laura,
>
> It should probably be two is my thought
>
> ​​​​​
>
>
>
> * katie *
>
> Katie Haritos-Shea
> Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)
>
> Cell: 703-371-5545 | ryladog@gmail.com | Oakton, VA | LinkedIn Profile 
> |
> Office: 703-371-5545 | @ryladog
>
>
> -----Original Message-----
> From: Laura Carlson [mailto:laura.lee.carlson@gmail.com]
> Sent: Thursday, November 17, 2016 9:13 AM
> To: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>; 
> Alastair Campbell <acampbell@nomensa.com>; Rochford, John 
> <john.rochford@umassmed.edu>; Wayne Dick <wayneedick@gmail.com>
> Subject: Metadata On Hover SC Text
>
> Hi John, Alistair, Wayne, and all,
>
> I am trying to understand the proposed change to the Metadata On Hover 
> [1] SC text. During the October 27th meeting it was changed to:
> "Content that appears on hover should not obscure the triggering 
> element or other content." After that Wayne asked me to add his "Popup 
> Text Overwriting Actionable Buttons Example" screenshot, which I did.
>
> With these 2 changes it seems that the original issue may have gotten lost.
> The original issue was not content obscuring the triggering element or 
> other content. It was the "Cursor Overlapping Tooltip Text on Hover" 
> due to authors using title attributes. Simply put: Authors shouldn't 
> not rely on tool tips alone. Authors should not put important 
> information in title attributes that can become unreadable when content and cursors are enlarged.
> Information should be available through more than one mechanism.
>
> I think either Alistair's or my prior versions of the SC text address 
> that original problem. That SC text was:
>
> 1. "Hidden content that is necessary for understanding is available 
> using any available input method." - Alistair, 25 October 2016 2. 
> "Metadata in a webpage that is shown on mouse-over does not include 
> information necessary to perceive content." - Laura, 21 October 2016
>
> But now that we have 2 different hover issues 1) Cursor Overlapping 
> Tooltip Text on Hover as well as 2) Popup Text Overwriting Actionable 
> Buttons in this one SC, how do we best address both issues? Ideas for new SC verbiage?
>
> Or should they be 2 different SCs?
>
> Thoughts?
>
> Thank you.
>
> Kindest Regards,
> Laura
> [1]
> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Metadata_on_Mouse-Ov
> er
>
> --
> Laura L. Carlson
>
>
>


--
Laura L. Carlson

Received on Thursday, 17 November 2016 15:48:43 UTC