| 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. |
| 2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup. | N/A | No information is related only to color. |
| 4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). | N/A | No language changes on this page. |
| 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 stylesheets off did not affect the reading of the page. |
| 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. | N/A | No dynamic content on this page. |
| 7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. | Pass | No flickering on the page. |
| 14.1 Use the clearest and simplest language appropriate for a site's content. | Pass | Appropriate language is used. |
| 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 | Image map is client side |
| 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. | Pass | Image Map is client side. |
| 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. |
| 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. |
| 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 |
| 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 | MouseOver image swap script does not affect the usability of the page. |
| 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 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 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 | All issues are easily fixed within the page. |
| 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 | Color contrast is high |
| 3.1 When an appropriate markup language exists, use markup rather than images to convey information. | Fail | Many instances of images used in place of text. Could/Should use HTML and CSS for these. Even MouseOver Image swaps culd be accomplished via CSS hover. |
| 3.2 Create documents that validate to published formal grammars. | Fail | No Doctype, lack of ALTs means no validation. |
| 3.3 Use style sheets to control layout and presentation. | Fail | TABLEs used for layout |
| 3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values. | Pass | One CSS declaration used pts instead of ems or percentages. |
| 3.5 Use header elements to convey document structure and use them according to specification. | Fail | Very few structural tags used. TABLEs used for layout and images were used for visual emphasis. |
| 3.6 Mark up lists and list items properly. | N/A | no lists |
| 3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation. | N/A | no quotes |
| 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. | N/A | no dynamic content |
| 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 |
| 7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. | Pass | no auto-refresh |
| 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. | pass | no auto-redirect |
| 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-ups (that I noticed) |
| 11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. | Fail | Not using a valid HTML space. |
| 11.2 Avoid deprecated features of W3C technologies. | Fail | Technically they failed. There are several places where deprecated features such as "align='center'" are used. But no glaring examples, like FONT tags. Also, TABLE based layout is strongly discouraged and could be considered "deprecated." |
| 12.3 Divide large blocks of information into more manageable groups where natural and appropriate. | N/A | No large blocks of info |
| 13.1 Clearly identify the target of each link. | Pass | No surprises |
| 13.2 Provide metadata to add semantic information to pages and sites. | Fail | More could be provided |
| 13.3 Provide information about the general layout of a site (e.g., a site map or table of contents). | Pass | Ther is an index page and a search page |
| 13.4 Use navigation mechanisms in a consistent manner. | Pass | The rest of the site has a consistent Nav bar at the top of each page |
| 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 | Table linearizes fine. |
| 5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting. | Pass | |
| 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. | N/A | No forms on this page |
| 12.4 Associate labels explicitly with their controls. | N/A | No forms |
| 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. | N/A | No applets, script is not necessary to the usability of the page. |
| 7.3 Until user agents allow users to freeze moving content, avoid movement in pages. | N/A | no moving content |
| 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.] | N/A | script functionalilty is eye candy |
| 9.2 Ensure that any element that has its own interface can be operated in a device-independent manner. | N/A | none present |
| 9.3 For scripts, specify logical event handlers rather than device-dependent event handlers. | Fail | Uses onMouseOver, but the effect is just eyecandy and doesn't contribute to the sites usability |
| In General (Priority 3) | Pass/Fail | Explanation |
|---|---|---|
| 4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs. | N/A | Noone on the page |
| 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. | Pass | tabbing works fine |
| 9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. | Fail | Not there, tha I can see |
| 10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. | pass | vertical bars used to separate links |
| 11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) | Fail | Didn't see any preferences |
| 13.5 Provide navigation bars to highlight and give access to the navigation mechanism. | Pass | This was done |
| 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 | links are grouped, but no jumps to content (the links are the main content on this page, however) |
| 13.7 If search functions are provided, enable different types of searches for different skill levels and preferences. | Fail | Search link goes to a page that says it isn't available yet... |
| 13.8 Place distinguishing information at the beginning of headings, paragraphs, lists, etc. | Fail | The groups are distinguished by whether they are text or images... |
| 13.9 Provide information about document collections (i.e., documents comprising multiple pages.). | N/A | |
| 13.10 Provide a means to skip over multi-line ASCII art. | N/A | |
| 14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page. | N/A | |
| 14.3 Create a style of presentation that is consistent across pages. | Pass | For the most part, this was done. Could be better implemented. |
| 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. | Fail | No text equivalents for the client-side image map. |
| And if you use tables (Priority 3) | Pass/Fail | Explanation |
| 5.5 Provide summaries for tables. | N/A | no data tables |
| 5.6 Provide abbreviations for header labels. | N/A | no data tables |
| 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. | N/A | |
| 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 |