WCAG 2.0 Checklist including related techniques and tests [DRAFT]

This is a view generated from the 11 February 2005 Working Draft. It represents a view of checklists that only includes success criterion and links to related techniques and tests.

Guideline 1.1 Provide text alternatives for all non-text content.

Status	Success Criterion
	1.1 L1 SC1: For all non-text content that is functional, such as graphical links or buttons, text alternatives serve the same purpose as the non-text content. Related Techniques: GENERAL Text alternatives for non-text content that provides functionality HTML 9.3: Text for images used as links HTML 9.4: Image and text links side by side HTML 10.4: Short text alternatives for object elements (future) HTML 10.5: Non-explicit text alternatives for object HTML 11.1: Use client side image map HTML 11.2: Text links for server side image maps. HTML 11.3: Redundant text links for client side image maps (deprecated) HTML 11.4: Text alternatives for client-side image maps HTML 12.3: Alternative content for programmatic objects HTML 12.4: Text and non-text alternatives for object HTML 12.5: Alternative content for applet HTML 12.6: Alt text for applet HTML 12.7: Alternative content for embed HTML 12.8: Alt text for embed HTML 14.4: Writing for browsers that do not support FRAME HTML 15.7: Text alternatives for submit buttons HTML 16.1: Text alternatives for scripts HTML 16.2: JavaScript URLs HTML 16.3: Scripted form submission Related Tests: Test 58: All input elements with a type attribute value of "image" have an alt attribute. Test 192: Alt text for all input elements with a type attribute value of "image" does not use the words "submit" or "button" (English). Test 59: Alt text for all input elements with a type attribute value of "image" identifies the purpose or function of the image. Test 196: Server-side image maps are not used except when image map regions cannot be defined using an available geometric shape. Test 13: All links in all client side image-maps are duplicated within the content.
	1.1 L1 SC2: For all non-text content that is used to convey information, text alternatives convey the same information. Related Techniques: GENERAL Text alternatives for non-text content that conveys information HTML 10.1: Short text alternatives for img elements ("alt-text") HTML 10.6: Long descriptions of images HTML 10.7: Long description of objects HTML 10.8: D links (deprecated) HTML 10.9: Describe images without longdesc HTML 10.12: Text in images HTML 12.4: Text and non-text alternatives for object HTML 12.5: Alternative content for applet HTML 14.6: Descriptive links for inaccessible frame source HTML 14.7: Alternative content for iframe HTML 14.8: Longdesc for iframe Related Tests: Test 1: All img elements have an alt attribute. Test 6: Alt text for all img elements is not placeholder text or user has confirmed that the Alt text is appropriate. Test 178: Alt text for all img elements that are not used as source anchors conveys the same information as the image. Test 8: A long description (longdesc) file is used for each img element that does not have Alt text and/or body text conveying the same information as the image. Test 9: All img elements that have a longdesc attribute also have an associated 'd-link'. Test 14: For all img elements, content text does not refer to the image by color alone. Test 64: All area elements have an alt attribute. Test 66: area link to sound file must have text transcript. Test 11: Alt text for all img elements contains all text in the image unless the image text is decorative or appears elsewhere in the content. Test 193: Alt text for all input elements with a type attribute value of "image" contains all non decorative text in the image. Test 194: Alt text for all area elements contains all non decorative text in the image area.
	1.1 L1 SC3: For non-text content that is intended to create a specific sensory experience, such as music or visual art, text alternatives identify and describe the non-text content. Related Techniques: GENERAL Text alternatives for non-text content that creates a specific sensory experience [music without words] GENERAL Text alternatives for non-text content that creates a specific sensory experience [visual art] HTML 10.6: Long descriptions of images HTML 10.7: Long description of objects HTML 10.8: D links (deprecated) HTML 10.9: Describe images without longdesc HTML 12.4: Text and non-text alternatives for object
	1.1 L1 SC4: Non-text content that does not provide information, functionality, or sensory experience is marked such that it can be ignored by assistive technology. Related Techniques: GENERAL Text alternatives and non-text content that does not provide functionality or convey information Related Tests: Test 16: Alt text for all img elements is the empty string ("") if the image is decorative. Test 175: Alt text for all img elements used as source anchors is different from the link text. Test 192: Alt text for all input elements with a type attribute value of "image" does not use the words "submit" or "button" (English).
	1.1 L1 SC5: Any text alternatives are explicitly associated with the non-text content. Related Techniques: HTML 9.3: Text for images used as links HTML 9.4: Image and text links side by side HTML 10.1: Short text alternatives for img elements ("alt-text") HTML 10.4: Short text alternatives for object elements (future) HTML 10.5: Non-explicit text alternatives for object HTML 10.6: Long descriptions of images HTML 10.7: Long description of objects HTML 10.12: Text in images HTML 11.1: Use client side image map HTML 11.4: Text alternatives for client-side image maps HTML 12.4: Text and non-text alternatives for object HTML 12.6: Alt text for applet HTML 12.8: Alt text for embed HTML 14.4: Writing for browsers that do not support FRAME HTML 14.6: Descriptive links for inaccessible frame source HTML 14.7: Alternative content for iframe HTML 14.8: Longdesc for iframe HTML 15.7: Text alternatives for submit buttons
	1.1 L1 SC6: For live audio-only or live video-only content, such as internet radio or Web cameras, text alternatives describe the purpose of the presentation or a link is provided to alternative real-time content, such as traffic reports for a traffic Web camera
	1.1 L3 SC1: For multimedia content, a combined transcript of audio descriptions of video and captions is provided. Related Techniques: GENERAL Text documents that provide descriptions of important visual information and transcripts of important auditory information

