Re: Linking to WAI Guidelines & WAI Resources

Hi Anna, Shawn - my suggestions follow:

h1: Referencing WAI Guidelines and Technical Reports

Remove first para ('This page provides guidance on referencing and 
linking to accessibility guidelines and other technical reports from the 
W3C Web Accessibility Initiative (WAI).') - it just repeats the H1.

H2: Linking to Overview pages

H2: Referencing Technical Documents

>> 1. Swap the columns: first "what", then "URI" followed by "use" and 
>> then "content change". IMO the table as it is now is hard to read.

Suggest URI comes first, then use, then what, then change?

>> 2. Rename the column titles: "what" should be "referenced document", 
>> "use" explains the rules of what to reference with this particular 
>> URI, it extends the column "referenced document", I would rename "use" 
>> into "referencing guidance/instruction".

Not sure about this - suggest 'What' should be relabelled 'Document 
linked to:'?

>> 3. "Content change" is not absolutely necessary it merely repeats what 
>> is stated in "use"

Suggest that the heading here be replaced by 'Will the content at this 
URI change?', and replace the entries that read 'The content at this URI 
will not change.' with 'No.'

>> 4. There is too much text in the current "use". My proposal for each 
>> row of the table:
>> =====
>> WCAG Overview --> URL --> The URL always points to the Guidelines 
>> Overview page. Page content changes over time
>> =====
>> Latest version of the guidelines (draft or approved) --> URI --> The 
>> URL always points to the latest available version of the guideline.
>> =====
>> Latest approved version of the guidelines ---> URI ---> The URL always 
>> points to the latest approved version of the guideline. The content of 
>> the page remains unchanged untill the guidelines are superceeded by 
>> the new approved version.
>> =====
>> Old approved version of the guideline ---> URI ---> The URL always 
>> points to old approved versions of the guideline. The content of the 
>> page remains unchanged untill more guidelines are superceeded by the 
>> new approved version and added to this page.
>> =====
>> I don't see the need in the last row of the table

My suggestion would be:

www.w3.org/WAI/intro/wcag ---> For most links about WCAG ---> WCAG 
Overview ---> Yes, but fragments/targets/anchors will be stable

www.w3.org/TR/WCAG/ ---> For links to the latest version of the WCAG 
technical specification ---> Yes, when there are new versions of WCAG. 
Fragments/targets/anchors may change when new versions are published

www.w3.org/TR/WCAG20/ ---> For links specifically to Version 2.0 of the 
technical specification, and *not* to subsequent versions ---> WCAG 
version 2.0 ---> No

www.w3.org/TR/WCAG10/ --> For links specifically to Version 1.0 of the 
WCAG technical specification, and *not* to subsequent versions. ---> 
WCAG version 1.0 ---> No

www.w3.org/TR/WAI-WEBCONTENT ---> Deprecated. We prefer that for WCAG 
1.0 you use www.w3.org/TR/WCAG10/ ---> Deprecated link to WCAG Version 
1.0 ---> No

One related query. Why is wcag in lower case in the first link, but 
upper case in all the others?

Just my opinion, etc. :)

Regards

Liam

Received on Friday, 20 February 2009 16:59:27 UTC