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

Re: Metadata On Hover SC Text

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Fri, 18 Nov 2016 15:03:13 -0600
Message-ID: <CAOavpvdhFzu7y8q8MqwN2k0B0o4DozbB7_p3rZpsOO4u_dCDUA@mail.gmail.com>
To: alands289@gmail.com
Cc: "public-low-vision-a11y-tf@w3.org" <public-low-vision-a11y-tf@w3.org>
Hi Alan,

Nice to hear from you.

On 11/18/16, alands289@gmail.com <alands289@gmail.com> wrote:
> Just a quick question. Since the original issue was that on iOS and Zoomtext
> it was an enlarged cursor pointer that was the item that was obscuring the
> title mouse over text, how does the informational content not obscuring
> other content solve that original problem?

It doesn't. That was added for Wayne's use case. But I suspect that
may be addressed in another SC.

> Having the informational content that is available upon hover now be
> required to not be the only means of conveying that information does not
> solve the original problem and introduces further requirements for designers
> and developers and perhaps user agents to find some other means of conveying
> that information for visual users. Because, the main issue is for visual
> users, not screen reader users.

It would solve it for visual users if static on-screen labels were
used in addition to tool tips.

> We have made a simple solution into a complex new requirement for designer
> and developers.

It seems to me a static on-screen label is much simpler than hovering.
Rely on simple copy. A text label is clearer and more accessible.

The title attribute has [1] and currently is [2] for advisory
information not critical information. The HTML5 spec warns authors not
to rely on it. WCAG 2.1 would be bolstering that.

If the examples in the screenshots [3],[4],[5],[6], [7],had had a text
label, the Cursor Overlapping Tooltip Text on Hover would be a
non-issue.

> Stating that “the hover text not be covered over by the cursor” is the
> simplest wording for fixing the original issue.

That could work too but it would need to be stated in a positive
statement. And I suspect the WCAG WG would push it off to silver,
resulting in people with disabilities not being helped in the near
term.

Kindest Regards,
Laura

[1]  https://www.w3.org/TR/html401/struct/global.html#h-7.4.3
[2]  https://www.w3.org/TR/2008/WD-html5-20080610/semantics.html#title
[3] https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/File:Obscured_tooltip_footnotes.png
[4] https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/File:Obscured_tooltip_glossary.png
[5] https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/File:Obscured_tooltip_mail.png
[6] https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/File:Obscured_tooltip_firefox.png
[7] http://simplyaccessible.com/wordpress/wp-content/uploads/2013/09/400percentTitleAttribute.png

Kindest Regards,
Laura

-- 
Laura L. Carlson
Received on Friday, 18 November 2016 21:03:49 UTC

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