Priority 2

Table of contents 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 When an appropriate markup language exists, use markup rather than images to convey information. Create documents that validate to published formal grammars. Use style sheets to control layout and presentation Use relative rather than absolute units in markup language attribute values and style sheet property values. Use header elements to convey document structure and use them according to specification. Mark up lists and list items properly. Mark up quotations. Do not use quotation markup for formatting effects such as indentation. Ensure that dynamic content is accessible or provide an alternative presentation or page. 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). Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. 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. 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. Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. Avoid deprecated features of W3C technologies. Divide large blocks of information into more manageable groups where natural and appropriate. Clearly identify the target of each link. Provide metadata to add semantic information to pages and sites. Provide information about the general layout of a site (e.g., a site map or table of contents). Use navigation mechanisms in a consistent manner.

Copyright © 2001-2003 by Rainer Hillebrand and Thomas Wierlemann