Museo&Web

Planning Kit for a Quality Site for Small and Medium Sized Museums

wp5 logo
vai al contenuto

You are in: Home - Tutorial - Accessibility - The Web Accessibility Initiative (WAI)

The Web Accessibility Initiative (WAI)

From the Handbook for quality in cultural Web sites Improving quality for citizens, paragraph 2.2.3:

The Web Content Accessibility Guidelines of the WAI project are constantly referred to in the search for quality accessibility in a Web site.


The WAI project deals with Web accessibility in the lay sense; that is, not only as far as regards contents, but also in terms of the tools used to realise the Web pages, the browser and, more generically, technologies for Web access. For example, for this purpose, all the images in a site "must provide text equivalents for images and other multimedia content", and "non-text equivalents of text (e.g., icons, pre-recorded speech, or a video of a person translating the text into sign language) can make documents accessible to people who may have difficulty accessing written text, including many individuals with cognitive disabilities, learning disabilities, and deafness".

 

The Web Content Accessibility Guidelines (WCAG) version 1.0, 5 May 1999, is particularly important for accessibility of content.

The document consists of 14 GuideLines. Each of these presents typical situation that could present difficulties for disabled users. In every Guide Line a certain number of checkpoints are defined and explain the specific way the guide can be applied to developing content. The Guidelines introduce the concept of priority and thence the concept of conformity. These concepts are thus defined by the WCAG:

“Each checkpoint has a priority level assigned by the Working Group based on the checkpoint's impact on accessibility.
[Priority 1]

A Web content developer ‘must’ satisfy this checkpoint. Otherwise, one or more groups will find it impossible to access information in the document. Satisfying this checkpoint is a basic requirement for some groups to be able to use Web documents.
[Priority 2]

A Web content developer ‘should’ satisfy this checkpoint. Otherwise, one or more groups will find it difficult to access information in the document. Satisfying this checkpoint will remove significant barriers to accessing Web documents.
[Priority 3]

A Web content developer ‘may’ address this checkpoint. Otherwise, one or more groups will find it somewhat difficult to access information in the document. Satisfying this checkpoint will improve access to Web documents.

Some checkpoints specify a priority level that may change under certain (indicated) conditions.

Respect of the above points leads to the concept of conformity:

Conformance Level "A":
all Priority 1 checkpoints are satisfied;

Conformance Level "Double-A":
all Priority 1 and 2 checkpoints are satisfied;

Conformance Level "Triple-A":
all Priority 1, 2, and 3 checkpoints are satisfied.

Various tools for evaluation of the accessibility of Web contents are commercially available. These automatic tools are not alone sufficient to guarantee conformity to the degree of accessibility required. Indeed, many guidelines require a degree of subjective evaluation that no automatic tool can supply.

Useful Resources

© Minerva Project 2005-02, last revision 2006-03-23, edited by WP5, Committee for the development of a prototype of public cultural websites.
URL: www.minervaeurope/structure/workinggroups/userneeds/prototipo/progproto/accessibilita/wai_e.html