Guideline 1.2 Provide synchronized alternatives for multimedia.

Status	Success Criterion
	1.2 L1 SC1: Captions are provided for prerecorded multimedia.
	1.2 L1 SC2: Audio descriptions of video are provided for prerecorded multimedia
	1.2 L1 SC3: If multimedia content is rebroadcast from another medium, the accessibility features required by policy for that medium are intact.
	1.2 L2 SC1: Real-time captions are provided for live multimedia.
	1.2 L3 SC1: Sign language interpretation is provided for multimedia
	1.2 L3 SC2: Extended audio descriptions of video are provided for prerecorded multimedia.
	1.2 L3 SC3: Audio descriptions of video are provided for live multimedia.

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

Status	Success Criterion
	1.3 L1 SC1: Structures and relationships within the content can be programmatically determined. Related Techniques: GENERAL Separating structure from presentation GENERAL Identifying lists and list-items GENERAL Identifying forms and form-controls GENERAL Identifying data tables GENERAL Identifying images GENERAL Using text alternatives to identify structures within images GENERAL Using alternative views to highlight image structure GENERAL Alternative views of mathematical expressions GENERAL Structure of mathematical expressions GENERAL Forms and labels GENERAL Header cells and data cells GENERAL Functionality and presentation HTML 1.3: The address element HTML 3.1: Section headings HTML 5.6: Short Quotations (future) HTML 5.7: Long quotations HTML 5.13: Inline structural elements to identify citations, code fragments, deleted text, etc. HTML 6.1: Ordered lists HTML 7.1: The caption element (optional) HTML 7.4: Identifying groups of rows (optional) HTML 7.5: Identifying groups of columns (optional) HTML 7.6: Specifying the set of data cells for which each header cell provides header information HTML 7.7: Associating header cells with data cells HTML 7.8: Categorizing data cells HTML 7.10: Row and column headings HTML 12.1: Markup and style sheets rather than images: the example of math CSS 5.2: Creating layout, positioning, layering, and alignment CSS 9.1: Creating stylized text with CSS rather than using raster images CSS 9.2: Make raster image text accessible with CSS CSS 9.3: Indenting text Related Tests: Test 57: All input elements, with type of "text", have an explicitly associated label. Test 118: All input elements, with type of "password", have an explicitly associated label. Test 119: All input elements, with type of "checkbox", have an explicitly associated label. Test 120: All input elements, with type of "file", have an explicitly associated label. Test 121: All input elements, with type of "radio", have an explicitly associated label. Test 135: All img elements with images containing math expressions have equivalent MathML markup.
	1.3 L1 SC2: Emphasis can be programmatically determined. Related Techniques: GENERAL Emphasis HTML 5.1: Emphasis CSS 7.1: Specifying colors CSS 8.2: Specifying font characteristics CSS 9.1: Creating stylized text with CSS rather than using raster images CSS 9.2: Make raster image text accessible with CSS CSS 9.3: Indenting text CSS 9.5: Changing case
	1.3 L1 SC3: Any information conveyed through color can be programmatically determined. For example, through markup or unique characters that accompany the color coding. Related Techniques: GENERAL Using color to convey information CSS 8.2: Specifying font characteristics CSS 9.1: Creating stylized text with CSS rather than using raster images CSS 9.2: Make raster image text accessible with CSS CSS 9.3: Indenting text
	1.3 L2 SC1: Any information that is conveyed through color is visually evident without having to interpret color. For example, the distinction can additionally be determined through context, characters, or symbols that accompany the color presentation, or through pattern differences such as dotted red vs. solid green lines in a graph. Related Techniques: GENERAL Tactile graphics

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

