WCAG 1.0

One of the first things to learn is compliance with the Web Content Accessibility Guidelines version 1.0 (WCAG 1.0) does not equal accessibility. It indicates a high level of accessibility but you can break a number of guidelines and still pose relatively few problems for users with disabilities.

The second thing to learn is it's very difficult. Often pages start off compliant but as soon as pages start getting updated compliance starts going down. Editors move on and new ones come in and break compliance without realising.

The third thing to learn is WCAG 1.0 are soon to be replaced. Considering they were brought out in 1999 they still have a lot of relevance. However the emergence of standards compliant browers and improvements in assistive technology can no longer be ignored. The new guidelines (WCAG 2.0) attemtp to address these issues and others.

WCAG 1.0 have three levels which can be complied with: Priority 1,2 and 3 also known as A, AA and AAA. The latter level of compliance isn't possible by the way - this article explains why.

Priority 1

A Web content developer must satisfy checkpoints at this level. 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 checkpoints at this level. 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 checkpoints at this level. 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.

Feel free to contact us by filling in the form below. Alternatively, call us on 0151 223 0001 for a free no obligation chat.