The Web Content Accessibility Guidelines Working Group is working carefully to enable organizations and individuals that are currently using WCAG 1.0 (which remains stable and referenceable at this time) to ensure that they will eventually be able to make a smooth transition to WCAG 2.0.

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. [Priority 1]

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. [Priority 1]

content-structure-separation

Guideline 1.3 Ensure that information, functionality, and structure are separable from presentation.

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

3.3 Use style sheets to control layout and presentation. [Priority 2] (see also structure-emphasis)

3.5 Use header elements to convey document structure and use them according to specification. [Priority 2] (see also use-spec and navigation-mechanisms)

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. [Priority 1]

5.6 Provide abbreviations for header labels. [Priority 3]

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. [Priority 1]

12.4 Associate labels explicitly with their controls. [Priority 2]

visual-audio-contrast

Guideline 1.4 Make it easy to distinguish foreground information from background images or sounds.

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].

keyboard-operation

Guideline 2.1 Make all functionality operable via a keyboard or a keyboard interface.

7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. [Priority 2]

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. [Priority 2] (see also consistent-behavior)

3.3 Use style sheets to control layout and presentation. [Priority 2] (see also content-structure-separation)

3.5 Use header elements to convey document structure and use them according to specification. [Priority 2] (see also content-structure-separation and use-spec)

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). [Priority 2]

9.4 Create a logical tab order through links, form controls, and objects. [Priority 3] (see also keyboard-operation)

9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. [Priority 3] (see also keyboard-operation)

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. [Priority 2]

12.1 Title each frame to facilitate frame identification and navigation. [Priority 1] (see also text-equiv)

12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. [Priority 2]

12.3 Divide large blocks of information into more manageable groups where natural and appropriate. [Priority 2]

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. [Priority 2] (see also time-limits)

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. [Priority 2]

13.1 Clearly identify the target of each link. [Priority 2]

13.4 Use navigation mechanisms in a consistent manner. [Priority 2]

14.3 Create a style of presentation that is consistent across pages. [Priority 3]

3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation. [Priority 2]

5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting. [Priority 2]

11.2 Avoid deprecated features of W3C technologies. [Priority 2]

technology-supports-access

Guideline 4.2 Ensure that user interfaces are accessible or provide an accessible alternative(s)

3.1 When an appropriate markup language exists, use markup rather than images to convey information. [Priority 2]

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. [Priority 1]

6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. [Priority 2]

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.]

9.2 Ensure that any element that has its own interface can be operated in a device-independent manner. [Priority 2]

11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.

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. [Priority 1]