Re: April 24 version UAAG-WCAG2.0 alignment

At 20:43 24/04/2006, Jim Allan wrote:
>http://www.tsbvi.edu/technology/uawg/wcag2b.html

I have worked on the mapping between WCAG 1 and WCAG 2 [1] and I've been 
asked how the UAAG-WCAG2 correlation relates to the WCAG mapping.
Here are some comments I have on your correlation table.

WCAG 2.0 SC 1.3.1: would UAAG CP 6.6 be "shared"?

WCAG 2.0 SC 1.3.3: I don't think that UAAG CP 4.1 and 4.2 map to this SC; I 
would map them to WCAG GL 1.3. One way to fail WCAG 2.0 SC 1.3.3 is having 
a stylesheet that positions the content in a way that changes the meaning 
of the content. I wonder if UAAG CP 4.14 correlates here somehow. I also 
don't see how UAAG CP 4.11 would correlate to this WCAG SC.

WCAG 2.0 SC 1.4.1: I also don't see how UAAG CP 10.2 would correlate to 
this WCAG SC; I think that this UAAG CP supports the second part of WCAG 
2.0 SC 1.3.1 ("notification of changes...").

For WCAG 2.0 SC 2.1.1 there is a comment: "jr: 11.4 seems not to fit". If 
"single-key access" refers to UA functionality, I agree that there is no 
correlation.

WCAG 2.0 SC 2.2.1: one way of meeting this SC is providing a mechanism to 
turn off the time out, so UAAG CP 3.5 seems to fit here. I don't think that 
UAAG CP 5.1 fits here; I would correlate that to 3.2.1 (it already 
correlates to 3.2.2 in your table). I'm also not sure that that UAAG CP 
11.5 fits here.

WCAG 2.0 SC 2.2.2: UAAG CP 11.5: if blinking text fits the UAAG definition 
of animation, then the last bullet in #1 (the bullet that links to CP 4.5) 
correlates to this WCAG SC, but WCAG requires that the method to stop 
blinking is in the content. Does this mean that UAAG CP 11.5 extends WCAG 
2.0 SC 2.2.2?

WCAG 2.0 - Level 3 Success Criteria for Guideline 2.2: I'm also not sure 
that that UAAG CP 11.5 fits here. Possibly, UAAG CP 11.5 supports SC 2.2.5 
(cf. the UAAG CP 11.5 bullet point: "interrupt a request to load or reload 
a resource").

WCAG 2.0 SC 2.5.1: I don't understand why UAAG CP 5.5 would fit with SC 
2.5.2/2.5.3 but not with 2.5.1. I think UAAG CP 6.6 helps here, but I'm not 
sure if it is required in all circumstances.

WCAG 2.0 SC 2.5.1: I think UAAG CP 6.6 helps here, but I'm not sure if it 
is required in all circumstances.

WCAG 2.0 SC 4.1.1: one way to fail this is using markup that results in 
inconsistent DOMs in user agents, so this seems to correlate to UAAG CP 6.2.

I wonder if WCAG SC 3.2.1 and 3.2.5 correlate to UAAG CP 10.6, because if 
there is a change of viewport (which is included in the WCAG definition of 
change of context), it is important that the current viewport is highlighted.

Regards,

Christophe Strobbe

[1] http://lists.w3.org/Archives/Public/w3c-wai-gl/2006AprJun/0080.html


-- 
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 Tuesday, 25 April 2006 10:35:50 UTC