Status	Success Criterion
	1.4 L1 SC1: Any text that is presented over a background image, color, or text can be programmatically determined. Related Techniques: HTML 10.12: Text in images
	1.4 L2 SC1: Text and diagrams that are presented over a background image, color, or text have a contrast greater than X1 where the whiter element is at least Y1 as measured by _____. Related Techniques: HTML 5.14: Color CSS 7.3: Creating foreground and background contrast
	1.4 L2 SC2: Text that is presented over a background pattern of lines which are within 500% +/- of the stem width of the characters or their serifs must have a contrast between the characters and the lines that is greater than X2, where the whiter element is at least Y2.
	1.4 L2 SC3: Users can disable background audio that plays automatically on a page so that it does not interfere with text reading software they may be using.
	1.4 L3 SC1: Text is not presented over any background (image, text, color or pattern), or if any background is present, the contrast between the text and the background is greater than X2. Related Techniques: HTML 10.13: Background images
	1.4 L3 SC2: Audio content does not contain background sounds or the background sounds are at least 20 decibels lower than the foreground audio content, with the exception of occasional sound effects.

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

Status	Success Criterion
	2.1 L1 SC1: All of the functionality of the content, where the functionality or its outcome can be described in a sentence, is operable through a keyboard or keyboard interface. Related Techniques: HTML 9.9: Keyboard access HTML 11.1: Use client side image map HTML 11.2: Text links for server side image maps. HTML 16.4: Keyboard shortcuts for directly accessible scripts SCRIPT 1.2: Images as submit buttons SCRIPT 2.3: Changing focus
	2.1 L2 SC1: Wherever a choice between input device event handlers is available and supported, the more abstract event is used. Related Techniques: HTML 16.5: Device dependent event handlers SCRIPT 2.4: Device-independent events SCRIPT 2.5: The onactivate event
	2.1 L3 SC1: All functionality of the content is designed to be operated through a keyboard or keyboard interface. Related Techniques: HTML 11.3: Redundant text links for client side image maps (deprecated)

Guideline 2.2 Allow users to control time limits on their reading or interaction.

