We mapped WCAG 1.0 checkpoints with "until user agents" clauses to WCAG 2.0 HTML Techniques and to UAAG 1.0 Test Suite test cases as part of creating a test plan to gather data to address both WCAG 1.0 errata and updating HTML Techniques for WCAG 1.0/2.0. We'll gather user agent and assistive technology support information to determine if we can deprecate some of the WCAG 1.0 checkpoints (that contain "until user agents") as well as deprecate some HTML Techniques in WCAG 2.0. If we don't deprecate, we can provide data as to how we made our decisions.
Related resources:
| WCAG 1.0 Checkpoint | HTML Techniques for WCAG 2.0 | UAAG Test Suite Test Cases | HTML Test Suite Test Cases |
|---|---|---|---|
| 1.5 Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map. [P3] | 11.3 Provide redundant text links for client side image map | repairing missing ALT conditional content for AREA | |
| 7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects. [P2] | 1.2 Meta redirect | META HTTP-EQUIV redirect | |
| 7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. [P2] | 1.3 Meta refresh | META HTTP-EQUIV refreshl | |
| 10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user. [P2] | 9.9 Anchors and targets | ||
| 10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned. [P2] | 14.4 Labeling form controls | no test case to determine if label/for is supported | |
| 10.3 Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns. [P3] | Have a variety of techniques for marking up tables. Have one technique to create a linear reading order (of layout tables). 8.3 Linear reading order of tables | test cases address table navigation. There are 8 tests cases for UAAG 1.0 Checkpoint 10.1. Here is a test case for UAAG 1.0 Checkpoint 9.9: | For this WCAG 1.0 checkpoint, we need to test that user agents appropriately read text in cells (I.e., that they don't blend content from neighboring cells) |
| 10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. [P3] | 14.5 Place-holding characters in empty controls (deprecated) | The issue was tabbing to and recognizing text areas. | |
| 10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. [P3] | No technique | No test case specific to determining if links in a row will be recognized separately. | |
| 13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. [P3] |
|
||
| 1.3 Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation. [P1] | Not in HTML techniques, in gateway | UAAG 1.0 Checkpoint 2.5. No test available. (Checkpoint 2.5 Make captions, transcripts, audio descriptions available ) | |
| 7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. [P1] | No HTML technique mentions flicker | No test available. | |
| 7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off). [P2] | No HTML technique mentions blinking (could be in images or css) | TEXT-DECORATION:BLINK in the STYLE element | |
| 7.3 Until user agents allow users to freeze moving content, avoid movement in pages. [P2] | No HTML Technique | UAAG 1.0 Checkpoint 2.5. No test available. (Checkpoint 4.5 Start, stop, pause, and navigate multimedia ) |
24 February 2004. Wendy Chisholm, Jenae Andershonis for the WCAG WG