Sample WAI Compliance Test Sheet
Scoring system
A Pass score indicates that no problems were found with this issue on the site.
A Near score indicates that a few problems were found on some pages, but in general the site complied with the guideline.
A Fail score indicates a serious problem with the relevant guideline throughout the site. This issue needs to be addressed as a priority.
Please note that the N/A score awarded for a particular technology that is not used on the site is the same as that awarded for a pass score. The assumption is that you have deliberately avoided using technology that might create a barrier.
Score sheet for http://www.examplesite.com
Date of test 23rd March 2006
| Score | General Requirements | See Note |
|---|---|---|
| Fail | 1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video. | 1 |
| Pass | 2.1 Ensure that all information conveyed with colour is also available without colour, for example from context or markup. | |
| N/A | 4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). | |
| Near | 6.1 Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document. | 2 |
| N/A | 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. | |
| Pass | 7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. | |
| Pass | 14.1 Use the clearest and simplest language appropriate for a site's content. | 3 |
| And if you use images and image maps | ||
| N/A | 1.2 Provide redundant text links for each active region of a server-side image map. | |
| N/A | 9.1 Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape. | |
| And if you use tables | ||
| Pass | 5.1 For data tables, identify row and column headers. | |
| N/A | 5.2 For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. | |
| And if you use frames | ||
| N/A | 12.1 Title each frame to facilitate frame identification and navigation. | |
| And if you use applets and scripts | ||
| Fail | 6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. | 4 |
| And if you use multimedia | ||
| Fail | 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. | 5 |
| N/A | 1.4 For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation. | |
| And if all else fails | ||
| 11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page. | ||
| Score for Priority 1 = 39 out of possible 48 |
Notes
- Many images use the word "image" as alternative text (alt tag). The alternative text should indicate what the image is showing - for example "picture of the mayor at the Womens Institute meeting". Automated software, such as Bobby, would not pick this up as they are unable to check if the actual text makes sense. However people with visual problems rely upon this text to explain why you have included the image.
- Technically your pages can be read without the linked style sheet. However it is very hard to follow long pages as you do not use the correct sub-heading codes (<H1> etc.) in your documents. Instead you use a style sheet that defines a class called ".sectionhead" and apply that to any normal paragraph that you want to be a section heading. Without the style sheet these headings become lost amongst the general text. The use of correct code for section headings is a Priority 2 issue so we have scored a near - but you should use the appropriate HTML code when it is available.
- The website is aimed at professional adults, so the complex sentence structure is acceptable.
- The use of Java script to produce "roll down" submenus beneath the main navigation buttons means that users without access to Java will not be able to find large sections of your website.
- The information videos in your services section should have links to the transcripts for deaf people to read, these are also useful for people whose speakers may not be working.