Copyright © 2007 ASCS — Some Rights Reserved.
Design by wgpotter — Tested in IE, Opera, Firefox, Netscape, Safari.
This checklist covers the following accessibility standard:
The column headings in the checklists indicate the following:
| Standard Title: | Web Content Accessibility Guidelines (WCAG) 1.0 |
| Standard Source: | http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/ |
| Compliance Level: | AAA |
| Compliance Scope: | All pages of adoptionsask.org |
| Checklist Created: | 28 August 2007 |
| Checklist Author: | W.G. Potter |
| Checklist Completed: | 28 August 2007 |
| Completed By: | W.G. Potter |
| Checkpoint | P | Summary | C | Notes |
|---|---|---|---|---|
| 1.1 | 1 | Provide a text equivalent for every non-text element. | F | |
| 1.2 | 1 | Provide redundant text links for each active region of a server-side image map. | N/A | No image maps. |
| 1.3 | 1 | Provide an auditory description of the important information of the visual track of a multimedia presentation. | N/A | No videos. |
| 1.4 | 1 | 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 videos. |
| 1.5 | 3 | Provide redundant text links for each active region of a client-side image map. | N/A | No image maps. |
| 2.1 | 1 | Ensure that all information conveyed with color is also available without color. | F | |
| 2.2 | 2 | For images, 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. | F | |
| 2.2 | 3 | For text, 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. | F | |
| 3.1 | 2 | Use markup rather than images to convey information. | F | |
| 3.2 | 2 | Create documents that validate to published formal grammars. | F | |
| 3.3 | 2 | Use style sheets to control layout and presentation. | F | |
| 3.4 | 2 | Use relative rather than absolute units in markup language attribute values and style sheet property values. | P | Relative units em or % used for all text and text spacing except title header. |
| 3.5 | 2 | Use header elements to convey document structure and use them according to specification. | F | |
| 3.6 | 2 | Mark up lists and list items properly. | F | |
| 3.7 | 2 | Mark up quotations. Do not use quotation markup for formatting effects such as indentation. | F | |
| 4.1 | 1 | Clearly identify changes in the natural language of a document's text and any text equivalents. | N/A | All English. |
| 4.2 | 3 | Specify the expansion of each abbreviation or acronym in a document where it first occurs. | F | |
| 4.3 | 3 | Identify the primary natural language of a document. | F | |
| 5.1 | 1 | For data tables, identify row and column headers. | F | |
| 5.2 | 1 | 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 | |
| 5.3 | 2 | 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. | F | Layout tables used on Contact page for Phone and Email contact information. They make sense when linearized. |
| 5.4 | 2 | If a table is used for layout, do not use any structural markup for the purpose of visual formatting. | F | |
| 5.5 | 3 | Provide summaries for tables. | F | |
| 5.6 | 3 | Provide abbreviations for header labels. | F | |
| 6.1 | 1 | Organize documents so they may be read without style sheets. | F | |
| 6.2 | 1 | Ensure that equivalents for dynamic content are updated when the dynamic content changes. | N/A | No scripts, applets or programmatic objects. |
| 6.3 | 1 | 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. | N/A | No scripts, applets or programmatic objects. |
| 6.4 | 2 | For scripts and applets, ensure that event handlers are input device-independent. | N/A | No scripts, applets or programmatic objects. |
| 6.5 | 2 | Ensure that dynamic content is accessible or provide an alternative presentation or page. | N/A | No scripts, applets or programmatic objects. |
| 7.1 | 1 | Avoid causing the screen to flicker. | F | |
| 7.2 | 2 | Avoid causing content to blink. | F | |
| 7.3 | 2 | Avoid movement in pages. | P | Assumes GIF slide show (6 seconds per image) on each page is exempt. |
| 7.4 | 2 | Do not create periodically auto-refreshing pages. | F | |
| 7.5 | 2 | Do not use markup to redirect pages automatically. Instead, configure the server to perform redirects. | N/A | No page redirection. |
| 8.1 | 1 | When functionality is important and not presented elsewhere, make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies. | N/A | No scripts, applets or programmatic objects. |
| 8.1 | 2 | Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies. | N/A | No scripts, applets or programmatic objects. |
| 9.1 | 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. |
| 9.2 | 2 | Ensure that any element that has its own interface can be operated in a device-independent manner. | F | Assumes QuickTime plug-in, or similarly accessible plug-in, is used for audio content. |
| 9.3 | 2 | For scripts, specify logical event handlers rather than device-dependent event handlers. | N/A | No scripts. |
| 9.4 | 3 | Create a logical tab order through links, form controls, and objects. | F | |
| 9.5 | 3 | Provide keyboard shortcuts to important links, form controls, and groups of form controls. | F | Alt keyboard shortcuts provided for main navigation |
| 10.1 | 2 | Do not cause pop-ups or other spawned windows to appear and do not change the current window without informing the user. | F | |
| 10.2 | 2 | For all form controls with implicitly associated labels, ensure that the label is properly positioned. | N/A | No forms. |
| 10.3 | 3 | Provide a linear text alternative for all tables that lay out text in parallel, word-wrapped columns. | P | For layout tables it's not applicable, since the layout tables on the Contact page have no word-wrap. For data tables, this guideline is open to interpretation - the table markup (e.g. scope="col") appears to be sufficient to meet this guideline. |
| 10.4 | 3 | Include default, place-holding characters in edit boxes and text areas. | N/A | No text input. |
| 10.5 | 3 | Include non-link, printable characters (surrounded by spaces) between adjacent links. | F | Hidden period (.) placed after each main navigation link (there are no other adjacent links). This shows up as a printable nonlink character when style sheet is turned off, for example. |
| 11.1 | 2 | Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. | F | XHTML, CSS, JPEG and GIF used. Assume GIF images are OK since the W3C conformance icons are GIFs! |
| 11.2 | 2 | Avoid deprecated features of W3C technologies. | F | |
| 11.3 | 3 | Provide information so that users may receive documents according to their preferences. | P | This is not a multilingual web site, so languages other than English are not supported. Aural CSS is not provided, but users can provide their own. |
| 11.4 | 1 | 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 pages are accessible. |
| 12.1 | 1 | Title each frame to facilitate frame identification and navigation. | N/A | No frames. |
| 12.2 | 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. |
| 12.3 | 2 | Divide large blocks of information into more manageable groups where natural and appropriate. | F | |
| 12.4 | 2 | Associate labels explicitly with their controls. | N/A | No forms. |
| 13.1 | 2 | Clearly identify the target of each link. | F | |
| 13.2 | 2 | Provide metadata to add semantic information to pages and sites. | F | |
| 13.3 | 2 | Provide information about the general layout of a site. | F | Site contents described at bottom of Home Page. |
| 13.4 | 2 | Use navigation mechanisms in a consistent manner. | F | |
| 13.5 | 3 | Provide navigation bars to highlight and give access to the navigation mechanism. | F | |
| 13.6 | 3 | Group related links, identify the group and provide a way to bypass the group. | F | Hidden "Skip to Contents" link provided at the top of every page (shows up when style sheet is turned off, for example). |
| 13.7 | 3 | If search functions are provided, enable different types of searches for different skill levels and preferences. | N/A | No search function. |
| 13.8 | 3 | Place distinguishing information at the beginning of headings, paragraphs, lists, etc. | F | |
| 13.9 | 3 | Provide information about document collections (i.e., documents comprising multiple pages). | N/A | No multiple page documents. |
| 13.10 | 3 | Provide a means to skip over multi-line ASCII art. | N/A | No ASCII art! |
| 14.1 | 1 | Use the clearest and simplest language appropriate for a site's content. | F | |
| 14.2 | 3 | Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page. | F | |
| 14.3 | 3 | Create a style of presentation that is consistent across pages. | F |