jarmin.com

  Accessibility Guide : Guidelines & Techniques : WAI : Priority 1

Priority 1 Checkpoints

WAI Guideline 1: Provide equivalent alternatives to auditory and visual content.

Text equivalents

1.1: Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video. [WAI ]

See the chapter on:
Graphics

Images and image maps

1.2: Provide redundant text links for each active region of a server-side image map. [WAI ]

See the chapter on:
Graphics : Image maps

Multimedia

1.3: Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation. [WAI ]

1.4: For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation. [WAI ]

See the chapter on:
Dynamic and multimedia content

WAI Guideline 2: Don't rely on color alone.

Colour

2.1: Ensure that all information conveyed with color is also available without color, for example from context or markup. [WAI ]

See the chapter on:
Colour

WAI Guideline 4: Clarify natural language usage.

Language changes

4.1: Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). [WAI ]

See the chapter on:
Content: Language changes

WAI Guideline 5: Create tables that transform gracefully.

Tables

5.1: For data tables, identify row and column headers. [WAI ]

5.2: For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. [WAI ]

See the chapter on:
Tables

WAI Guideline 6: Ensure that pages featuring new technologies transform gracefully.

Style sheet independence

6.1 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. [WAI ]

See the chapter on:
Cascading Style sheets (CSS)

Updating multiple versions

6.2: Ensure that equivalents for dynamic content are updated when the dynamic content changes. [WAI ]

See the chapter on:
Multimedia

Scripts and applets

6.3: 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. [WAI ]

See the chapter on:
Multimedia

WAI Guideline 7: Ensure user control of time-sensitive content changes.

Flickering

7.1: Until user agents allow users to control flickering, avoid causing the screen to flicker. [WAI ]

See the chapter on:
Graphics

WAI Guideline 9: Design for device-independence.

Images and image maps

9.1: Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape. [WAI ]

See the chapter on:
Graphics : Image maps

WAI Guideline 11: Use W3C technologies and guidelines.

Alternative formats

11.4: If, after best efforts, 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. [WAI ]

See the chapter on:
Multimedia: Text-only versions

WAI Guideline 12: Provide context and orientation information.

Frames

12.1: Title each frame to facilitate frame identification and navigation. [WAI ]

See the chapter on:
Frames

WAI Guideline 14: Ensure that documents are clear and simple.

Content

14.1: Use the clearest and simplest language appropriate for a site's content. [WAI ]

See the chapter on:
Content

Priority 2 Guidelines

| Access Guide Home | Table of Contents | Definitions | Glossary |

Copyleft © 2000-2015 jarmin.com
<webmaster@jarmin.com>
date: 021105