Edit comment LC-2620 for Accessibility Guidelines Working Group

Previous: LC-2605 Next: LC-2596

Comment LC-2620: Comment Shortname:; Commenter: Devarshi Pant <devarshipant@gmail.com>; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
Note that a screen reader like JAWS allows users to set 'expand abbreviation' and 'expand acronym' in their configuration settings, which goes against the user agent notes that cite the title attribute. The fact is that this technique is about acronyms and abbreviation.
The first two pointers do not seem to be in the right place follow:
">Assistive technologies provide different levels of support for speaking title attributes. Some do not include features that allow users to access information provided via the title attribute.
>Implementing this technique with the title attribute is only sufficient if the title attribute is accessibility supported. The content of the title attribute needs to be available to all keyboard users (not only those with text-to-speech software) for this attribute to be accessibility supported."

Proposed Change:
Replace the first two pointers with:

> Assistive technologies provide different levels of support for speaking abbreviations and acronyms.; Related issues: (space separated ids); WG Notes: I think Devarshi Pant is right. One may add that even where screen reader support exists in principle, it will be dependent on the activation of specific customization settings. suggest NOT removing the following, the advice in this point is correct "Implementing this technique with the title attribute is only sufficient if the title attribute is accessibility supported. The content of the title attribute needs to be available to all keyboard users (not only those with text-to-speech software) for this attribute to be accessibility supported." It is not pertaining to assistive technology it is about non mouse users. The technology notes are about user agents (i.e. browsers as well as AT). refer to http://www.paciellogroup.com/blog/2010/11/using-the-html-title-attribute/ Stevef; Resolution: [DONE] Replace the first user agent note with "Assistive technologies provide different levels of support for speaking abbreviations and acronyms, often dependent upon specific customization settings." [DONE] Change the wording of the second note to start "This technique is only sufficient if the <code>abbr</code> or <code>acronym</code> element's <code>title</code> attribute is accessibility supported." [DONE] Add to Resources: 'HTML title attribute' http://www.paciellogroup.com/blog/2010/11/using-the-html-title-attribute/ Response to commenter: Thank you for raising this. We have replace the first user agent note with your proposed text. However, we retained the second note, since access to the abbreviation expansion for keyboard users is often missing.; (Please make sure the resolution is adapted for public consumption)