W3C home > Mailing lists > Public > public-html@w3.org > October 2008

Re: title/alt attribut keyboard accessibility

From: Robert J Burns <rob@robburns.com>
Date: Wed, 29 Oct 2008 10:48:27 -0500
Cc: "HTML WG" <public-html@w3.org>, "Steve Faulkner" <faulkner.steve@gmail.com>, "W3C WAI-XTECH" <wai-xtech@w3.org>, "aurélien levy" <aurelien.levy@free.fr>
Message-Id: <15653FB2-FE31-4CE3-A1BC-4CDD2A084696@robburns.com>
To: "Laura Carlson" <laura.lee.carlson@gmail.com>

Hi Laura,

On Oct 27, 2008, at 6:38 PM, Laura Carlson wrote:

> Steve Faulkner <faulkner.steve@gmail.com>, W3C WAI-XTECH <wai-xtech@w3.org 
> >
> Aurélien Levy wrote [1]:
>>> Is it possible to have something in the spec to say that the way of
>>> rendering the content of the title/alt attribut must be non  
>>> specific to
>>> a certain type of pointing device or is it to the UAAG spec to say
>>> something like that ?
> Ian Hickson wrote [2]:
>> Right now HTML5 doesn't say that user agents should do anything  
>> with this
>> information. The non-normative rendering section will probably  
>> suggest
>> current behaviour but hasn't been written yet. (Volunteer editors  
>> welcome;
>> see the e-mail from earlier today.)
> Related: Steve Faulkner's June 6, 2008 bug report "User Agent display
> of title attribute content not defined":
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=5807
> [1] http://lists.w3.org/Archives/Public/public-html/2008Oct/thread.html#msg131
> [2] http://lists.w3.org/Archives/Public/public-html/2008Oct/thread.html#msg134

This also relates to my earlier proposal to separate the presentations  
and semantics of a tooltip[1], where I suggest we liaison with the CSS  
WG to encourage them to allow authors control over visual tooltips. An  
important supplement to that proposal is also my suggestion to add  
norms for interactive UAs to provide users access to document data  
that may not be presented with the current stylesheet (such as alt and  
title, etc.).[2][3] The proposal then is not to specify how  
interactive UAs present the document data, rather to require that the  
UAs expose this data in a way users can understand in the UA's  
appropriate UI. Currently UAs often provide a source view or even an  
inspector. The problem is that there are certain pieces of a document  
that are semantically more important for the user consumer to have  
access to and requiring users to delve into the document source or a  
overly rich inspector is a barrier to user comprehension of the  

Take care,

[1]: <http://esw.w3.org/topic/HTML/TooltipSemanticsAndPresentation>
[2]: <http://esw.w3.org/topic/HTML/RicherUIAccessToHTMLData>
[3]: <http://www.w3.org/Bugs/Public/show_bug.cgi?id=5756>
Received on Wednesday, 29 October 2008 15:49:15 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:38 UTC