Validation report Validation reportPage: http://bkdelong.mit.edu/browsertests/imagegallery/
Author: chaals <charles@sidar.org>
| Checkpoint | Result |
|---|---|
| Point 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. [Priority 1] | Partial There is something there, but in the gallery pages the alt equals the caption (unnecesasry redundancy) and there is no longdesc which there ought to be for a gallery. |
| Point 1.2 Provide redundant text links for each active region of a server-side image map. [Priority 1] | Not applicable |
| Point 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. [Priority 1] | Not applicable |
| Point 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. [Priority 1] | Not applicable |
| Point 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. [Priority 3] | Not applicable |
| Point 2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup. [Priority 1] | Not applicable No information is conveyed by colour in the first place --CMN |
| Point 2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen. [Priority 2 for images, Priority 3 for text]. | Yes Just. Grey text looks cool but is painful to read. It generally can be done though. |
| Point 3.1 When an appropriate markup language exists, use markup rather than images to convey information. [Priority 2] | Yes |
| Point 3.2 Create documents that validate to published formal grammars. [Priority 2] | Yes Valid HTML 4.01 - W3C Validator, Valid CSS without warnings - W3C CSS validator. |
| Point 3.3 Use style sheets to control layout and presentation. [Priority 2] | Yes Interesting idea to decide that the thumbnails are a collection of listed items... --CMN |
| Point 3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values. [Priority 2] | No Unless you accept a legalistic interpretation of the checkpoint that is known not to have been what the working group intended at the time. --CMN |
| Point 3.5 Use header elements to convey document structure and use them according to specification. [Priority 2] | No Although this could be not applicable. I am not really sure --CMN |
| Point 3.6 Mark up lists and list items properly. [Priority 2] | Cannot tell Interesting call to use lists, and to break them into a number of them. I am not sure that this makes sense semantically. But then, HTML deprecated menu which would have made sense semantically. --CMN |
| Point 3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation. [Priority 2] | Not applicable |
| Point 4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). [Priority 1] | Not applicable |
| Point 4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs. [Priority 3] | Not applicable |
| Point 4.3 Identify the primary natural language of a document. [Priority 3] | Yes |
| Point 5.1 For data tables, identify row and column headers. [Priority 1] | Not applicable |
| Point 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. [Priority 1] | Not applicable |
| Point 5.3 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version). [Priority 2] | Not applicable |
| Point 5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting. [Priority 2] | Not applicable |
| Point 5.5 Provide summaries for tables. [Priority 3] | Not applicable |
| Point 5.6 Provide abbreviations for header labels. [Priority 3] | Not applicable |
| Point 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. [Priority 1] | Yes |
| Point 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. [Priority 1] | Not applicable |
| Point 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. [Priority 1] | Yes |
| Point 6.4 For scripts and applets, ensure that event handlers are input device-independent. [Priority 2] | Not applicable |
| Point 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. [Priority 2] | Not applicable |
| Point 7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. [Priority 1] | Yes |
| Point 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). [Priority 2] | Yes |
| Point 7.3 Until user agents allow users to freeze moving content, avoid movement in pages. [Priority 2] | Yes |
| Point 7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. [Priority 2] | Yes |
| Point 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. [Priority 2] | Not applicable |
| Point 8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies. [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.] | Not applicable |
| Point 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. [Priority 1] | Not applicable |
| Point 9.2 Ensure that any element that has its own interface can be operated in a device-independent manner. [Priority 2] | Not applicable |
| Point 9.3 For scripts, specify logical event handlers rather than device-dependent event handlers. [Priority 2] | Not applicable |
| Point 9.4 Create a logical tab order through links, form controls, and objects. [Priority 3] | Yes |
| Point 9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. [Priority 3] | No Not strictly necessary, but might be nice, especially in the gallery view page --CMN |
| Point 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. [Priority 2] | Yes |
| Point 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. [Priority 2] | Not applicable |
| Point 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. [Priority 3] | Yes Strictly speaking. The lists do lay out side by side, but turning off stylesheets is enough to change that. --CMN |
| Point 10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. [Priority 3] | Not applicable |
| Point 10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. [Priority 3] | No |
| Point 11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. [Priority 2] | Partial HTML 4 is, IMHO, out of date. There seems no clear reason not to have used XHTML, which is the latest version... --CMN |
| Point 11.2 Avoid deprecated features of W3C technologies. [Priority 2] | Partial Old DTD :-) Also, the gallery viewing pages use an align attrribute. --CMN |
| Point 11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) [Priority 3] | Partial Content Language would be nice in HTTP. Some more metadata might be useful too. Of course an interoperable way of making it work is tricky, but starting out would satisfy the checkpoint... --CMN |
| Point 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. [Priority 1] | Not applicable There is no apparent reason why this page cannot be accessible itself. --CMN |
| Point 12.1 Title each frame to facilitate frame identification and navigation. [Priority 1] | Not applicable |
| Point 12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. [Priority 2] | Not applicable |
| Point 12.3 Divide large blocks of information into more manageable groups where natural and appropriate. [Priority 2] | Yes Maybe this justifies the lists... --CMN |
| Point 12.4 Associate labels explicitly with their controls. [Priority 2] | Not applicable |
| Point 13.1 Clearly identify the target of each link. [Priority 2] | Yes |
| Point 13.10 Provide a means to skip over multi-line ASCII art. [Priority 3] | Not applicable |
Report generated by HERA:
© Copyright 2003 Sidar.