They are finally released, the Web Content Accessibility Guidelines version 2.0 (WCAG 2.0) are now published, after many years in the making. Out-Law describes them as the “de facto standard”. Despite many changes in web technology and how the use of the web is now common place, this is actually the first update of the guidelines since 1999.

The guidelines are now based around four principles:

1. Perceivable - Information and user interface components must be presentable to users in ways they can perceive.

   • This means that users must be able to perceive the information being presented (it can’t be invisible to all of their senses)

2. Operable - User interface components and navigation must be operable.

   • This means that users must be able to operate the interface (the interface cannot require interaction that a user cannot perform)

3. Understandable - Information and the operation of user interface must be understandable.

   • This means that users must be able to understand the information as well as the operation of the user interface (the content or operation cannot be beyond their understanding)

4. Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

   • This means that users must be able to access the content as technologies advance (as technologies and user agents evolve, the content should remain accessible)

From Introduction to Understanding WCAG 2.0.

From each of these guidelines extend out the techniques and advice that web developers should follow when wanting to make their websites more accessible for users with disabilities.

Unlike the version 1.0 guidelines the new guidelines are meant to establish principles that will remain irrespective of changes to the technology. So for example it shouldn’t matter that touch screen interfaces are becoming increasingly popular (especially on mobile devices), because the principle of operability applies irrespective of the interface.

Will they work?

Only time will tell if the new guidelines will help ensure that the web becomes accessible for all. Many countries have had to introduce legislation because the needs of disable users were being ignored by so many web developers. In the UK this is now been taken further with the development of a British Standard designed to build on the PAS 78 - Guide to Good Practice in Commissioning Accessible Websites. The PAS 78 document relied heavily on WCAG 1.0 so it would be surprising to see the emerging standard not make strong use of its successor.

Many companies now include ‘accessibility’ as a requirement in contracted web work but there is much confusion about what this actually means and there remains a lot of misunderstanding about where accessibility should be applied. For some companies, accessibility has been reduced to a series of technical tests based on some of WCAG 1.0, passing those tests they assume they are ‘accessible’. However, this may not be the case, there is much in WCAG 1.0 and in the new guidelines that cannot be tested automatically and many of the champions of the guidelines would not encourage their use as the be all and end of accessibility.

The Continuing Problem?

So WCAG 1.0 left the web with a problem - with no guidelines web developers who did not understand the problems of the disabled had no guidance on development but the establishment of guidelines for so many became the end itself. It didn’t actually matter if the websites met disabled or other needs so long as it passed ‘the WCAG test’. This risk remains with the new guidelines. One of the problems with reducing accessibility to series of technical tests is that it leaves the users out. There are a wide range of disabilities which can be hampered by poor application of some ‘accessibility techniques’ with no understanding of the human need that led to their creation in the first place.

Can we really have accessibility for all?

The new WCAG guidelines come at a time of another shift in the web landscape. Increasingly we are not using the web on desktop and laptop computers but on Internet Tablets (e.g. Ipod Touch), mobile phones, games consoles and many other devices. This era of web convergence makes the new guidelines even more timely. Disabled users will also be using these devices and developers will need to take this into account.

Ultimately legislation and guidelines themselves cannot make a better web for disabled users. That can only come as more companies providing web services want to provide a better experience for their users, whatever their abilities and means of access. Accessibility makes good business sense - after-all why shut yourself off from a market? In the current economic climate is your company making sure that your web services are working as hard as they can and available anywhere and everywhere your customers are?

About This Post

• Written by Stuart Smith
• December 22nd, 2008 at 3:04 pm