What’s good in WCAG 2.0
The latest version of web content accessibility guidelines 2.0 (WCAG 2.0) are divided into 4 principles – Perceivable, Operable, Understandable and Robust (POUR) respectively. Each principle is divided into guidelines with priority levels A, AA, AAA.  The WCAG 1.0 has 14 guidelines but are not divided into blocks. This has been taken care in WCAG 2.0 in the form of principles. The explanations of the checkpoints are given in separate hyperlinks.

Important Issues in WCAG 2.0:

1.  Tables:
Tables are one of the most widely used attributes in HTML and they do create problems in the accessibility of the web page. Even though tables are not used for the visual layout in the recent era ,they are used to present the important data in a tabular form.  WCAG 2.0 provides no information about tables and the ways in which they can be used whereas WCAG 1.0 guideline 5  entirely speaks about HTML tables.

2.  Users of older browsers and turn-off features:
WCAG 2.0 includes the turn-off feature for the ones who use older browsers that do not support images, java script and so many new features.

3.  Auto refreshing and auto redirecting:
The features such as auto refreshing, auto redirecting and causing pop-ups create problems for visually impaired users who can be both low vision and screen reader users. These features are explained clearly in check points 7.4 & 7.5 in WCAG 1.0 but were not defined in WCAG 2.0.

4.  Usage of deprecated features of HTML:
WCAG 2.0 does not contain any information about deprecated features of HTML,  that cannot be used as per WCAG 1.0.

5.  Usage of frames:
The usage of frames is clearly explained in checkpoints 12.1 & 12.2 of WCAG 1.0 but were left unexplained in the latest version of WCAG.

6.  Usage of style sheets:
Nowadays, most of the web designers are using CSS for visual lay out of the web pages. WCAG 2.0 do not contain any relevant information about the usage of style sheets.

7. Usage of HTML doc type:
There are no guidelines about doc type declaration in WCAG 2.0 where as WCAG 1.0 has it explained. The latest version did not focus much on the alidation of HTML and its perfect usage.

New issues brought in by WCAG 2.0:

1.  Usage of links in meaningful sequence:
WCAG 2.0 guidelines 1.3.2 defines that the links should be presented in meaningful sequence so that the user can use the track to find the required information easily. In the checkpoint 1.3.2 it is given that any audio or video should not play continuously for more than 3 seconds, if it plays the user has to be given an option to pause or stop, or at least have a mechanism to reduce the volume without changing the over all system volume.

2.  Input errors:
This is one of the issue, where WCAG 1.0 didn’t focus  much, but it does have a vital role in web pages. This was nicely explained in the guideline 3.3 of latest version.

Some more issues raised by WCAG 2.0 are:
1.  Foreground and background colors selected by the user.
2.  Width should not be more than 80 characters or glyphs (40 if CJK).
3.  Text is not justified (aligned to both the left and the right margins).
4.  Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing.
5.  Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window.

Comments

comments