![[Home]](/jarmin/pics/arrow-r.gif){kind=icon}
Priority 2 Checkpoints
WAI Guideline 2: Don't rely on color alone.
Colours
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]. [WAI ![[Open link in new browser window.]](../images/newwin.gif "Open external link in new browser window."){kind=small}
]
See the chapter on:
Colour: Provide contrast
WAI Guideline 3: Use markup and style sheets and do so properly.
Images
3.1: When an appropriate markup language exists, use markup rather than images to convey information. [WAI ]
See the chapter on:
Graphics
Validation
3.2: Create documents that validate to published formal grammars. [WAI ]
See the chapters on:
Doctype
Validation
Stylesheets
3.3: Use style sheets to control layout and presentation. [WAI ]
See the chapter on:
CSS
Sizes (fonts, margins, etc.)
3.4: Use relative rather than absolute units in markup language attribute values and style sheet property values. [WAI ]
See the chapter on:
Relative units
Structure
3.5: Use header elements to convey document structure and use them according to specification. [WAI ]
See the chapter on:
Structural mark-up
Lists
3.6: Mark up lists and list items properly. [WAI ]
Quotations
3.7: Mark up quotations. Do not use quotation markup for formatting effects such as indentation. [WAI ]
See the chapter on:
Quotations
WAI Guideline 5: Create tables that transform gracefully.
Tables
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). [WAI ]
5.4: If a table is used for layout, do not use any structural markup for the purpose of visual formatting. [WAI ]
See the chapter on:
Tables
WAI Guideline 6: Ensure that pages featuring new technologies transform gracefully.
Dynamic content
6.5: Ensure that dynamic content is accessible or provide an alternative presentation or page. [WAI ]
See the chapter on:
Dynamic and multimedia content
Applets and scripts
6.4: For scripts and applets, ensure that event handlers are input device-independent. [WAI ]
WAI Guideline 7: Ensure user control of time-sensitive content changes.
Blinking
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). [WAI ]
Automatic refresh
7.4: Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. [WAI ]
See the chapter on:
Metadata
Automatic redirect
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. [WAI ]
See the chapter on:
Metadata
Applets and scripts
7.3: Until user agents allow users to freeze moving content, avoid movement in pages. [WAI ]
See the chapter on:
Dynamic and multimedia content
WAI Guideline 8: Ensure direct accessibility of embedded user interfaces.
Applets and scripts
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]. [WAI ]
See the chapter on:
Dynamic and multimedia content
WAI Guideline 9: Design for device-independence.
Applets and scripts
9.2: Ensure that any element that has its own interface can be operated in a device-independent manner. [WAI ]
9.3: For scripts, specify logical event handlers rather than device-dependent event handlers. [WAI ]
WAI Guideline 10: Use interim solutions.
Pop-up windows
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. [WAI ]
Forms
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. [WAI ]
WAI Guideline 11: Use W3C technologies and guidelines.
Technologies reviewed for accessibility
11.1: Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. [WAI ]
See the chapter on:
Standards
Deprecated features
11.2: Avoid deprecated features of W3C technologies. [WAI ]
See the chapter on:
Deprecated elements
WAI Guideline 12: Provide context and orientation information.
Readability
12.3: Divide large blocks of information into more manageable groups where natural and appropriate. [WAI ]
See the chapter on:
Content
Frames
12.2: Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. [WAI ]
See the chapter on:
Frames
Forms
12.4: Associate labels explicitly with their controls. [WAI ]
WAI Guideline 13: Provide clear navigation mechanisms.
Links
13.1: Clearly identify the target of each link. [WAI ] [Techniques ]
See the chapter on:
Usability
Metadata
13.2: Provide metadata to add semantic information to pages and sites. [WAI ]
See the chapter on:
Metadata
Site maps
13.3: Provide information about the general layout of a site (e.g., a site map or table of contents). [WAI ]
See the chapter on:
Usability
Consistent navigation
13.4: Use navigation mechanisms in a consistent manner. [WAI ]
See the chapter on:
Usability
| Access Guide Home | Table of Contents | Definitions | Glossary |