| In General (Priority 1) | Pass/Fail | Explanation |
|---|---|---|
| 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. | Fail | Many images do not have ALT text, including spacer images used for layouts. |
| 2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup. | N/A | No information on the page relies on color for understanding. |
| 4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). | N/A | There are no changes in the natural language of the document text. There are some images that show Japanese, Chinese, Korean and Taiwanese text. These images are links to pages in that language, but there is no text in any other language. |
| 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. | Pass | Turning off style sheets does not leave the page unreadable. In fact there is very little other than a few fonts that even changes when the style sheet is not applied. |
| 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. | N/A | Content is not changed dynamically. |
| 7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. | Pass | There is no flickering on the page, no animated gifs or other changing content. |
| 14.1 Use the clearest and simplest language appropriate for a site's content. | Pass | Most of the text are links to other sections of the site. The navigation is clear and straightforward. |
| And if you use images and image maps (Priority 1) | Pass/Fail | Explanation |
| 1.2 Provide redundant text links for each active region of a server-side image map. | N/A | No image maps are used on this page. |
| 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. | N/A | No image maps are used on this page. |
| And if you use tables (Priority 1) | Pass/Fail | Explanation |
| 5.1 For data tables, identify row and column headers. | N/A | No Data Tables were used on this page. |
| 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. | N/A | No Data Tables were used on this page. |
| And if you use frames (Priority 1) | Pass/Fail | Explanation |
| 12.1 Title each frame to facilitate frame identification and navigation. | N/A | No Frames were used on this page. |
| And if you use applets and scripts (Priority 1) | Pass/Fail | Explanation |
| 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. | Pass and Fail | Access to the same information is provided even if scripting is turned off. This is done in a non-standard manner: instead of using NOSCRIPT tags, the script uses document.write to create a dropdown list of options for users from areas other than the United States. Thi script also uses document.write to hide (by commenting out) the text that is presented when scripting is turned off or not available.
However, the script goes to a new page when a new link is chosen from the list, without hitting a submit button. This is a problem when a someone using a screen reader, or is restricted to using only the keyboard, wants to read through the list before making a choice. The first item in the list gets chosen automatically. |
| And if you use multimedia (Priority 1) | Pass/Fail | Explanation |
| 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. | N/A | No Multimedia is used on this page. |
| 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. | N/A | No Multimedia is used on this page. |
| And if all else fails (Priority 1) | Pass/Fail | Explanation |
| 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. | N/A | Not needed for this page - it can be brought up to speed without significantly changing the layout or flow. |
| In General (Priority 2) | Pass/Fail | Explanation |
|---|---|---|
| 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]. | Pass, with one nit... | Black text on a white background. Other colors are shades of yellow. Everything looks fine in 256 grays. The nit: the "submit button" for the dropdown is an image that has a white arrow on the yellow background. Difficult to see in color or grayscale. |
| 3.1 When an appropriate markup language exists, use markup rather than images to convey information. | Pass, sort of... | With a bit of CSS wrangling, we could come up with text equivalents for the current image based navigational elements. It would be time better spent to make the current images accessible (by adding appropriate ALT text) |
| 3.2 Create documents that validate to published formal grammars. | Fail | No Doctype, many IMG tags missing ALT text, the JavaScript document.writes cause many errors. Proprietary code such as marginheight and topmargin, are not even necessary.
|
| 3.3 Use style sheets to control layout and presentation. | Fail | CSS is used a bit for presentation, but TABLEs are used for layout. They do linearize fairly well, however. |
| 3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values. | Fail | The stylesheet usees absolute sizes (pixels) for markup. Many browsers now allow for text resizing regardless of whether the stylesheet uses absolute or relative sizing for markup. |
| 3.5 Use header elements to convey document structure and use them according to specification. | Fail | Images are used instead of header text. |
| 3.6 Mark up lists and list items properly. | N/A | No LISTs are used on the page. |
| 3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation. | N/A | No quotation markup is used on the page. |
| 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. | N/A | No dynamic content is used on the page. |
| 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). | Pass | No blinking is used on the page. |
| 7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. | Pass | no auto-refreshing pages. |
| 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. | N/A | any redirects that may be there are transparent to the user/browser. |
| 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. | Pass | no pop-up windows |
| 11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. | Fail | Not using CSS or a valid HTML space. |
| 11.2 Avoid deprecated features of W3C technologies. | Fail | FONT tag is used in multiple places. |
| 12.3 Divide large blocks of information into more manageable groups where natural and appropriate. | Pass | Links are grouped appropriately. |
| 13.1 Clearly identify the target of each link. | Pass | Links are not hidden - except for the dropdown list, but context serves to explain where those links are going. |
| 13.2 Provide metadata to add semantic information to pages and sites. | Pass | While some metadata is there, there could be more... |
| 13.3 Provide information about the general layout of a site (e.g., a site map or table of contents). | Fail | No site map or table of contents, but there is a search capability. |
| 13.4 Use navigation mechanisms in a consistent manner. | Pass | Navigation elements are consistent. |
| And if you use tables (Priority 2) | Pass/Fail | Explanation |
| 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). | Pass | Layout tables make sense when linearized (looked at in Lynx). |
| 5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting. | Pass | Structural markup was not used (IE TH not used to make text bold and centered...). |
| And if you use frames (Priority 2) | Pass/Fail | Explanation |
| 12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. | N/A | No frames used on the page. |
| And if you use forms (Priority 2) | Pass/Fail | Explanation |
| 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. | Fail | Form is used as a navigational element. Labels not used. |
| 12.4 Associate labels explicitly with their controls. | Fail | See above |
| And if you use applets and scripts (Priority 2) | Pass/Fail | Explanation |
| 6.4 For scripts and applets, ensure that event handlers are input device-independent. | Fail | Keyboard only users will get sent to the first page in the dropdown list as they key through it, Likewise for screen readers reading through the options. |
| 7.3 Until user agents allow users to freeze moving content, avoid movement in pages. | Pass | No motion on the page |
| 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.] | Fail | Keyboard only users will get sent to the first page in the dropdown list as they key through it, Likewise for screen readers reading through the options. |
| 9.2 Ensure that any element that has its own interface can be operated in a device-independent manner. | N/A | no optional interfaces present. |
| 9.3 For scripts, specify logical event handlers rather than device-dependent event handlers. | Fail | Keyboard only users will get sent to the first page in the dropdown list as they key through it, Likewise for screen readers reading through the options. |
| In General (Priority 3) | Pass/Fail | Explanation |
|---|---|---|
| 4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs. | Fail | Abbreviations and Acronyms are not expanded. |
| 4.3 Identify the primary natural language of a document. | Fail | Not identified. |
| 9.4 Create a logical tab order through links, form controls, and objects. | Fail | Works for the most part, but could use some refining (sometimes tabbing goes vertically, sometimes horizontally (when you expect vertical). |
| 9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. | Fail | No keyboard shortcuts provided. |
| 10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. | Fail | Most of the links are separated only by space. Is this still an issue? |
| 11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) | Pass | At least for language this has been done |
| 13.5 Provide navigation bars to highlight and give access to the navigation mechanism. | Pass | Navigation bars are present, but as images. |
| 13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. | Fail | Related links are grouped, but no way to bypass them |
| 13.7 If search functions are provided, enable different types of searches for different skill levels and preferences. | Pass | A variety of ways to narrow your search is offered. |
| 13.8 Place distinguishing information at the beginning of headings, paragraphs, lists, etc. | Pass | This is done with images, though. It would be better with text headers. |
| 13.9 Provide information about document collections (i.e., documents comprising multiple pages.). | N/A | No document collections |
| 13.10 Provide a means to skip over multi-line ASCII art. | N/A | No ASCII art. |
| 14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page. | N/A | Not needed for this page that is primarily navigation. |
| 14.3 Create a style of presentation that is consistent across pages. | Pass | Style is consistent. |
| And if you use images and image maps (Priority 3) | Pass/Fail | Explanation |
| 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. | N/A | No image maps used. |
| And if you use tables (Priority 3) | Pass/Fail | Explanation |
| 5.5 Provide summaries for tables. | N/A | Tables are used for layout, not data. |
| 5.6 Provide abbreviations for header labels. | N/A | Tables are used for layout, not data. |
| 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. | Pass | The layout linearizes fine. |
| And if you use forms (Priority 3) | Pass/Fail | Explanation |
| 10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. | N/A | The FORM on the page does not have any empty controls. |