This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1083 - Deprecation in case of WCAG 1.0/WCAG 2.0
Summary: Deprecation in case of WCAG 1.0/WCAG 2.0
Status: RESOLVED REMIND
Alias: None
Product: QA
Classification: Unclassified
Component: QASpec-GL (show other bugs)
Version: LC-2004-11-22
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Karl Dubost
QA Contact: Karl Dubost
URL: http://lists.w3.org/Archives/Public/w...
Whiteboard:
Keywords: LC, SpecGL
Depends on:
Blocks:
 
Reported: 2005-02-07 15:40 UTC by Karl Dubost
Modified: 2005-04-28 11:53 UTC (History)
0 users

See Also:

Attachments

Description Karl Dubost 2005-02-07 15:40:26 UTC 
[[[
About section: 4.4 Requirement A - "deprecated features"
Does "Mapping Between WCAG 1.0 and the WCAG 2.0 Working Draft" [2]
satisfy this requirement? Some of the WCAG 1.0 Checkpoints have evolved
into WCAG 2.0 Techniques while others are likely to be deprecated.
However, because the style is so different between WCAG 1.0 and WCAG
2.0, we are not able to include WCAG 1.0 Checkpoints directly in WCAG
2.0 in a way that makes sense and would allow us to mark them as
deprecated (in the WCAG 2.0 spec).
[2] <http://www.w3.org/WAI/GL/2004/11/19-mapping.html
]]]
Comment 1 Dominique Hazael-Massieux 2005-04-08 08:08:43 UTC 
Documents are very different and mapping between the two is neither easy nor
direct. One possibility is to declare 2.0 as a new document and not a revision
of 1.0. This avoids the issue. Think this mapping may be difficult but important
that people know the evolution of a feature. Suggest there be an appendix with
the mapping, showing and explaining the evolution. Use whatever format works.
Comment 2 Dominique Hazael-Massieux 2005-04-28 11:53:50 UTC 
setting version to LC in case of future use