Status	Success Criterion
	2.2 L1 SC1: Content is designed so that time-outs are not an essential part of interaction, or at least one of the following is true for each time-out that is a function of the content: Related Techniques: HTML 2.1: Meta redirect HTML 2.2: Meta refresh
	2.2 L2 SC1: A method is provided to stop content that blinks for more than 3 seconds. Related Techniques: HTML 5.4: Blink CSS 9.7: Underlining, overlining, and blinking
	2.2 L2 SC2: A method is provided to pause and/or permanently stop dynamic (moving or time-based) content. Related Techniques: HTML 5.5: Marquee Related Tests: Test 69: marquee element is not used.
	2.2 L3 SC1: With the exception of real-time events, content has been designed in a way that timing is not designed to be an essential part of the activity and any time limits in the content would pass level 1, success criteria 1 for this guideline.
	2.2 L3 SC2: Any non-emergency interruptions, such as the availability of updated content, can be postponed and/or suppressed by the user.

Guideline 2.3 Allow users to avoid content that could cause photosensitive epileptic seizures.

Status	Success Criterion
	2.3 L1 SC1: Content that violates international health and safety standards for general flash or red flash is marked in a way that the user can avoid its appearance.
	2.3 L2 SC1: Content does not violate international health and safety standards for general flash or red flash.
	2.3 L3 SC1: Content does not violate international health and safety standards for spatial pattern thresholds or red flash.

Guideline 2.4 Provide mechanisms to help users find content, orient themselves within it, and navigate through it.

Status	Success Criterion
	2.4 L1 SC1: Structures and relationships within the content can be programmatically determined.
	2.4 L2 SC1: Documents that have five or more section headings and are presented as a single delivery unit include a table of contents with links to important sections of the document. Related Techniques: GENERAL Table of contents HTML 2.3: Site map
	2.4 L2 SC2: There is more than one way to locate the content of each delivery unit, including but not limited to link groups, a site map, site search or other navigation mechanism. Related Techniques: GENERAL Site maps GENERAL Search engine as alternative navigation HTML 9.13: The link element and navigation tools
	2.4 L2 SC3: Blocks of repeated material, such as navigation menus and document headers, are marked up so that they can be bypassed by people who use assistive technology or who navigate via keyboard or keyboard interface. Related Techniques: GENERAL Repeated material HTML 9.5: Link groups HTML 9.6: tabindex to skip link groups (future) HTML 9.7: Skipping link groups HTML 9.8: Hide link groups HTML 10.10: ASCII art
	2.4 L3 SC1: When content is arranged in a sequence that affects its meaning, that sequence can be determined programmatically. Related Techniques: GENERAL Reading order HTML 2.4: Collection information HTML 8.4: Linear reading order of tables HTML 15.6: Tab order in forms
	2.4 L3 SC2: When a page or other delivery unit is navigated sequentially, elements receive focus in an order that follows relationships and sequences in the content. Related Techniques: GENERAL Tab order
	2.4 L3 SC3: Images have structure that users can access. Related Techniques: GENERAL Structured images
	2.4 L3 SC4: Delivery units have descriptive titles Related Techniques: GENERAL Page titles Related Tests: Test 50: Content contains a title element. Test 51: title contains text. Test 53: title is not placeholder text. Test 54: title is descriptive of the content.
	2.4 L3 SC5: Text is divided into paragraphs.
	2.4 L3 SC6: Documents are divided into hierarchical sections and subsections that have descriptive titles.

Guideline 2.5 Help users avoid mistakes and make it easy to correct them.

Status	Success Criterion
	2.5 L2 SC1: If a user error is detected, the error is identified and provided to the user in text.
	2.5 L2 SC2: If a user error is detected and suggestions for correction are known and can be provided without jeopardizing security or purpose, the error is identified and the suggestions are provided.
	2.5 L2 SC3: Where consequences are significant and time-response is not important, one of the following is true:
	2.5 L3 SC1: Where text entry is required for which there is a known set of less than 75 valid choices and they can be provided without jeopardizing security or purpose, users are allowed to select from a list of options as well as to type the data directly.
	2.5 L3 SC2: If possible for the natural language of the text, an option is provided to check text entries for misspelled words with suggestions for correct spellings.

Guideline 3.1 Ensure that the meaning of content can be determined.

