Re: [2.4] Updated proposal for GL 2.4

>SC 1. Structures and relationships within the content can be determined programmatically.
>Editor's note:This is identical to the wording of Guideline 1.3 L1 SC 1 
>("Structures and relationships within the content can be determined programmatically").
>Several people who participated in the 28 October call felt that there should be a Level 1
 >success criterion for this guideline, and that it should be
>identical or nearly identical to 1.3 L1 SC1. 
>There was some discussion about whether to use exactly the same wording, or just link to
 >1.3 L1 SC1. There
>was also some feeling that the reference to "relationships" expressed in 1.3 L1 SC1 would >not be appropriate here. Since the only response to the wording
>proposed on 3 November was a strong comment from Jason that the this SC should be identical >to 1.3 L1 SC1, the wording of 1.3 L1 SC1 is used here as well.
If content does not comply with 1.3 SC 1, it  cannot claim conformance with all level  1 SC
 anyway. I do not see the point of repeating the same SC here under 2.4.
If the SC is met, the content author will merely check off  2.4 SC 1 in the same breath as 
he checks off 1.3 SC 1.
And in order to find content, orient oneself  and be able to navigate, relationships are 
important. For instance,
when lists are nested 2-3 levels in a table of contents, one needs to  be aware of the 
nesting relation in order to perceive  (and by extension, be able to navigate / operate )an 
individual  list item's position in the overall scheme of things.
Sailesh Panchang
Senior Accessibility Engineer 
Deque Systems,11180  Sunrise Valley Drive, 
4th Floor, Reston VA 20191
Tel: 703-225-0380 Extension 105 
E-mail: sailesh.panchang@deque.com
Fax: 703-225-0387
* Look up <http://www.deque.com> *


		
---------------------------------
Do you Yahoo!?
 Discover all that’s new in My Yahoo!