[Fwd: Re: [Fwd: Re: New properties for StatusNotifierItem: Accessible Label (1/3)]]

Matthew Paul Thomas mpt at canonical.com
Tue Mar 1 13:38:49 CET 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sebastian Kügler wrote on 10/02/11 17:22:
>
> On Thursday, February 10, 2011 05:39:08 Ted Gould wrote:
>...
>> I forwarded the discussion that was had about using the title in the
>> tooltip for the accessible label.  While I felt that it was not
>> adequate I couldn't express why.  As per usual, mpt says it better
>> than I, here is his response:
>...
> I understand that it's suboptimal (though thanks, Matthew for laying it
> out in greater detail), my reservation was that many developers simply
> don't care about accessibility enough to add another string, so it
> probable makes sense if the accessible label falls back to the tooltip
> when the developer forgot to specify the accessible label.

In the particular case of StatusNotifierItem, KDE developers may decide
for consistency that they should always, or (as in Ubuntu) should never,
have tooltips. But in general, while all interactive graphic-only
elements should have accessible labels, not all of them need tooltips.
So thinking about it as "add another string" could be a bit misleading.

>...
>> Images in HTML. After a long struggle, accessibility advocates finally
>> got most browsers to treat alt= (the accessible equivalent) and title=
>> (the tooltip) differently, to help Web authors understand that what's
>> good for one is rarely good for the other.
> 
> Exactly, and how many websites end up with this distinction correctly 
> implemented?
>...

In a survey by Opera Software of 3,219,487 Web pages that used the <img>
element, 2,520,939 of them (78%) used alt=, while 367,132 (11%) used
title=.
<http://dev.opera.com/articles/view/mama-images-elements-and-formats/#img>

As far as I know, there are no public statistics on how often <img>
elements have distinct alt= and title= values. But we can conclude, at
least, that Web authors care enough about accessibility to provide
accessible equivalents most of the time.

- -- 
mpt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk1s6NkACgkQ6PUxNfU6ecovQACfQxQArrvx3Hd/8iirN0z+XvQK
AZIAnjVqiyp071ZLORODYLnkY2jjc6vI
=i+4S
-----END PGP SIGNATURE-----


More information about the Plasma-devel mailing list