The Web Content Accessibility Guidelines (WCAG) Working Group is excited to announce the publication of WCAG 2.0 as a W3C Candidate Recommendation on 30 April. WCAG 2.0 explains how to make Web sites, applications, and other content accessible to people with disabilities, and many elderly users.

Candidate Recommendation (CR) is a major step in the W3C standards development process; it signals that there is broad consensus in the Working Group and among public reviewers on the technical content of WCAG 2.0. The W3C Process stages are described in How WAI Develops Accessibility Guidelines through the W3C Process.

The primary purpose of this CR stage is for developers and designers to “test drive” WCAG 2.0 to demonstrate that WCAG 2.0 can be implemented in Web sites. WAI encourages a broad range of Web sites and Web applications to use WCAG 2.0 at this stage, and share implementation experience. For information on submitting your implementations, see WCAG 2.0 Candidate Recommendation Implementation Information

If you plan to provide implementations, please let us know your intentions by 23 May 2008.
Actual implementations are due by 30 June 2008.

It is important to note that some WCAG 2.0 requirements are at risk; that is, they may not be included if there are not sufficient implementations. Items at risk are listed under “Items at Risk” in WCAG 2.0.

While the focus of this stage is to collect implementations, the comment form and email address are still available from Instructions for Commenting on WCAG 2.0 Documents.

The different WCAG 2.0 documents that the WCAG Working Group updated with this publication are introduced in Overview of Web Content Accessibility Guidelines (WCAG) 2.0 Documents.

A key tool for using WCAG 2.0 documents, which was previously called the “Quick Reference”, is:
How to Meet WCAG 2.0: A customizable quick reference to WCAG 2.0 requirements.

For more information about the Candidate Recommendation status of WCAG 2.0 and the changes since the last publication, see “Status of this Document” section of WCAG 2.0

WCAG 2.0 is part of a series of accessibility guidelines/standards developed by WAI, which are listed in WAI Guidelines and Techniques

WebAnywhere is a web-based screen reader. It requires no special software to be installed on the client machine and, therefore, enables blind people to access the web from any computer they happen to have access to that has a sound card.

All you need to do is switch a PC on, plug in your headphones, execute a couple of keyboard commands so that you open up the WebAnywhere home page, switch it on and away you go. What sets WebAnywhere apart from other text-to-speech software, free or otherwise, is that it can be used on any website rather than only sites where that software is installed.

This is fantastic on so many levels:

• Enables people who can’t afford costly screen readers to access the web
• Enables people with slight sight problems who don’t yet use a screen reader but may want audio support to have it
• You can use it on other PC’s and laptops if you’re traveling or unable to access your own i.e in libraries, schools and colleges
• Enables people with reading problems to get reading and audio support
• People browsing in a second language can use it to help understand written text
• Is an additional tool in the web developers toolbox when testing websites for accessibility

The software is also open source which is a huge bonus.

Visit their site to see WebAnywhere being demo’ed.

The conference will focus on web accessibility in the Web 2.0 world. So if you’re involved in the development of social networking portals, sites using Ajax or rich in user generated content, it really should be in your diary.

AbilityNet have brought together an impressive line-up of experts on a wide range of issues that keep raising their heads whenever the words Accessibility and Web 2.0 crop up in the same sentence. The conference promises practical solutions to the Web 2.0 accessibility problems, showing cutting edge techniques and offering realistic solutions.

The Accessibility 2.0 web site, has full information on the schedule and how to book online. See you there!

The tool is essentially your regular Google instant messaging box but with translation support added so you can have text translated on the fly. It works using ARIA and the AxsJAX library together with Google Translate.

To start using this all you need to do is add a translation feauture as a friend and chat as normal. When you send text it will appear in the original as well as the translate language. The ARIA support then allows the translated text to be read out loud by screen readers.

There are roughly 25 languages supported distinguished by their own two letter identifier in an email address. If you want to try it in Chinese, just add en2zh@bot.talk.google.com as a friend in Google Talk and send it a message to translate from English to Chinese. If you want to chat with someone you then just add them to the conversation and away you go.

You’ll also have in-depth knowledge of HTML and CSS and will be comfortable discussing finer coding issues with website developers as well as being experienced accessibility specialists with expertise in providing accessibility consultancy
services to blue chip organisations. You’ll carry out accessibility audits and deliver reports for clients, provide first line support and answer general technical queries about web accessibility, keeping abreast of relevant trends and developments.

To find out more and apply (quote 4711) or email recruitment@rnib.org.uk or call 020 7391 2363.
Closing date: 17 April 2008.

Committed to diversity. Reg. Charity No. 226227.

He was an inspiration to all of us here and will be missed.

I’ll be headed over to Beijing in April for the W4A and WWW2008 conferences where I’ll be speaking about the cross over between mobile and web accessibility. If you’re going to be there come by and say hi.

Read about and download the Chinese Web Accessibility Toolbar.

The focus of the session was to walk blind and partially sighted users through how to blog using Wordpress, use Twitter, Facebook and what poscasting tools there were out there. It was a really well thought out presentation which was written up in a Wordpress blog together with tools, resources and links. This was made all the better as everyone was sat at a laptop or PC all of which had a screen reader running.

Twitter was the area Mika seemed most excited about and talked the most in depth about. In fact his enthusiasm was such that when he asked how many people in the room used Twitter only two said yes. By the end of the session people were signing up and following his feed.

Most social networking sites have a way to go to make them truly accessible to all users with disabilities but it is great to see people taking advantage of these tools as far as they canm and Mika’s resources are a great place to start if you want to get into it. I’m a true believer in signing up to Facebook, Twitter and blogging in order to spread the word about web accessibility as well as keep up to date with what is going on.

Join us on Facebook and Twitter and follow news soundbites as well as updates on what we are up to.

It was fascinating to learn about what is happening in India with regards to web accessibility and talk to different people, learn what the drivers are and what needs to be done to promote accessibility. As an invited guest blogger on the UN Global Initiative for Inclusive ICT (G3ICT) I pulled these thoughts into an article. This, I hope, will be the first of a series of articles looking at web accessibility in various locales. Next will be China as I’ll be speaking about the cross over between web and mobile accessibility at the WWW 2008 Conference and gathering information there in April.

Read Putting accessibility to information centre stage in India

ATAG defines how authoring tools should help Web developers produce Web content that is accessible and conforms to the Web Content Accessibility Guidelines; it also defines how to make authoring tools accessible so that people with disabilities can use the tools. ATAG is introduced in the ATAG Overview

ATAG is part of a series of accessibility guidelines/standards developed by WAI, which are listed in
WAI Guidelines and Techniques

WAI encourages you to review the update ATAG 2.0 documents and submit comments on any issues that you think could present a barrier to future adoption and implementation of ATAG 2.0. Please send comments by 14 April 2008 to the comment list, which is publicly archived.

Please read, and comment. These guidelines are just as important as the Web Content Accessibility Guidelines.