All of the test files are available in a simple list. (Updated 2/22 with Ramp 6 stuff)
| # | Issue description | Total | Bo | IF | LM | Ra | WK | WX |
|---|---|---|---|---|---|---|---|---|
| 1 | Alt-Text. Every image element (IMG) must have an alt attribute. No alt-text (step-1-1-1-f) is an error and there should be no error when alt-text is present (step-1-1-1-s). | 6 |
1 |
1 |
1 |
1 |
1 |
1 |
| 2 | ASCII Art as Alt Text. If alt-text is "ASCII art", like alt="-->", a screen reader would speak "hyphen hyphen greater than" which is not meaningful alt-text. It is an error when alt-text consists of ASCII art (step-1-1-1-f2). | 2 |
0 |
0 |
0 |
1 |
1 |
0 |
| 3 | Object requires default content. An OBJECT element should have content which is available if the object/plug-in is not supported (step-1-1-2-s). Though this is a requirement of WCAG 1.0, it is not widely supported by assistive technology. A testing tool scores on this if there is no warning or error on the good file (step-1-1-2-s) and there is a warning or error on the bad one (step-1-1-2-f). | 5 |
1 |
1 |
1 |
0 |
1 |
1 |
| 4 | Image button. Every image button, that is INPUT element with type="image", must have alt-text that specifies the purpose of the button (step-1-1-4-s, step-1-1-4-f). | 5 |
1 |
1 |
1 |
1 |
1 |
0 |
| 5 | Long alt-text. Alt-text should be short, succint, and to the point. The question is "how long is too long?" I have chosen 151 characters (step-1-1-5-f) as the break-off point that should raise an error. There is also a file with 102 characters of alt text (step-1-1-5-f2) which I think should be an error too; none of the tools caught 102 characters as an error. | 6 |
1 |
1 |
1 |
1 |
1 |
1 |
| # | Issue | Total | B | IF | LM | Ra | WK | WX |
| 6 | Image map areas. Avery AREA element of a MAP for a client-side image map needs to have alt-text. The sample file (step-1-1-6-f) has one AREA that has no alt-text. For comparison, step-1-1-6-s has alt text on all the AREA elements. | 6 |
1 |
1 |
1 |
1 |
1 |
1 |
| 7 | Server-side image maps. I believe that a server side map (IMG with ismap attribute) should never be used, so any page with a server-side map should raise an error. There are two test files, one with the server-side map and no text links (step-1-2-f) and, just for interest, step-1-2-s is coded with text links provided for each server side hot spot. The tools score correct (1) on this if they raise an error or warning for the server-side map (on either or both files). | 6 |
1 |
1 |
1 |
1 |
1 |
1 |
| 8 | Frame titles. Each FRAME in a FRAMESET needs a title attribute indicating the prupose of the frame. In the sample file (step-12-1-f) the FRAME elements do not have title attributes. For comparison, step-12-1-s has adequate title attribures. | 6 |
1 |
1 |
1 |
1 |
1 |
1 |
| 9 | Quality of frame titles. The title attributes on the frames must be meaningful. Here (step-12-1-f2) the sample frames have title="top", title="left" and title="right" which are not meaningful - that is they do not specify the purpose of the frame. | 3 |
0 |
1 |
0 |
1 |
1 |
0 |
| 10 | Input Element needs label. The first form example (step-12-4-f) is just a text INPUT field (type="text") with neither a title attribute nor an associated LABEL element. This condition should raise an error. The same form using the LABEL element (step-12-4-s) is correct and should not raise the error. | 6 |
1 |
1 |
1 |
1 |
1 |
1 |
| # | Issue | Total | B | IF | LM | Ra | WK | WX |
| 11 | Use of title attribute for form control. Another way to explicitly specify prompting text for an text INPUT field is to use the title attibute on the input control. This is illustrated in step-12-4-s4. | 3 |
0 |
1 |
0 |
1 |
1 |
0 |
| 12 | Text intervenes between label and control. The text that is enclosed by the LABEL element does not have to be right next to the control. Here the LABEL element encloses text, but there is intervening text before the control is encountered. This file (step-12-4-s3) should not raise an error or warning. | 5 |
1 |
0 |
1 |
1 |
1 |
1 |
| 13 | Label text from two places. Not only does the labeling text not have to be adjacent; it can come from two places. It is perfectly legitimate to have two LABEL elements with the same for attribute which this file (step-12-4-s6) illustrates. Even though AT support for two labels is spotty at best, this should not be an error. I doubt that the tools even notice that there are two labels. | 6 |
1 |
1 |
1 |
1 |
1 |
1 |
| 14 | An invisible gif holds the prompting text. A common phenomenon on IBM.com is to use an invisible gif with alt-text as the label for the search form. This technique was introduced by IBM at a time when few tools recognized the title attribute (see #11 above). Although this technique (hack) is acceptable - it is not an error - the title attribute is much better (See chapter 8). The file, step-12-4-s5, uses an invisible gif with alt-text in the LABEL container. It should not raise an error. | 6 |
1 |
1 |
1 |
1 |
1 |
1 |
| 15 | Label that matches no control. This form example, step-12-4-f2 has a LABEL element, but the for attribute does not match any id. This is an error. | 6 |
1 |
1 |
1 |
1 |
1 |
1 |
| # | Issue | Total | B | IF | LM | Ra | WK | WX |
| 16 | Two input elements with same id. In this case (step-12-4-f3) there are two input elements with the same id. This is an error which, surprisingly, is only detected by one tool, The LIFT Machine. Not only is it an accessibility error; using the same id on any two elements is invalid HTML. | 3 |
0 |
0 |
1 |
1 |
1 |
0 |
| 17 | Textarea needs label or title. This file, step-12-4-f8, contains a textarea with no label element or title attribute. This test is just like #10 except for textarea instead of input with type="text". | 6 |
1 |
1 |
1 |
1 |
1 |
1 |
| 18 | Select menu needs label or title. This file, step-12-4-f9, contains a select menu with no label element or title attribute. Just like #10 except for select instead of input with type="text". | 6 |
1 |
1 |
1 |
1 |
1 |
1 |
| 19 | Inaccessible select menu. This file, step-12-4-f10, contains a select menu which is open (size="4") and which has an onChange event handler which opens a new page. This menu is not accessible because it cannot be operated with the keyboard. This is an error, but the tool scores here only if it does not flag step-12-4-s10 as an error. That file is the same except the select menu is not "open" (size="1") which can be handled from the keyboard using ALT+DownArrow then up and down arrows. | 2 |
0 |
0 |
0 |
1 |
1 |
0 |
| 20 | Empty label.This file (step-12-4-f11) has properly coded label element except that the contents of that label element is empty. This is an error. It is very surprising that none of the tools detected this error. | 3 |
0 |
0 |
0 |
1 |
1 |
1 |
| # | Issue | Total | B | IF | LM | Ra | WK | WX |
| 21 | Inadequate link text. Link text is "click here"; (step-13-1-1-f) an error. | 4 |
1 |
0 |
0 |
1 |
1 |
1 |
| 22 | Image link with empty alt-text. An extreme case of inadequate link text, an anchor containing only one image and that image has empty alt text, alt="" (step-13-1-1-f2). | 5 |
1 |
0 |
1 |
1 |
1 |
1 |
| 23 | Image link with spaces for alt-text. Very similar to number #22; this anchor element (a)contains just one img element and the alt-text on that is alt=" " (quote four-spaces quote), step-13-1-1-f3. | 5 |
1 |
0 |
1 |
1 |
1 |
1 |
| 24 | Link with empty alt-text but also text. This file, step-13-1-1-s2, is OK. In this commonly occurreing sitiation, there is in image in the anchor with alt="" but there is also text in the anchor. This file should pass, but a tool gets a score here only if it passes this file and fails #22. The issue here is distinguishing between empty link text and non-empty link text. | 4 |
0 |
0 |
1 |
1 |
1 |
1 |
| 25 | Link text; "click here" with title attributeThis file (step-13-1-1-s3) has an anchor element (A) containing exactly the text "click here" which is inadequate (see#21). But there is also a title attribute on the anchor which specifies the target. This is not an error. A tool scores here only if this file passes and #21 fails. | 2 |
0 |
0 |
0 |
1 |
1 |
0 |
| # | Issue | Total | B | IF | LM | Ra | WK | WX |
| 26 | Same link text, different targets. If two links have the same link text but different targets (href) then the links cannot be distinguished in a list of links. This file, step-13-1-2-f, has two links with the same text but different href. It is an error. | 6 |
1 |
1 |
1 |
1 |
1 |
1 |
| 27 | Page title. The contents of the TITLE element on a page is what appears in the title bar of the browser and it is spoken by a screen reader. Every page should have a non-empty TITLE element. This file, step-13-2-f, has no TITLE element which is an error. | 4 |
1 |
0 |
1 |
1 |
0 |
1 |
| 28 | Inadequate page title. Similar to #27, but here the TITLE is "Title", i.e, the code looks like this: <TITLE>Title</TITLE>. The file, step-13-2-f2, should raise an error. | 2 |
0 |
0 |
0 |
1 |
1 |
0 |
| 29 | Skip link. The files both have links at the top followed by text. The file that fails has neither headings nor a skip link after the "navigation links." The file that is OK has a skip link. A tool scores on this test if it raises an appropriate error on step-15-2-f and does not raise that error on (step-15-2-s2) . | 3 |
0 |
1 |
1 |
1 |
0 |
0 |
| 30 | Heading for skipping to conent. This is exactly like #29 except the successful file (step-15-2-s) has headings, especially a level 1 heading at the beginning of the main content. I was disappointed that none of the tools (that were looking for skip techniques at all) recognized headings as such a tecnique. I hope this will change. | 1 |
0 |
0 |
0 |
1 |
0 |
0 |
| # | Issue | Total | B | IF | LM | Ra | WK | WX |
| 31 | Layout table that won't resize. When a layout table uses pixel widths it won't resize with either a larger window or larger text. This file (step-3-4-f) uses fixed widths in pixels. The response by the tool needs to be compared with that for a file, step-3-4-s, which uses percentage widths instead of pixel widths. | 6 |
1 |
1 |
1 |
1 |
1 |
1 |
| 32 | Data tables. The issue I wanted to check was (1) whether the tools checked for data tables - distinguishing from layout tables. The data table (step-5-1-s) is quite obviously such and marked up properly. A tools scores here is there is no data table error or warning on the good table or on the layout table (step-5-1-s3) and a table markup warning or error on the one with no use of TH (step-5-1-f). | 4 |
0 |
1 |
1 |
1 |
1 |
0 |
| 33 | Layout table with a summary. It is an error to have a layout table (step-5-1-f3) which has a summary attribute and TH markup. | 2 |
1 |
0 |
0 |
1 |
0 |
0 |
| 34 | Frame source must be HTML.. Here (step-6-2-f) is a frame page (FRAMESET) in which the first FRAME directly references an image (gif). The src attributes of FRAME must be an HTML page. | 5 |
1 |
1 |
0 |
1 |
1 |
1 |
| 35 | Blink element. Here's a file, step-7-2-f, that uses the BLINK element. This is an error because of blinking text; also because of depricated elements. | 6 |
1 |
1 |
1 |
1 |
1 |
1 |
| # | Issue | Total | B | IF | LM | Ra | WK | WX |
| 36 | Marquee element. Here's a file, step-7-3-f, that uses the MARQUEE element. Like #35, this is an error because text is moving and bacause the MARQUEE element is depricated. | 6 |
1 |
1 |
1 |
1 |
1 |
1 |
| 37 | Auto refresh. This page (step-7-4-f) has an auto refresh every 6 seconds, an error. | 4 |
1 |
0 |
1 |
1 |
1 |
0 |
| 38 | Keyboard access. The issue with this file, step-9-3-f, is keyboard acces. It contains a JavaScript function that requires a double click (onDoubleclick) and it doesn't work from the keyboard. A tool scored here if it raises a scripting error on this file (no keyboad access) but not on step-9-3-s where onKeyDown is used for the same function. | 1 |
1 |
0 |
0 |
0 |
0 |
0 |
| 39 | Structure of headings markup. WCAG suggests that headings should be used according to specification. There are two files for testing the use of headings. The correct one, step-3-5-s, has these headings (in order) H1, H2, H2, H3, H1. The error file, step-3-5-f, has H4, H1, H2, H5, H1. There are two herror here, the transition H4 (starting) to H1, and H2 followed by H5. The use of headings is so important for page navigation, errors like this are not very important in my opinion. | 4 |
1 |
1 |
0 |
1 |
0 |
1 |
| 40 | Title for in-line frame. This is another Frame issue - an IFRAME without a title attribute - step-12-1-f3. It is quite surprising how manytools fail on this even though they pass #8. | 5 |
1 |
0 |
1 |
1 |
1 |
1 |
| Totals | Maximum possible score is 40. | 28 |
23 |
27 |
38 |
34 |
26 |
|
| # | Issue | Total | B | IF | LM | Ra | WK | WX |