W3C home > Mailing lists > Public > public-wai-ert@w3.org > July 2005

[Fwd: Location Property]

From: Shadi Abou-Zahra <shadi@w3.org>
Date: Wed, 20 Jul 2005 01:28:44 +0200
Message-ID: <42DD8CAC.9070205@w3.org>
To: public-wai-ert@w3.org

[relaying to active list]

-------- Original Message --------
Subject: Location Property
Resent-Date: Mon, 18 Jul 2005 14:33:12 +0000
Resent-From: w3c-wai-er-ig@w3.org
Date: Mon, 18 Jul 2005 09:58:22 -0400
From: Chris Ridpath <chris.ridpath@utoronto.ca>
To: WAI ER IG List <w3c-wai-er-ig@w3.org>

The current draft EARL schema does not seem to have any properties to 
describe the location of the error. We've discussed these issues earlier on 
the list [1] and I believe we need these properties and that they should be 
part of the assertion. Here's my formal proposal:

1) Each assertion that describes an error needs to describe where the error 
occurs. For example, if an HTML page contained the error "image is missing 
an alt attribute" we need to state which image. It's not enough to simply 
state that the content contains an error, you've got to state where it is.

2) The location properties that we use to describe the error is dependant on 
the accessibility test that is performed. For example, the properties used 
to describe HTML errors will be different from the properties used to 
describe errors in Flash or PDF.

3) The location properties should be precise and interoperable. We need to 
describe as clearly as possible where the error occurred and this should be 
done in a standard manner so the results may be exchanged with other 
programs. I suggest that for HTML errors we require that at least one xpath 
expression be used to describe the accessibility error.

4) More than one location property may be required. For example, to describe 
a series of links that should be grouped with a list element, properties to 
identify all the links in the group would be required. The number of 
location properties is dependant on the accessibility test. If more than one 
location property is used then each property must have a title to describe 

5) Other optional location properties may be included. For example line and 
column numbers could be included as well as xpath expressions.

6) The location properties apply to the content evaluated and do not 
necessarily locate the error when the document has been modified.

7) Other location 'hint' properties may be included for finding the error if 
the document is modified.

Example EARL code for discussion:

This example locates an image within the document that has failed the test 
"all images must have an alt attribute".

<rdf:li rdf:parseType="Resource">

This example locates the anchor that has failed the test "all source anchors 
contain text that describes the link destination". Here is the problem HTML 
<a href="spending.html"><img src="more.gif" width="30" height="10" 

The problem is that the alt text for the image does not describe the link 


<!-- the anchor element -->
<rdf:li rdf:parseType="Resource">

<!-- the image within the anchor -->
<rdf:li rdf:parseType="Resource">
<earl:xpath>/html/body/p/a/img[@src="more.gif" and 


Comments appreciated.


[1] http://lists.w3.org/Archives/Public/public-wai-ert/2005Mar/0092.html 

Shadi Abou-Zahra,     Web Accessibility Specialist for Europe 
Chair and Team Contact for the Evaluation and Repair Tools WG 
World Wide Web Consortium (W3C),           http://www.w3.org/ 
Web Accessibility Initiative (WAI),    http://www.w3.org/WAI/ 
WAI-TIES Project,                 http://www.w3.org/WAI/TIES/ 
Evaluation and Repair Tools WG,     http://www.w3.org/WAI/ER/ 
2004, Route des Lucioles -- 06560, Sophia-Antipolis -- France 
Voice: +33(0)4 92 38 50 64           Fax: +33(0)4 92 38 78 22 
Received on Tuesday, 19 July 2005 23:28:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:53 UTC