W3C home > Mailing lists > Public > public-html@w3.org > December 2011

Re: HTML5 implementor feedback requested - title attribute accessibility mapping

From: Charles McCathieNevile <chaals@opera.com>
Date: Tue, 20 Dec 2011 17:43:33 +0100
To: "Adrian Bateman" <adrianba@microsoft.com>, "Maciej Stachowiak" <mjs@apple.com>, "Anne van Kesteren" <annevk@opera.com>, "L. David Baron" <dbaron@dbaron.org>, "Steve Faulkner" <faulkner.steve@gmail.com>
Cc: "HTMLWG WG" <public-html@w3.org>, "Sam Ruby" <rubys@intertwingly.net>, "Paul Cotton" <Paul.Cotton@microsoft.com>, "Ian Hickson" <ian@hixie.ch>, "HTML Accessibility Task Force" <public-html-a11y@w3.org>, "David Bolter" <dbolter@mozilla.com>
Message-ID: <op.v6srevhuwxe0ny@widsith-3.local>
On Mon, 12 Dec 2011 12:54:58 +0100, Steve Faulkner  
<faulkner.steve@gmail.com> wrote:

> Your feedback on this would be appreciated.
>
> The title attribute as implemented (in all browsers that implement
> accessibility support) is mapped to the accessible name in all
> accessibility APIs in all browsers (that implement mapping),

We don't do this currently.

> so in the
> absence of other labelling mechanisms, all HTML form controls are
> labelled by the title attribute content if present. The same goes for
> most other HTML elements. This reality is not reflected in the usage
> advice in the spec.

The spec doesn't seem to match the reality of existing content and advice.

> There is a WCAG technique that documents how to use the title
> attribute to label controls: H65: Using the title attribute to
> identify form controls when the label element cannot be used
> http://www.w3.org/TR/WCAG20-TECHS/H65
>
> There is another WCAG 2.0 technique that documents how to use the
> title attribute to identify frame and iframe elements
> H64: Using the title attribute of the frame and iframe elements
> http://www.w3.org/TR/WCAG-TECHS/H64.html
>
> The HTML5 specification does not provide any advice on how the title
> attribute content is used (as detailed above).
> I filed a bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=14740
>
> the rationale provided by the HTML5 editor for its rejection:
>
> "Rationale: If browsers map it in a manner inconsistent with its  
> meaning, that should be fixed."

Assuming "that" means "the meaning the specification draft currently  
suggests", the rationale makes sense but rejecting the bug goes counter to  
it.

> Do any implementors have any plans to change the current
> implementation in browsers to match the HTML5 specification meaning?
>
> i.e. are there any plans to stop mapping the title attribute to the
> accessible name in accessibility APIs? So that it does not provide a
> label for controls and other elements?

We're unlikely to do anything new for accessibility that works against  
what other implementations do although we may do new stuff that enhances  
the platform without introducing conflicts. We don't have any strong plans  
either way, but we're likely to follow the other browsers on this.

cheers

Chaals

-- 
Charles 'chaals' McCathieNevile  Opera Software, Standards Group
     je parle français -- hablo español -- jeg kan litt norsk
http://my.opera.com/chaals       Try Opera: http://www.opera.com
Received on Tuesday, 20 December 2011 16:44:33 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:29 UTC