W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2006

Mapping of WCAG 1 to WCAG 2: issues and comments

From: Christophe Strobbe <christophe.strobbe@esat.kuleuven.be>
Date: Wed, 05 Apr 2006 18:15:41 +0200
Message-Id: <6.0.0.22.2.20060405172226.0305f710@mailserv.esat.kuleuven.be>
To: w3c-wai-gl@w3.org

Hi,

As a follow-up to my previous message, here is a summary of issues and 
comments that I came across while updating the mapping.


For some WCAG 1.0 checkpoints, the previous mapping referred to advisory 
items in a future version of Understanding WCAG 2.0 (for example because 
there are no matching success criteria), but these items have not been 
created or exist only as drafts in the Wiki:
* CP 3.1 (markup rather than images): this would map to GL 1.3 advisory, 
but there is currently no technique for this.
* CP 3.3 (Use style sheets to control layout and presentation): this would 
map to CSS techniques for 1.3.1, CSS techniques for 1.3.2 and a client-side 
scripting technique for 1.3.5 (now 1.3.3). The optional CSS technique for 
1.3.1 is currently empty ('wanted'/red), there is no CSS technique for 
1.3.2 and the style switcher technique for 1.3.3 is currently empty.
* CP 12.3 (divide info into manageable groups): this might map to advisory 
info in GL 3.1, but no technique seems to exist for this. Ordering the 
content in a meaningful sequence[1] addresses something very different. 
Using h1-h6 to identify headings[2] (for 1.3.1) comes close but does not 
match well enough, I think.
* CP 13.2 (metadata to add semantic information): there are proposals for 
techniques with metadata for 3.1.5 (supplements), Using the link element 
and navigation tools (for 2.4.2); no relevant techniques yet for 4.2.
* CP 13.3 (information about the general layout of a site): in addition to 
2.4.2 and 2.4.7, this could also map to an advisory item, but no such item 
or technique seems to exist.
* CP 10.2 (properly positioned labels): this would map to an advisory item, 
unless a success criterion for this issue was created. I'm not sure how 
that action item was closed, but we have no SC for this, nor a relevant 
technique.
* CP 10.5 (printable characters between adjacent links): this would map to 
an advisory item (not for browsers but for people with cognitive 
disabilities); no such technique is available.
* CP 11.3 (information so that users may receive documents according to 
their preferences): this might map to advisory items in Understanding WCAG 
2.0, but no relevant techniques appear to be available.
* CP 13.5 (navigation bars): this would be a possible strategy for SC 
2.4.2, but there is no relevant technique.
* CP 13.8 (distinguishing information at the beginning of headings etc): 
part of this maps to an optional technique for 2.4.5 (Starting section 
headings with unique information), but that technique is only a draft.
[* CP 13.9 (information about document collections): this would map to 
advisory items for 2.4.7, but some techniques are still drafts.]
* CP 13.10 (skip over multi-line ASCII art): this would map to an advisory 
item, but no matching failure or technique seems available.
* CP 5.6 (abbreviations for header labels): this would be "a potentially 
useful technique", but no such technique seems to exist.
* CP 10.4 (place-holding characters in edit boxes and text areas): this is 
marked as "deprecated", but that decision dates back to a time when some 
understood deprecated as "not required", and others as "bad practice". 
Should we add a technique or failure for this (depending on the 
interpretation of "deprecated")?


Some mappings had action items:
* CP 3.4 (relative rather than absolute units): there was action item to 
explore whether there should or shouldn't be a SC about scaling of fonts 
and other presentational elements. I can't remember if or how this was 
closed; I could not find anything about this in Understanding WCAG 2.0.


CP 12.1 (frame titles) used to map to SC 2.4.1, which was removed a few 
weeks ago and SC 2.4.5. I have now mapped it to SC 4.1.2, which seems a bit 
debatable to me, and SC 2.4.4 (which is just the result of renumbering).


Some places in the mapping state that a certain "Until user agents" clause 
has been met, but this information is out of sync with the document 'User 
Agent Support for Accessibility'[3], which is referenced by the defintion 
of "until user agents" in WCAG 1.0:
* CP 7.3 (movement in pages): update 'User Agent Support for Accessibility' 
based on the info in the mapping?
* CP 1.5 (redundnant text links for areas in image maps): update 'User 
Agent Support for Accessibility' based on the info in the mapping?


Editorial issues:
Some places in the mapping are supposed to reference a complete level (all 
success criteria) in a guideline, but this is not possible until the final 
Guidelines document has been generated: the levels have IDs that are 
generated with an XSLT function and which are different each time the XSLT 
is run.
Some places in the mapping refer to techniques (usully advisory items): 
these currently refer to the Wiki because the techniques are not available 
elsewhere. These links will need to be updated for the final mapping.


[1] 
http://trace.wisc.edu/wcag_wiki/index.php?title=Ordering_the_content_in_a_meaningful_sequence
[2] 
http://trace.wisc.edu/wcag_wiki/index.php?title=Using_h1-h6_to_identify_headings
[3] http://www.w3.org/WAI/Resources/WAI-UA-Support

Regards,

Christophe Strobbe


-- 
Christophe Strobbe
K.U.Leuven - Departement of Electrical Engineering - Research Group on 
Document Architectures
Kasteelpark Arenberg 10 - 3001 Leuven-Heverlee - BELGIUM
tel: +32 16 32 85 51
http://www.docarch.be/ 


Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
Received on Wednesday, 5 April 2006 16:15:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:45 GMT