 |
Results for http://www.ahead.org 
Page last checked on Fri 05/08/2005 at 11:01pm.
General Quality
Privacy
Accessibility
This page
complies with all of the automatic checkpoints of the W3C Web Content
Accessibility Guidelines. However, it does not comply with all of the
manual checkpoints, and requires manual verification.
| Automatic Checkpoints | Manual Checkpoints | |||||
|---|---|---|---|---|---|---|
| Status | Errors | Instances | Status | Warnings | Instances | |
| Priority 1 |  |
0 | 0 | |
6 | 12 |
| Priority 2 | |
0 | 0 | |
13 | 19 |
| Priority 3 | |
0 | 0 | |
8 | 8 |
|
Warnings | |
| 6 tests, 12 instances on page | Expand Code Fragments |
| Guideline | Instances | Line Numbers | |
|---|---|---|---|
| 1.1 | If an image conveys important information beyond what is in its alternative text, provide an extended description. | 4 | 28, 36, 70, 88 |
| 2.1 | If you use color to convey information, make sure the information is also represented another way. | 4 | 28, 36, 70, 88 |
| 4.1 | Identify any changes in the document's language. | ||
| 6.1 | If style sheets are ignored or unsupported, ensure that pages are still readable and usable. | ||
| 7.1 | Make sure that the page does not cause the screen to flicker rapidly. | ||
| 14.1 | Use the simplest and most straightforward language that is possible. | ||
|
Warnings | |
| 13 tests, 19 instances on page | Expand Code Fragments |
| Guideline | Instances | Line Numbers | |
|---|---|---|---|
| 2.2 | Check that the foreground and background colors contrast sufficiently with each other. | 4 | 28, 36, 70, 88 |
| 3.1 | Where it's possible to mark up content instead of using images, use a markup language. | ||
| 3.2 | Make sure your document validates to formal published grammars. | ||
| 3.5 | Make sure header elements are not used only for bold text. | ||
| 7.2 | If this .gif image is animated, make sure it does not contain fast or distracting motion. | 4 | 28, 36, 70, 88 |
| 10.1 | Inform the user that clicking on certain links or areas of a window will open pop-up windows or change the active window. | 1 | 57 |
| 10.2 | Make sure that labels of all form controls are properly placed. | ||
| 11.1 | Use the latest technology specification available whenever possible. | ||
| 12.3 | If there are logical groupings of form controls, use FIELDSET with LEGEND on each group. | 1 | 57 |
| 12.3 | Group related elements when possible. | ||
| 13.1 | Make sure that all link phrases make sense when read out of context. | ||
| 13.3 | Provide the user with a site map or table of contents , a description of the general layout of the site, the access features used, and instructions on how to use them. | ||
| 13.4 | Provide a clear, consistent navigation structure. | ||
|
Warnings | |
| 8 tests, 8 instances on page |
| Guideline | Instances | Line Numbers | |
|---|---|---|---|
| 9.4 | Consider specifying a logical tab order among form controls, links, and objects. | ||
| 9.5 | Consider adding keyboard shortcuts to frequently used links. | ||
| 11.3 | Allow users to customize their experience of the web page. | ||
| 13.5 | Provide navigation bars for easy access to the navigation structure. | ||
| 13.7 | If there is a search feature, provide different types of searches for different skill levels and preferences. | ||
| 13.8 | Provide distinguishing information at the beginning of headings, paragraphs, lists, etc. | ||
| 13.9 | If this document is part of a collection, provide metadata that identifies this document's location in the collection. | ||
| 14.3 | Use a consistent style of presentation between pages. | ||
Custom Accessibility Standards
![[Information available when using Watchfire products]](index_files/wso_flame.gif){kind=small} Watchfire WebXM and WebQA can identify pages that do
not meet custom accessibility standards (learn
more) |
|---|
Links out:
22
