Skip to
content
Translations
About RSS
Search[DRAFT - methodology for transition] Managing the transition from WCAG 1.0 to WCAG 2.0
Note: This document is a very rough initial concept draft only and should not be referenced or quoted under any circumstances.
$Date: 2006/08/03 [ changelog ]
Page Contents
Methodology for managing the transition from WCAG 1.0 to WCAG 2.0
This is a draft description of key stages needed when transitioning from WCAG 1.0 to WCAG 2.0 including key considerations and documents and resources to support each stage.
Benchmark site against WCAG 2.0
Before you can start managing the transition from WCAG 1.0 to 2.0 you need to establish how compliant your site is with the WCAG 2.0 guidelines. To do this:
- Establish technologies used in the site and test it against WCAG 2.0 guidelines - Review and list technologies currently used in the site. The site can then be assessed using the WCAG 2.0 quick reference document. This is a customisable reference document that lists all Success Criteria for testing against WCAG 2. The document itself can be customised so it only shows Success Criteria relevant to the technologies used in your website. Before testing the site customise the document according to technologies used in the site. As this is a benchmarking assessment this could be done to Level Success Criteria AAA. This makes it possible to see how how many Success Criteria are met overall. The results can then be sifted to see how far which WCAG 2.0 Level Success Criteria A, AA or AAA are met.
- Identify discrepancies between WCAG 1.0 and WCAG 2.0 to establish what the gaps are. This can be done by referencing the Comparison of WCAG 1.0 checkpoints to WCAG 2.0 against your website's assessment.
- @@
Set a baseline
Once you have established how compliant your site is against WCAG 2.0, what technologies are currently in use, are intended to be used etc you can then start to set a baseline- Decide who sets the baseline. This may be set by authors, organizations (including corporations, non-governmental or non-profit organizations), customers, or governmental bodies and is variable from site to site. Government websites for example may be set by Government, a commercial website mat set their own, a small website may have the baseline set by the page author. Advocacy groups may recommend baselines and be able to advise. About Baselines and WCAG 2.0 can help you
- Establish baseline technologies according to audience, industry etc..
- Ensure that your baseline is fair etc
- @@.
Decide conformance level
Based on the benchmarking of the site against WCAG 2.0 and technologies set in the Baseline decide can then decide your conformance level. etc
- risk assess (see what is achievable what should be done i.e. gov should do this) - etc
- decide date of claim and timelines - etc
- establish conformance level satisfied: Level A, AA or AAA
- reference the baseline
- decide scope of conformance claim
- Write a conformance statement for WCAG 2.0
- Can reference content created before the transition date that is WCAG 1.0 compliant i.e. "Material with creation or modification dates before December 2006 conform to WCAG 1.0..." [ref: "Conformance to WCAG 2.0" Content that conforms to WCAG 1.0 ]
- Conformance to Web Content Accessibility Guidelines 2.0 - this document gives guidance scoping and putting together a conformance claim.
- Comparison of WCAG 1.0 checkpoints to WCAG 2.0 - this mapping document can be used to establish what issues addressed in WCAG 1.0 are similar or different to WCAG 2.0.
Project plan
Based on technologies set in the baseline and conform level etc
- map out techniques to be used to meet each success criteria at levels 1, 2 and 3 according to technologies in the baseline
- who they are to be done by (developer, designer, content author etc)
- ensure resources and training are available
- establish an accessibility policy (includes, baseline reference accessibility policy
- establish timelines
- establish and document techniques to meet success criteria for your conformance claim
- set up a testing program
- @@
Implement changes
Maintain conformance
- ensure web material meets the success criteria of WCAG 2.0
- ensure conformance claims are valid
- review baseline and conformance claims at regular intervals
Documents and resources:
- WCAG 2.0 quick reference - customise the quick reference document according to technologies used in your baseline, success criteria
References
Notes
- [Open issue] In About baselines and WCAG 2.0 there is reference to a possible document to be written "A Guide for Policy Makers". Could this be somethinng that is included as part of this transitioning suite.