Validation report Validation reportPage: http://www.bendigo2004.com/
Author: Charles McCathieNevile (with help) <charles@w3.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] | No Major faults include search button, page heading, sponsors (who might be happy not to be identified with the inaccessibility :-)... |
| Point 1.2 Provide redundant text links for each active region of a server-side image map. [Priority 1] | Not applicable no image maps |
| 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 --hera2 |
| 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 --H2V |
| 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] | Yes |
| 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]. | No search button, last update info, producers info. (This was an ayeball test, not using the so-called algorithm) |
| Point 3.1 When an appropriate markup language exists, use markup rather than images to convey information. [Priority 2] | No Search button,, "top" button. Generally OK otherwise |
| Point 3.2 Create documents that validate to published formal grammars. [Priority 2] | No |
| Point 3.3 Use style sheets to control layout and presentation. [Priority 2] | Partial There are style sheets, there are also layout tables and style attributes everywhere |
| Point 3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values. [Priority 2] | No text uses "font:11px" --AMJA And there are plenty of other fixed layout sizes --CMN |
| Point 3.5 Use header elements to convey document structure and use them according to specification. [Priority 2] | No Not even one header |
| Point 3.6 Mark up lists and list items properly. [Priority 2] | No menu items could have been presented as lists --AMJA |
| 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 All in english |
| Point 4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs. [Priority 3] | No Countries in the medal table |
| Point 4.3 Identify the primary natural language of a document. [Priority 3] | No --AMJA |
| Point 5.1 For data tables, identify row and column headers. [Priority 1] | No The medal tally table... |
| 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 nothing that complex |
| 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] | Yes |
| Point 5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting. [Priority 2] | Yes |
| Point 5.5 Provide summaries for tables. [Priority 3] | No Medal table should have a caption IMHO |
| Point 5.6 Provide abbreviations for header labels. [Priority 3] | Not applicable Not necessary for the only data table, not that it has table headers... |
| 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 The only dynamic content is its own equivalent - static content animated. |
| 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 (as far as I can tell - I think I checked everything) |
| Point 6.4 For scripts and applets, ensure that event handlers are input device-independent. [Priority 2] | No redundant with 9.2 (tested first) |
| Point 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. [Priority 2] | Yes In principle |
| Point 7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. [Priority 1] | Cannot tell It is in a grey area because in many browsers it gives a jerky red over red motion. I do not think it is severe enough to trigger the PSE response, but I would have wanted to test properly before letting it loose on the web. |
| 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] | No scrolling news --AMJA |
| 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 no redirection |
| 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.] | Cannot tell This would cause a problem for the Tiflowin screen reader, still widely used in South America. It seems to be causing problems with JAWS too, which means in the Australian context there is a problem for most blind users. Half an hour of testing should work out what the problem is |
| 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 --hera2 |
| Point 9.2 Ensure that any element that has its own interface can be operated in a device-independent manner. [Priority 2] | No The scroller is operable by mouse or mouse. |
| Point 9.3 For scripts, specify logical event handlers rather than device-dependent event handlers. [Priority 2] | No has onMouseOver - no onFocus - for scolling news. --AMJA |
| Point 9.4 Create a logical tab order through links, form controls, and objects. [Priority 3] | Yes q/a ok; tab ok --AMJA |
| 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 Some accesskeys would be nice |
| 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] | Not tested |
| 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] | No --Hera2 |
| 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] | No |
| Point 10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. [Priority 3] | No |
| 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] | Yes |
| Point 11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. [Priority 2] | Yes Not valid, but being used after a fashion... |
| Point 11.2 Avoid deprecated features of W3C technologies. [Priority 2] | No --Hera2 |
| Point 11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) [Priority 3] | No No link information, nothing usful from the server... |
| 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] | No Page is not level A, there is no linnk to anything better |
| Point 12.1 Title each frame to facilitate frame identification and navigation. [Priority 1] | Not applicable --hera2 |
| 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 --hera2 |
| Point 12.3 Divide large blocks of information into more manageable groups where natural and appropriate. [Priority 2] | Yes In my opinion... |
| Point 12.4 Associate labels explicitly with their controls. [Priority 2] | No --hera2 |
| Point 13.1 Clearly identify the target of each link. [Priority 2] | No some "click here" links, ... |
| Point 13.2 Provide metadata to add semantic information to pages and sites. [Priority 2] | Partial Title only - no description, keywairs, or DC/AGLS or other metadata. --AMJA |
| Point 13.3 Provide information about the general layout of a site (e.g., a site map or table of contents). [Priority 2] | Yes |
| Point 13.4 Use navigation mechanisms in a consistent manner. [Priority 2] | Yes |
| Point 13.5 Provide navigation bars to highlight and give access to the navigation mechanism. [Priority 3] | Yes |
| Point 13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. [Priority 3] | No |
| Point 13.7 If search functions are provided, enable different types of searches for different skill levels and preferences. [Priority 3] | Yes site map, search box, browse. Doubt that there ios error correction or advanced functionality in the search box though... |
| Point 13.8 Place distinguishing information at the beginning of headings, paragraphs, lists, etc. [Priority 3] | Not applicable Content generally too short to be applicable here. |
| Point 13.9 Provide information about document collections (i.e., documents comprising multiple pages.). [Priority 3] | No Should be link elements at least |
| Point 13.10 Provide a means to skip over multi-line ASCII art. [Priority 3] | Not applicable |
| Point 14.1 Use the clearest and simplest language appropriate for a site's content. [Priority 1] | Partial ...the concept was agreed on for the purpose of providing... would be better as ... they agreed to provide... Otherwise not too bad. |
| Point 14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page. [Priority 3] | Yes |
| Point 14.3 Create a style of presentation that is consistent across pages. [Priority 3] | Yes except the front page :-) |
Report generated by HERA:
© Copyright 2003 Sidar.