W3C home > Mailing lists > Public > public-low-vision-a11y-tf@w3.org > April 2017

Re: Positioning Tooltips - Revisiting Hover SC

From: Wayne Dick <wayneedick@gmail.com>
Date: Mon, 10 Apr 2017 09:40:37 -0700
Message-ID: <CAJeQ8SC6Wf6V7UbFXNtuWxumgTmk=YYQbrn_cknX29WZWHtRUA@mail.gmail.com>
To: Laura Carlson <laura.lee.carlson@gmail.com>
Cc: Marla Runyan <marlarunyan1@gmail.com>, Jim Allan <jimallan@tsbvi.edu>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Hi Laura and Marla,
I can still manage the SC, but I will need to change the wording.

Can we work on this. How do we set up an LVTF wiki dicussion first? I think
we should come up with language first.


On Monday, April 10, 2017, Laura Carlson <laura.lee.carlson@gmail.com>
> Hi Marla and all,
> Wow. This is brilliant. Thank you so very much!
> Tooltips are not obscured in OS X (I tested in Safari, FireFox, and
> Chrome) with the cursor is set to either a medium large or large size
> & with zoom levels set from 0% and up (either full zoom or text zoom).
> The tooltip responds to accommodate zoom settings. Tooltip text
> enlarges. Tooltip is perceivable.
> In addition, I tested on Android 5.0 Lollipop and it works great there
> too. Chrome: all good. FireFox: all good.
> Folks, thanks to Marla it seems we have a solution that authors can
> easily implement.
> I am now in favor of the LVTF pursuing this SC. Wayne, your thoughts
> as SC manager?
> Kindest Regards,
> Laura
> On 4/8/17, Marla Runyan <marlarunyan1@gmail.com> wrote:
>> LVTF,
>> As many of you may recall, the original “Metadata on Hover” SC was
>> addressing the issue of tooltips that are generated from the title
>> being obscured by an enlarged mouse pointer. This is a daily occurrence
>> many low vision users, including myself. While we all know that tooltips
>> should not contain essential information (only advisory information), I
>> don’t see tooltips going away any time soon.  Also, determining whether
>> not their content is “essential” or advisory opens the door for a wide
>> of interpretations — especially when they appear as the only visual label
>> for icons.
>> From a low vision user perspective, encountering a tooltip that I cannot
>> read is a constant reminder of an accessibility barrier — because I see a
>> piece of something, and the rest is out of reach.  So, even if the same
>> content is available on the page, how would I know? All I know is that
>> is something right in front of me that I can’t access. This is a very
>> different experience from a keyboard-only user who is likely not aware
>> a tooltip even exists.
>> So, this got me thinking….
>> Is it possible to position title attribute tooltips ABOVE their triggers?
>> Is it possible to make title attribute tooltips keyboard accessible?
>> The answer is yes.
>> Should we revisit the “metadata on hover” SC, I created a sandbox where I
>> positioned the tooltips above their triggers.
>> The first 3 examples are using the title attribute as the content for the
>> tooltip. The last two examples use a custom tooltip created from a span.
>> All of them appear on hover, so they are also keyboard accessible.
>> https://jsfiddle.net/obsqynyp/4/ <https://jsfiddle.net/obsqynyp/4/>
>> This is far from perfect - just exploring possibilities.
>> Looking forward to discussing further.
>> Thank you,
>> Marla
> --
> Laura L. Carlson
Received on Monday, 10 April 2017 16:41:11 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 April 2017 14:44:34 UTC