Priority 1 Index

Priority 1 Item 1
Provide a text equivalent for every non-text element . This includes: images, graphical representations of text , image map regions, animations, applets and programmatic objects, ASCII art, frames, scripts, images used as list bullets, spacers, graphical buttons, all sounds, stand-alone audio files, audio tracks of video, and video.

Priority 1 Item 2
Ensure that all information conveyed with color is also available without color, for example from context or markup. (One type of accessibility we are addressing is color-blindness.)

Priority 1 Item 3
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.

Priority 1 Item 4
Avoid causing the screen to flicker. (This is not only inaccessible, but very annoying.)

Priority 1 Item 5
Client side image maps should be provided instead of server side image maps. If you must use server-side image maps, provide redundant text links for each link on the image map.

Priority 1 Item 6
Use of frames is discouraged. (Fort Hays State University has decided not to use frames on its Web sites not only because of accessibility issues, but also because of design and maintenance issues.)

Priority 1 Item 7
Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone with color deficits.

Priority 1 Item 8
Clearly identify the target of each link. (Do not use "click here" as a link. When a screen reader goes across that, all it says is "click here"; thus, the user has no idea where the link is going.)

Priority 1 Item 9
Use header elements to convey document structure and use them according to specification. (Since we use Cascading Style Sheets to specify head sizes, etc., this should not be a concern.)

Priority 1 Item 10
Mark up lists and list items properly.

Priority 1 Item 11
Mark up quotations. Do not use quotation markup for formatting effects such as indentation.

Priority 1 Item 12
Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).

Priority 1 Item 13
Make scripts and applets that allow users to interpret or access page content, or any other element that has its own interface, compatible with assistive technologies, and ensure that event handlers are input device-independent.

Priority 1 Item 14
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.

Priority 1 Item 15
For data tables, identify row and column headers.

Priority 1 Item 16
For data tables that have two or more logical levels of row or column headers, use markup to associate data cells with header cells.

Priority 1 Item 17
Provide summaries for data tables. If a table is used only for layout, provide an empty summary attribute (e.g., summary = "").

Priority 1 Item 18
Label all form controls. Position the label close to the form control, and use appropriate markup to identify the format control and associate it with its label.

Priority 1 Item 19
For any time-based multimedia presentation (e.g., movie or animation) synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation.

Priority 1 Item 20
When a timed response is required, the user shall be alerted and given sufficient opportunity to indicate more time is required.

Priority 1 Item 21
A method shall be provided that permits users to skip repetitive navigation links.

Priority 1 Item 22
If 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.


Back