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

Re: [review feedback] qa-choosing-encodings

From: Eric Eggert <ee@w3.org>
Date: Tue, 11 Mar 2014 13:09:10 +0100
To: www-international@w3.org
Message-ID: <5126BFC4-C190-4E19-8844-4A26C5AEDA7D@w3.org>
Hi Gunnar, hi Richard,

>>> »»
>>> 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.
> Richard,
> 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.

It fulfills WCAG Success Criteria 2.4.4 „Link Purpose (In 
Context)“[1] which says

> 2.4.4 Link Purpose (In Context): The purpose of each link can be 
> determined from the link text alone or from the link text together 
> with its programmatically determined link context, except where the 
> purpose of the link would be ambiguous to users in general. (Level A)

But I think the over all usability of the text may be improved by having 
the heading of the linked section included in the links, e.g.

You can find a number of encodings that you should avoid in the <a 
specification on specifying the document’s character encoding</a>.

Best, Eric



Eric Eggert, Web Accessibility Specialist
WAI-ACT Project

I’m yatil on IRC.
Received on Tuesday, 11 March 2014 12:09:38 UTC

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