W3C home > Mailing lists > Public > www-international@w3.org > January to March 2014

Re: [review feedback] qa-choosing-encodings

From: Gunnar Bittersmann <gunnar@bittersmann.de>
Date: Mon, 10 Mar 2014 14:08:06 +0100
Message-ID: <531DB936.7010708@bittersmann.de>
To: Richard Ishida <ishida@w3.org>, www-international@w3.org

>> »»
>> The HTML5 specification  <a
>> href="http://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset">says</a>
>> ««
>> Link titles should speak for themselves; “says” does not.
>> Make “The HTML5 specification” or “The HTML5 specification says” the
>> link title.
>> »»
>> The HTML5 specification <a
>> href="http://dev.w3.org/html5/spec/semantics.html#charset">calls out</a>
>> a number of encodings that you should avoid.
>> ««
>> Same here. Use “The HTML5 specification (calls out)” or even better “a
>> number of encodings that you should avoid” as link title.
> I don't want to make these changes. This is not a general link to the
> HTML spec, just to the specific point which talks about the topic in
> question. In some cases there may be a need to point to both, separately.

My concers are not about the link destinations, but about the link titles.

This is also an accessibility issue. Screenreader users who navigate 
through the links on the page would just hear “says” and “call out” 
which would mean nothing to them. It does not say anything about what 
content might be behind those links.

Links labelled as “The HTML5 specification (says / calls out)” are much 
more helpful.

The same applies to sighted users who scan the links on the page, either 
visually by font color or using the tab key.

Received on Monday, 10 March 2014 13:08:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:04 UTC