W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > June 2007

direct context or DOM context

From: WCAG 2.0 Comment Form <nobody@w3.org>
Date: Tue, 26 Jun 2007 16:03:00 +0000 (GMT)
To: public-comments-wcag20@w3.org
Message-Id: <20070626160300.2DBF86B643@tibor.w3.org>

Name: Aurélien Levy
Email: aurelien.levy@free.fr
Affiliation: tektonika
Document: TD
Item Number: F63: Failure of SC 2.4.6 due to providing link context only in content that is not related...
Part of Item: Examples
Comment Type: technical
Summary of Issue: direct context or DOM context
Comment (Including rationale for any proposed change):
I disagree with this failure because link can\'t be used out of context and there is always a DOM context, it\'s an AT missing feature to have an easy way to read full parent element, next sibling or preview sibling. 

For your example :


<p>A British businessman has racked up 2 million flyer miles and plans to 

travel on the world\'s first commercial tourism flights to space.</p>

<p><a href=\"ff.html\">Read More...</a></p>


the user must be able to read the brothers element of the a element (in this case empty), or read the brothers element of his parent element (in this case the content of the previous p element, or read the content of his grandfather (in this case the whole div element)

In definition list, dd go whis dt so if i read an a element in a dd i must be able to access to content of the previous dt element and brothers dd elements

Furthermore, if there is a title attribute with a title longer than the content of the a element and explaining the purpose of the link, i think the test must passed.

Make your choice, stay in the wcag 1.0 position and say the link must be understandable out of context or just say ok it\'s nearly impossible, so if you can\'t do it, use the title attribute to do so (or act that it impossible at all).

Proposed Change:
Received on Tuesday, 26 June 2007 16:03:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:14:44 UTC