W3C home > Mailing lists > Public > www-style@w3.org > October 2011

Re: [css3-speech] LC comment: Appendix B Index: why such cryptic hyperlink text?

From: Daniel Weck <daniel.weck@gmail.com>
Date: Thu, 20 Oct 2011 00:59:39 +0100
Cc: W3C style mailing list <www-style@w3.org>, wai-xtech <wai-xtech@w3.org>, Bert Bos <bert@w3.org>
Message-Id: <48CBE9A9-395F-435B-A8F4-BBBEFD1A9F64@gmail.com>
To: "Gregory J. Rosmaita" <gregory.rosmaita@gmail.com>
Hello Greg,
just a heads-up to let you know that the CSS Working Group has reviewed this issue, and the consensus is that we should indeed fix the links in the automatically-generated index. This will improve the accessibility of not only the Speech specification, but also of all the other CSS specifications that contain such index.

Could you please give us some advice regarding the kind of text and title/alt-text (for a given index entry) that would work best for a screen-reader user? Many thanks!

Kind regards, Dan

On 12 Oct 2011, at 14:37, Daniel Weck wrote:

> Hi Greg, just a quick response to let you know that the Working Group is looking into how to improve the links generated in the document index. Thank you for raising the issue. As it applies not only to CSS3-Speech, but to every CSS specification that contain an automatically-generated index, I don't think this is a blocking issue for this particular CSS Module. Kind regards, Dan
> 
> On 1 Oct 2011, at 04:19, Gregory Rosmaita wrote:
> 
>> aloha!
>> 
>> i find the hyperlink text used in Appendix B to be useless, especially
>> as that hyperlink text contains either a number or a number-sign --
>> what is the hyperlink text in the index intended to convey?
>> 
>> the hyperlink text should be as unambiguous as possible, and avoid the
>> repeated use of identical link text to point to different resources,
>> as per WCAG 2.0:
>> 
>> WCAG 2.0 Guideline 2.4 - Navigable: Provide ways to help users navigate,
>> find content, and determine where they are:
>> * http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms.html
>> 
>> 2.4.9 Link Purpose (Link Only): A mechanism is available to allow the
>> purpose of each link to be identified from link text alone, except
>> where the purpose of the link would be ambiguous to users in general.
>> (Level AAA)
>> * http://www.w3.org/WAI/WCAG20/quickref/#qr-navigation-mechanisms-link
>> * http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-link.html
>> * http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/G91
>> 
>> one means of improving the index is WCAG 2.0 Technique C7
>> 
>> * http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/C7
>> 
>> which provides a means of providing disambiguating hyperlink text for
>> aural and/or tactile contextualization
>> 
>> thanks, gregory.
>> 
>> --------------------------------------------------------------
>> You cannot depend on your eyes when your imagination is out of
>> focus.                                           -- Mark Twain
>> --------------------------------------------------------------
>> Gregory J. Rosmaita: gregory.rosmaita@gmail.com
>>    Camera Obscura: http://www.hicom.net/~oedipus/
>>         Oedipus' Online Complex: http://my.opera.com/oedipus
>> --------------------------------------------------------------
>> 
> 
Received on Thursday, 20 October 2011 00:00:24 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:45 GMT