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

Re: HTML5 implementor feedback requested - title attribute accessibility mapping

From: david bolter <david.bolter@gmail.com>
Date: Mon, 19 Dec 2011 10:44:01 -0500
Message-ID: <CAEO7jQBcsHL7=ts=3m0tGZKXB5oXSin3qGmyQsFhN-n1=UCFXQ@mail.gmail.com>
To: Steve Faulkner <faulkner.steve@gmail.com>
Cc: "Sharon Newman (COHEN)" <Sharon.Newman@microsoft.com>, Adrian Bateman <adrianba@microsoft.com>, Maciej Stachowiak <mjs@apple.com>, Anne van Kesteren <annevk@opera.com>, "L. David Baron" <dbaron@dbaron.org>, 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>
Hi Steve,

On Sat, Dec 17, 2011 at 6:04 AM, Steve Faulkner <faulkner.steve@gmail.com>wrote:

> Hi Sharon, thanks for the feedback
>
> > Steve - I'm a little confused about the exact issue you are trying to
> resolve.  Can you clarify the text you would propose be >added to the title
> attribute definition before we comment further?
>
>
> current spec definition
>
> "The title attribute represents advisory information for the element,
> such as would be appropriate for a tooltip. On a link, this could be
> the title or a description of the target resource; on an image, it
> could be the image credit or a description of the image; on a
> paragraph, it could be a footnote or commentary on the text; on a
> citation, it could be further information about the source; and so
> forth. The value is text."
>
> http://dev.w3.org/html5/spec/Overview.html#the-title-attribute
>
>
> suggested spec text in parentheses { }
>
>
> "The title attribute represents advisory information for the element,
> such as would be appropriate for a tooltip. On a link, this could be
> the title or a description of the target resource; on an image, it
> could be the image credit or a description of the image; on a
> paragraph, it could be a footnote or commentary on the text; on a
> citation, it could be further information about the source;
>
> {on interactive content[1] it could be a label for, or instructions
> for, use of an element}
>
> and so forth. The value is text."
>


This proposed text seems reasonable to me.

Cheers,
David


> [1] phrase 'interactive content' linked
> http://dev.w3.org/html5/spec/Overview.html#interactive-content-0
>
>
> Does this help?
>
> The text is intended to clarify  usage and pave the well trodden cow
> path of title attribute usage as a label for form controls:
>
> IBM accessibility advice on use of title attribute:
> http://www-03.ibm.com/able/guidelines/web/webforms.html
>
> aforementioned WCAG 2 technique:
> http://www.w3.org/TR/WCAG20-TECHS/H65
>
> Illinois Center for Information Technology and Web Accessibility
> (Labels for Form Controls Rules)
> http://html.cita.uiuc.edu/nav/form/form-rules.php
>
>
>
>
> regards
> Stevef
>
> On 17 December 2011 00:31, Sharon Newman (COHEN)
> <Sharon.Newman@microsoft.com> wrote:
> > Steve - I'm a little confused about the exact issue you are trying to
> resolve.  Can you clarify the text you would propose be added to the title
> attribute definition before we comment further?
> >
> > We don't plan to change the way title is mapped into the accessible name
> right now.
> >
> > -sharon
> >
> >
> > -----Original Message-----
> > From: Steve Faulkner [mailto:faulkner.steve@gmail.com]
> > Sent: Monday, December 12, 2011 3:55 AM
> > To: Adrian Bateman; Maciej Stachowiak; Anne van Kesteren; L. David Baron
> > Cc: HTMLWG WG; Sam Ruby; Paul Cotton; Ian Hickson; HTML Accessibility
> Task Force; David Bolter
> > Subject: HTML5 implementor feedback requested - title attribute
> accessibility mapping
> >
> > Hi Adrian, Maciej, Anne and David
> > (note: if there is a more approriate implementor representative this
> email should go to please advise)
> >
> > 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), 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.
> >
> > 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."
> >
> > 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?
> >
> >
> > with regards
> > Stevef
> >
> >
> >
>
>
>
> --
> with regards
>
> Steve Faulkner
> Technical Director - TPG
>
> www.paciellogroup.com | www.HTML5accessibility.com |
> www.twitter.com/stevefaulkner
> HTML5: Techniques for providing useful text alternatives -
> dev.w3.org/html5/alt-techniques/
> Web Accessibility Toolbar -
> www.paciellogroup.com/resources/wat-ie-about.html
>
>
Received on Monday, 19 December 2011 15:44:45 UTC

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