Re: HTML5 implementor feedback requested - title attribute accessibility mapping

Here are some real world examples of the title attribute being used to
label interactive content:

the search text box on https://www.google.com/

<input type="text" maxlength="2048" name="q" id="lst-ib"
autocomplete="off" size="41" title="Search" value="" class="gsfi"
dir="ltr" style="left: 0pt; border: medium none; padding: 0pt 0pt 0pt
2px; margin: 0pt; width: 100%; outline: medium none; top: 1px;
overflow: hidden; background:
url(&quot;data:image/gif;base64,R0lGODlhAQABAID/AMDAwAAAACH5BAEAAAAALAAAAAABAAEAAAICRAEAOw%3D%3D&quot;)
repeat scroll 0% 0% transparent; position: absolute; z-index: 5;
color: transparent;" spellcheck="false">

The 'notifications' and 'Options' custom controls on https://www.google.com/
<a aria-owns="gbd1" aria-haspopup="true" onclick="gbar.tg(event,this)"
title="Notifications"
href="https://plus.google.com/u/0/notifications/all?hl=en" id="gbg1"
class="gbgt gbgtd"><span class="gbtb2"></span><span class="gbts"
id="gbgs1"><span class="gbid" id="gbi1a"></span><span class="gbids"
id="gbi1">0</span></span></a>

<a aria-owns="gbd5" aria-haspopup="true" onclick="gbar.tg(event,this)"
title="Options" href="http://www.google.com/preferences?hl=en"
id="gbg5" class="gbgt"><span class="gbtb2"></span><span class="gbts"
id="gbgs5"><span id="gbi5"></span></span></a>

search text box on http://www.microsoft.com:

<input type="text" autocomplete="off" class="hpSrc_Textbox"
title="Search Microsoft.com"
id="ctl00_ctl07_SectionRepeater_ctl00_ItemRepeater_ctl00_ctl01_hpSearchTextBox"
name="ctl00$ctl07$SectionRepeater$ctl00$ItemRepeater$ctl00$ctl01$hpSearchTextBox"
style="width: 219px;">


search text box on www.Yahoo.com
<input type="text" autocomplete="off" value="" title="Search" name="p"
class="input-query input-long med-large  " id="p_13838465-p" style="">

Yahoo mail custom button

<a title="Next Page" data-action="next-page" class="icon next"
aria-disabled="true" role="button" href="#"></a>


If you would like more examples let me know

regards
steve



On 17 December 2011 11:04, 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."
>
> [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



-- 
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 Saturday, 17 December 2011 19:34:50 UTC