Default font size Decrease font size   |   Increase font size  |   Skip navigation

Introduction

Web Content Accessibility Guidelines (WCAG) are a set of guidelines which have been developed by interested parties from around the world in order, under the auspices of the W3C, to establish a standard for web content accessibility. They are essentially guidelines to provide a means for people with disabilities to more easily access web content. They are primarily aimed at web developers and designers.

Version 1.0 of the accessibility recommendation goes way back to 1999. This has since been superseded by version 2.0. Although web content may conform to either version, it is recommended that version 2.0 is adhered to.

Version 2.0 structure differs quite significantly from version 1.0. It now comprises several layers of guidance to meet the requirements of the different types of users. We now have overall principles, general guidelines, testable success criteria and a collection of sufficient and advisory techniques to assist in making web content accessible. W3C also provide documentation to help with the understanding of the guidelines and specific examples of how to develop accessible web content.

I should point out that blatant plagiarism is evident in this document. This is inevitable as the purpose of this document is to extract the salient points from W3C documentation in order to present it in a more condensed form for users. In addition to the formal specifications from the W3C, an attempt has been made to also provide a more user friendly explanation of the guidelines and techniques. Much of this text is courtesy of Global Alliance for Accessible Technologies and Environments (GAATES) and their document WCAG 2.0 - Web Content Accessibility Guidelines An Introductory Guide for Web Developers and also the book Web Content Accessibility Guidelines 2.0 made easy.

Top

Layers of Guidance

Principles

There are four principles under which the guidelines now fall. The following descriptions are taken from the document Introduction to Understanding WCAG 2.0 - Understanding the Four Principles of Accessibility

  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)

Guidelines

Previous guidelines have now been re-defined and applied to the four principles specified above. There are 12 guidelines in total and they provide the basic goals that authors should work toward and to provide the framework and overall objectives to help authors understand the success criteria and better implement the techniques. These guidelines are summarised below.

Success Criteria

For each guideline, testable success criteria are provided to allow WCAG 2.0 to be used where requirements and conformance testing are necessary such as in design specification and regulation. In order to meet the varying needs, three levels of conformance are defined from A(the lowest) through AA to AAA(the highest). For further reading see the W3C document Understanding Conformance - Understanding Levels of Conformance

The Success Criteria are numbered according to their principle and guideline. For example, Principle 1 has a Guideline 1.3 which has three Success Criteria; 1.3.1, 1.3.2 and 1.3.3.

Conformance levels

Sufficient and Advisory Techniques

A variety of techniques have been documented which enable the various accessibility requirements to be met. They fall into two categories, those that are sufficient for meeting the success criteria and those that are advisory. Advisory techniques go beyond what is required to meet the success level and allow authors to better address the guidelines. It should be noted that "sufficient" techniques are not mandatory and if a test fails this does not necessarily mean that the criterion has not been satisfied in another way. The techniques are divided up into specific technical areas e.g. HTML, CSS, Client-side scripting etc.

Each criterion may have multiple techniques applied to it. Each technique may apply to more than one criterion. Similarly a series of failures have been documented. These cover the situation where there is an error or techniques have been incorrectly or incompletely applied causing the criterion to fail. Each criterion has a series of associated failures and as with techniques, each failure may apply to more than one criterion.

See the W3C document Introduction to Understanding WCAG 2.0 - Sufficient and Advisory Techniques for further reading.

Common Failures

Although the bulk of the techniques required to meet the success criteria rely on valid well-formed HTML written to the W3C specification, this is often not the case with many sites. For one reason or another, inexperience, pure sloppiness etc., basic rules are ignored which lead to pages which are invalid or not to spec and thus made inaccessible not only to those using assitive technologies but even cause difficulties to those with a simple impairment such as color-blindness.

The technique pages show the most common errors even though it may be as simple as a missing end tag.

Please note that because there are many examples of non-conformance with the content in this document, this is often deliberate for demonstration purposes and as such it is not expected to pass validation by any accessibility tool.

Also please note that because of the nature of this document, part of which demonstrates bad techniques, some of the coding techniques used in this document, such as inline styles, are not considered to be best practices. In many cases they have been specifically used to demonstrate a particular technique or failure in the simplest way.

Top

How this website is structured

This website is organised into three groups, 'principle', 'guideline' and 'success criteria'. For each principle there is a page which lists its guidelines and the requirements for the conformance levels within that principle. There is another page for each principle which details the guidelines and their success criteria and for each guideline there are further pages which show techniques that can be used to achieve the success criteria and also common failures associated with the success criteria. Not every technique and failure is covered for each criterion as some are very similar or not appropriate (see next paragraph) but there is a link to the relevant W3C success criterion page which shows the full list of techniques and failures.

Please note that this document concentrates on HTML solutions and does not provide guidance for PDF documents, Flash Player or Silverlight issues and other video/audio technologies. The use of these technologies in business applications is rather limited and it is from the business application point of view that this documentation is directed.

Conventions used

In the Success Criterion pages, example code is shown with a pale yellow background and example output (rendered HTML) is shown with a white background. When these examples are used to demonstrate bad techniques or failures the background colour has a red border surrounding it.

In many of the pages, the examples are interactive. Using keyboard or mouse to interact with a form will produce an example of what is expected or in the case of a failure, what is not expected. As stated above, the coding techniques used to produce the results may not be what would normally be expected in developing a website, but are sufficient in these pages to demonstrate the techniques and failures.

Top

WCAG 2.0 Guideline List

The list below provides a quick reference to the WCAG 2.0 guidelines.

Principle - Perceivable

Text Alternatives
Guideline 1.1  Information and user interface components must be presentable to users in ways they can perceive.
Time-based Media
Guideline 1.2  Provide alternatives for time-based media.
Adaptable
Guideline 1.3  Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
Distinguishable
Guideline 1.4  Make it easier for users to see and hear content including separating foreground from background.

Principle - Operable

Keyboard Accessible
Guideline 2.1  Make all functionality available from a keyboard.
Enough Time
Guideline 2,2  Provide users enough time to read and use content.
Seizures
Guideline 2.3  Do not design content in a way that is known to cause seizures.
Navigable
Guideline 2.4  Provide ways to help users navigate, find content, and determine where they are.

Prinicple - Understandable

Readable
Guideline 3.1  Make text content readable and understandable.
Predictable
Guideline 3.2  Make Web pages appear and operate in predictable ways.
Input Assistance
Guideline 3.3  Help users avoid and correct mistakes.

Principle - Robust

Compatible
Guideline 4.1   Maximize compatibility with current and future user agents, including assistive technologies.
Top
Top