E-mail List Archives

Re: Available title indication via css


From: Wolfgang Berndorfer
Date: Nov 11, 2017 7:40AM

Hi Patrick,
I know the usage an abuses of the TITLE-atribute.
But I consider the “first usage rule” as a forensic plaster: Expand in plain
text in first instance! If You do, You pass WCAG.
But: Who reads a website from top left to bottom right? And why are we
demanding navigable headings or sections? It’s very easy and probable to
miss the first instance, when You visit a site applying navigational offers.
When I’m personally surfing I’m listening to what my screen reader says and
if I don’t understand something, I look at the monitor using ZoomText. And
it’s very helpful for me and all those, who didn’t read from top left
continuously, when there’s still additional information via TITLE available.
Admittedly not for everyone and unfortunately not for blind and other
non-mouse users.
Here we come to the fundamental discussion: Is allowed, what is helpful for
some, but inaccessible for others? And my other question: Is enough, what is
forensically accessible, but causes predictable usability issues?
These moral question could be interesting new threats.
Best regards!

Zweiter Blick - Für ein barrierefreies Web

Mag. Wolfgang Berndorfer

Akademischer Experte für Barrierefreies Webdesign

A-6020 Innsbruck, Schidlachstr. 9/3

T: +43 (0) 512 / 560 568

M: +43 (0) 664 / 734 934 05



Diese Nachricht und allfällige angehängte Dokumente sind nur für den
Adressaten bzw. die Adressatin bestimmt. Sollten Sie versehentlich dieses
E-Mail erhalten, ist jede Offenlegung, Weiterleitung oder sonstige
Verwendung dieser Information nicht gestattet. In diesem Fall bitten wir,
uns zu verständigen und die Information zu vernichten.

-----Ursprüngliche Nachricht-----
Von: WebAIM-Forum [mailto: <EMAIL REMOVED> ] Im Auftrag
von Patrick H. Lauke
Gesendet: Samstag, 11. November 2017 13:43
Betreff: Re: [WebAIM] Available title indication via css

On 11/11/2017 10:26, Wolfgang Berndorfer wrote:
> Hi Bim,
> Don’t only think of people with disabilities. Imagine, You find an
> abbreviation on a website, You don’t understand: If the abbreviation is
> visually perceivable as titled, You will hover with your mouse and get the
> meaning of the abbreviation as a browser functionality. If the
> TITLE-attribute wasn’t styled, You would probably not try to hover to get
> information. The titled abbreviation just looks like any other
> Styling would help You, if You are sighted and can use the mouse. Even if
> You need a magnification software, You benefit of the visual indication.
> If You need a screen reader, the information You get, depends on Your
> settings and not on the styling. But this is an other issue.
> <span lang="de" title="best regards">Beste Grüße!</span>
> Wolfgang

You're tackling the problem from the "we should make the fact there's a
title attribute on a random element visually clear", whereas the general
advice really is "don't use title attribute in general".

With the exception of MS Edge, no browser shows title attribute tooltips
even on focusable elements. Arbitrary, non-focusable elements with title
of course never show their title in any browser.

Instead of making the use of title more enticing with styling, we should
focus on avoiding title usage. For some elements like
acronyms/abbreviations, title has a clearly defined additional benefit
and per spec the expanded version of the acronym/abbreviation goes in
the title. But for arbitrary elements, you're really still just working
on something that for mouse users happens to provide a tooltip, but is
useless to most other users.

Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke