The five year strategy proposes that all government websites will be WCAG 2.0 compliant to Level A by 2012 and Double AA three years later.

Details of the Australian Government’s move to provide websites with accessibility in mind can be found on their website:

http://webpublishing.agimo.gov.au/Accessibility

Although adoption of the web accessibility standards has been pretty slow going, awareness in WCAG 2.0 is increasing and the guidelines are starting to make their way into web policy making.

One of the first governments to embrace W3C accessibility was New Zealand. In March 2009 they adopted WCAG 2.0 as a government accessibility standard (Level AA).

With governments in India, the UK, Canada and Australia following this trend in migrating from WCAG 1.0, we should see an increase in web design accessibility.

To celebrate WCAG 2.0’s first anniversary, accessibleweb will be conducting a review of each component of the web accessibility guidelines within the Perceivable, Operable, Understandable and Robust sections.

The new guidelines are divided into 4 main sections:

1. Perceivable
2. Operable
3. Understandable
4. Robust

Below is a very brief summary of what is included within the 4 WCAG sections.

WCAG 2.0

1. Perceivable
Web content can be seen and heard

• 1.1 Text alternatives – Alt text for images, labels for form controls, identification of embedded multimedia.
• 1.2 Time-based Media – Transcript of online audio files (MP3s and podcasts), transcript for web video.  Captions for multimedia files.
• 1.3 Adaptable – Correct use of headings, tables and lists in the HTML code. Flexibility to change page layout without damaging it’s structure.
• 1.4 Distinguishable – Contrasting foreground and background colours. Colour is not used as the sole mechanism for displaying content or interaction.

2. Operable
The page is operable

• 2.1 Keyboard accessible – The web page can be used via the keyboard
• 2.2 Enough time – Users have the ability to pause or cancel time based interactions.
• 2.3 Seizures – No flashing components that may cause a seizure
• 2.4 Navigable – Skip navigation option, descriptive page titles, clear link text meaning

3. Understandable
Page content and interface understandable

• 3.1 Readable – Correct use of the html lang attribute and abbr tag.
• 3.2 Predictable – Consistent navigation, no major page events (such as pop ups) on changes to focus or interaction
• 3.3 Input assistance – Identify required fields in a controls label, provide cues or error alerts.

4. Robust
Can be used by multiple browsers or devices

• 4.1 Compatible – Validate the pages

Call for Review: WCAG 2.0 Last Call Working Draft
http://lists.w3.org/Archives/Public/w3c-wai-ig/2007OctDec/0060.html

This is the second time the document process has reached the Last Call Working Draft stage. The new deadline for comments is February 2008 and will deal with the following points:

• Are the guidelines and Success Criteria clear?
• Are the Success Criteria implementable and testable?
• Does meeting the Success Criteria improve accessibility?

The successful completion of this step will result in the document process reaching the Candidate Recommendation stage.

When will WCAG 2.0 be available to use? The Web Accessibility Initiative predicts early 2008.

It had looked as though WCAG 2.0 would be available this year. However, with delays brought on by the W3C document process, the availability of the document has been pushed back.

 The W3C document process comprises a number of stages:

1. Working Draft
2. Last Call Working Draft
3. Candidate Recommendation
4. Proposed Recommendation
5. W3C Recommendation (Web Standard)

In addition to WCAG 2.0, a number of supporting documents are produced, such as “Working group notes” and “WAI Resources”.

Although the supporting documents are not subject to the scrutiny of the W3C document process, they will offer developers the technical know-how required to provide accessible content.

For developers, some positive observations include the reduction of constraints faced whilst creating accessible content. The provision of support materials will also be welcomed.

For people with disabilities, access to a broader range of web technologies is promised.

Interview extracts are available from the webstandards.org website.