Transition from WCAG 1 to WCAG 2: issue summary


Gregg asked me to look at issues related to the transition from WCAG 1 to 
WCAG 2 while updating the mapping.

Issue 393: Migrating from WCAG 1.0 to WCAG 2.0

The original comment and edditional comments #1, #2 and #7 are addressed by 
the mapping, but additional materials would be welcome.
Additional comment #6 request "a formal process for migration". Is this a 
task for WCAG or EO?
Additional comment #3 is addressed by the mapping and by the WCAG 2.0 
checklist (appendix B).
Additional comment #5 is more general than the mapping; not sure if this 
requires a response or action.

Action: leave open until decision about additional materials.

Issue 502: ease of transition to 2.0

Request for information for developers with different levels of experience 
(new/little experience; experienced; extensive experience), triggered by an 
example for 2.5 that seemed to require extensive programing experience. 
However, this search engine example is not listed under 2.5 in 
Understanding WCAG 2.0, so part of this is overcome by events.

Action: decide if we well develop materials for developers with different 
levels of experience, then close.

Issue 505: ease of implementation of WCAG 2.0

The reviewer thinks that migration will be difficult in the absence of 
technology-specific checklists, so there could be
widely disparate views of what constitutes conformance.

Action: close with comment: Techniques documents will contain 
technology-specific information and failures, to help developers and 
evaluators. Every attempt has been made to make WCAG 2.0 success criteria 
as accurate as possible.

Issue 835: need for mapping that describes migration from 1.0 to 2.0

Action: close with comment: A mapping will be provided as a standard part 
of the guidelines (in an appendix).

Issue 978: Editorial comments on Appendix C

These refer to an old draft (2004).

Action: close: overcome by events.

Issue 1014: Questions about process and differences between versions

Action: close with comment already in Bugzilla.

Issue Issue 1144: WCAG 2.0 and frames

One reviewer refers to JIS X 8341-3 and usability problems of frames.
Another reviewer asks if WCAG 2.0 will take XFrames into account, as that 
specification will solve some of the known problems with frames.

Note: XFrames was scheduled to go to Last Call in January 2006 but didn't. 
See the HTML Working Group Roadmap at
Action: close with comment: Understanding WCAG 2.0 and the mapping document 
address this issue.

Issue 1178: Request for strategies for making transition from WCAG1 to WCAG2

Request for "additional material, containing recommended strategies and 
best practices for organizations making the transition to WCAG 2.0 

Action: leave open. This is only partly addressed by the mapping.

Issue 1484: Client side vs. server side image maps

WCAG 1.0 checkpoint 9.1 required that client side image maps be used except 
where the regions cannot be defined with an available geometric shape. We 
need to provide guidance to authors on migrating from WCAG 1.0 to 2.0 

The mapping document notes that server-side image maps are not keyboard 
accessible. However, every geometric region can be defined with a geometric 
shape because client-side image map areas can be polygons (and if every 
co-ordinate is meaningful,  single-pixel "areas" can be created with 
circles with radius 0, which, of course, leads to an unusable number of areas).
I don't know how to solve this issue. Any thoughts?



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 


Received on Wednesday, 5 April 2006 17:21:40 UTC