Status	Success Criterion
	3.1 L1 SC1: The natural language of the document as a whole can be identified by automated tools. Related Techniques: HTML 4.1: Identifying the primary language CSS 5.1: Specifying the direction of text Related Tests: Test 48: Content has required lang attribute(s). Test 49: Content has valid language code.
	3.1 L1 SC2: The meaning of abbreviations and acronyms can be programmatically located. Related Techniques: HTML 5.2: Abbreviations HTML 5.3: Acronym
	3.1 L2 SC1: The meanings and pronunciations of all words in the content can be programmatically located. Related Techniques: HTML 1.4: Glossary HTML 5.10: Supplemental meaning cues
	3.1 L2 SC2: The meaning of all idioms in the content can be programmatically determined. Related Techniques: HTML 5.10: Supplemental meaning cues
	3.1 L2 SC3: For each foreign language passage or phrase in the body of the content, the language is identified through markup or other means. Foreign passages or phrases are passages or phrases that are in a language other than the primary language of the document. Related Techniques: HTML 4.2: Identifying changes in language
	3.1 L3 SC1: Where a word has multiple meanings and the intended meaning is not the first in the associated dictionary(s), then additional markup or another mechanism is provided for determining the correct meaning. Related Techniques: HTML 5.10: Supplemental meaning cues
	3.1 L3 SC2: Section headings and link text are understandable when read by themselves or as a group (for example, in a screen reader's list of links or a table of contents). Related Techniques: HTML 9.1: Link Text Related Tests: Test 195: Link text does not begin with "link to" or "go to" (English).
	3.1 L3 SC3: There is a statement associated with the content asserting that the Strategies for Reducing the Complexity of Content (the following list) were considered.

Guideline 3.2 Organize content consistently from "page to page" and make interactive components behave in predictable ways.

Status	Success Criterion
	3.2 L1 SC1: Any extreme change of context is implemented in a manner that can be programmatically identified. Related Techniques: HTML 9.12: Opening new windows
	3.2 L2 SC1: Components that are repeated on multiple "pages" within a resource or a section of a resource occur in the same sequence each time they are repeated, for at least one presentation format. Related Techniques: CSS 5.2: Creating layout, positioning, layering, and alignment CSS 9.3: Indenting text
	3.2 L2 SC2: All user interface components should be able to receive focus without causing activation.
	3.2 L2 SC3: Changing the setting of any input field should not automatically cause an extreme change in context such as leaving the "page." Related Techniques: HTML 16.7: Auto submit combo boxes Related Tests: Test 92: All select elements do not cause an extreme change in context.
	3.2 L2 SC4: Interactive elements that appear on multiple "pages," including graphical elements, are associated with the same functionality wherever they appear. Related Techniques: HTML 9.10: Anchors and targets HTML 9.11: Using frame targets (deprecated)
	3.2 L2 SC5: Explicit notice is given in advance of any extreme change of context.
	3.2 L2 SC6: The destination of each link is identified through words or phrases that either occur in the link or can be programmatically determined. Related Techniques: HTML 9.2: Supplement link text with the title attribute HTML 9.3: Text for images used as links HTML 9.4: Image and text links side by side HTML 11.1: Use client side image map HTML 11.2: Text links for server side image maps. HTML 11.4: Text alternatives for client-side image maps Related Tests: Test 65: Alt text for all area elements identifies the link destination. Test 174: Each source anchor contains text. Test 197: All source anchors contain text that identifies the link destination. Test 19: Link text is meaningful when read out of context.
	3.2 L3 SC1: Graphical components that appear on multiple pages, including graphical links, are associated with the same text equivalents wherever they appear.
	3.2 L3 SC2: Components that appear visually on multiple pages, such as navigation bars, search forms, and sections within the main content, are displayed in the same location relative to other content on every page or screen where they appear.
	3.2 L3 SC3: When components such as navigation menus and search forms appear on multiple pages, users can choose to have those elements presented in a different visual position or reading-order.
	3.2 L3 SC4: There are no extreme changes of context.

Guideline 4.1 Use technologies according to specification.

Status	Success Criterion
	4.1 L1 SC1: Except where the site has documented that a specification was violated for backward compatibility or compatibility with assistive technology, the technology has: Related Techniques: HTML 1.1: The !doctype statement HTML 1.2: The title element HTML 3.2: Header misuse HTML 5.12: Use non-deprecated presentational markup HTML 8.1: Layout tables (deprecated) HTML 8.2: Table structure in layout tables HTML 10.3: Misuse of alternative text HTML 12.9: Embedding multimedia objects SCRIPT 1.1: Form URIs Related Tests: Test 29: HTML Content has a valid doctype declaration. Test 3: All Alt text is short.
	4.1 L3 SC1: Technologies are used according to specification without exception. Related Techniques: HTML 5.4: Blink HTML 5.5: Marquee HTML 5.8: Misuse of blockquote HTML 6.2: Abuse of list markup HTML 7.9: Misuse of the pre element CSS 10.1: Displaying empty table cells

Status

Success Criterion

4.1 L1 SC1: Except where the site has documented that a specification was violated for backward compatibility or compatibility with assistive technology, the technology has:

Related Techniques:

HTML 1.1: The !doctype statement
HTML 1.2: The title element
HTML 3.2: Header misuse
HTML 5.12: Use non-deprecated presentational markup
HTML 8.1: Layout tables (deprecated)
HTML 8.2: Table structure in layout tables
HTML 10.3: Misuse of alternative text
HTML 12.9: Embedding multimedia objects
SCRIPT 1.1: Form URIs

Related Tests:

Test 29: HTML Content has a valid doctype declaration.
Test 3: All Alt text is short.

4.1 L3 SC1: Technologies are used according to specification without exception.

Related Techniques:

HTML 5.4: Blink
HTML 5.5: Marquee
HTML 5.8: Misuse of blockquote
HTML 6.2: Abuse of list markup
HTML 7.9: Misuse of the pre element
CSS 10.1: Displaying empty table cells

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

Status	Success Criterion
	4.2 L1 SC1: At least one user agent supporting the content conforms to at least the default set of conformance requirements of the User Agent Accessibility Guidelines (UAAG) 1.0 at Level A plus the sets of requirements (a) through (i) (below) that apply. If required plug-ins are not accessible, an alternative solution is provided that conforms to WCAG 2.0. If inaccessible plug-ins are available, then a method for obtaining an accessible plug-in is provided from the content. Related Techniques: HTML 12.10: Plugin viewers HTML 14.5: Frame sources SCRIPT 2.1: javascript: URIs SCRIPT 2.2: Dynamic content generation
	4.2 L1 SC2: Any programmatic user interface components of the content conform to at least the default set of conformance requirements of the UAAG 1.0 at Level A plus the sets of requirements (a) through (i) (below) that apply. If the custom user interfaces cannot be made accessible, an alternative solution is provided that meets WCAG 2.0 (including this provision) to the level claimed.
	4.2 L2 SC1: Accessibility conventions of the markup or programming language (API's or specific markup) are used. Related Techniques: CSS 5.5: Creating Invisible labels for form elements
	4.2 L3 SC1: The Web resource includes a list of the technologies user agents must support in order for its content to work as intended. The list is documented in metadata if such metadata is supported by the format, otherwise it is documented in a policy statement associated with the content.
	4.2 L3 SC2: Users who do not have one or more of these technologies can still access and use the resource, though the experience may be degraded. Related Techniques: CSS 1.1: Using em or percent for properties that need to change CSS 1.2: Using px for properties that do not need to be changed CSS 5.2: Creating layout, positioning, layering, and alignment CSS 9.3: Indenting text
	4.2 L3 SC3: Technologies and features on the required list are open standards or have a public specification.

There are a total of 13 guidelines and 77 success criteria in the 11 February 2005 Working Draft.