Requirements and Changelog for "Managing the transition from WCAG 1.0 to WCAG 2.0"
Page Contents
About "Managing the transition from WCAG 1.0 to 2.0"
Purpose
The purpose of the document is to:
- Reassure people
that WCAG 2.0
- it is an update, and not change from, WCAG 1.0
- the fundamental issues of Web accessibility are basically the same
- existing work (WCAG 1.0) is simply built upon and enhanced
- Define what web development, processes and practices are necessary to transition to WCAG 2.0
- Explain that WCAG 2.0 is more testable and applicable to non W3C technologies hence the change in glossary
- Provide a logical step by step guide for moving from WCAG 1.0 to WCAG 2.0
by
- describing a process, and the steps involved, when managing the move from WCAG 1.0 to WCAG 2.0
- possibly providing a flow chart to illustrate each step in relation to the next
- Reference WAI documents and tools that can be used at each stage
- Clarify the relationship between WCAG 2.0 documents.
Goals
The goals of this document are to answer common questions such as:
- Where do I start?
- Is previous work I have done to make my site WCAG 1.0 compliant valid?
- Will I need to start work all over again?
Objectives
To provide people who have been working towards WCAG 1.0 with the ability to:
- identify what needs to be done to move to WCAG 2, when, and by whom
- to benchmark their existing site against WCAG 2.0 and map out a project plan to help them meet the success criteria at chosen levels.
- to identify, prioritise and plan work needed to meet the required WCAG 2.0 conformance level.
Audience
The primary audience is people who already have an understanding of WCAG 1.0 and will be working to make their site meet WCAG 2.0 including project managers, web developers, designers, programmers and content authors. The secondary audience could be decision/policy makers, professional evaluators, trainers, managers and commercial organizations, government and nonprofit organizations who need an overview explanation.
Notes
- Size: possibly 2 documents. One a could be a more detailed document for the primary audience (see above) and the second a more top level document for teh secondary audience.
- Part of WCAG 2.0 Documentation Suite