| In General (Priority 2) |
Yes |
No |
N/A |
| 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]. |
|
|
Not Core ( OK ) |
| 3.1 When an appropriate markup language exists, use markup rather than images to convey information. |
|
|
Not Core ( OK ) |
| 3.2 Create documents that validate to published formal grammars. |
|
|
Not Core ( OK ) |
| 3.3 Use style sheets to control layout and presentation. |
|
To Do |
Not Core ( OK ) |
| 3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values. |
|
|
Not Core ( OK ) |
| 3.5 Use header elements to convey document structure and use them according to specification. |
|
To Do |
|
| 3.6 Mark up lists and list items properly. |
|
|
Not Core ( OK ) |
| 3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation. |
|
|
Not Core ( OK ) |
| 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. |
|
|
Not Core ( OK ) |
| 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). |
|
|
Not Core ( OK ) |
| 7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. |
|
|
Not Core ( OK ) |
| 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. |
|
|
Not Core ( OK ) |
| 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. |
|
To Do |
|
| 11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. |
|
|
Not Core ( OK ) |
| 11.2 Avoid deprecated features of W3C technologies. |
|
To Do |
|
| 12.3 Divide large blocks of information into more manageable groups where natural and appropriate. |
|
|
Not Core ( OK ) |
| 13.1 Clearly identify the target of each link. |
|
To Do |
|
| 13.2 Provide metadata to add semantic information to pages and sites. |
|
To Do |
|
| 13.3 Provide information about the general layout of a site (e.g., a site map or table of contents). |
|
To Do |
|
| 13.4 Use navigation mechanisms in a consistent manner. |
|
|
Not Core ( OK ) |
| And if you use tables (Priority 2) |
Yes |
No |
N/A |
| 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). |
|
To Do |
|
| 5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting. |
|
|
Not Core ( OK ) |
| And if you use frames (Priority 2) |
Yes |
No |
N/A |
| 12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. |
|
|
Not Core ( OK ) |
| And if you use forms (Priority 2) |
Yes |
No |
N/A |
| 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. |
OK |
|
|
| 12.4 Associate labels explicitly with their controls. |
OK |
|
|
| And if you use applets and scripts (Priority 2) |
Yes |
No |
N/A |
| 6.4 For scripts and applets, ensure that event handlers are input device-independent. |
|
|
Not Core ( OK ) |
| 7.3 Until user agents allow users to freeze moving content, avoid movement in pages. |
|
|
Not Core ( OK ) |
| 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.] |
|
|
Not Core ( OK ) |
| 9.2 Ensure that any element that has its own interface can be operated in a device-independent manner. |
|
|
Not Core ( OK ) |
| 9.3 For scripts, specify logical event handlers rather than device-dependent event handlers. |
|
|
Not Core ( OK ) |
Usability & Standards 
