WCAG 2.0 Success Criteria for HTML techniques

This document shows WCAG guidelines for the HTML techniques.

HTML Technique	Guideline	Notes
Uncategorized techniques
1.1: Use of the title attribute
1.2: Meta redirect	Content is designed so that time limits are not an essential part of interaction, or at least one of the following is true for each time limit: (Level 1)
1.3: Meta refresh	Content is designed so that time limits are not an essential part of interaction, or at least one of the following is true for each time limit: (Level 1)
Metadata
2.1: The title element.	There is a statement associated with the content asserting that items from the following list were considered: (Level 3)	Technique should be at least level 2.
2.2: The address element		Is this technique needed?
2.3: The !doctype statement		There should be a success criterion under 4.1 that the machine language of the content can be unambiguously and automatically determined.
2.4: The link element and navigation tools	In documents greater than 50,000 words or sites larger than 50 perceived pages, at least one of the following is provided. (Level 2)
2.5: The link element and alternative documents		Do we want any guidelines about alternative resources being acceptable ways to claim conformance, or are we explicitly avoiding that? If so, perhaps we should have a guideline saying that?
Structural Grouping
3.1: Section headings	Structures and relationships within the content can be derived programmatically. (Level 1)
3.2: Style headers	Different structural elements look or sound different from each other and from body text. (Level 2)
Language
4.1: Identifying the primary language	The natural language of the document as a whole can be identified by automated tools. (Level 1)
4.2: Identifying changes in language	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. (Level 2)
Text Markup
5.1: Emphasis	Emphasis can be derived programmatically. (Level 1)
5.2: Abbreviations	The meaning of abbreviations and acronyms can be programmatically located. (Level 1)	Unsure if this needs to be Level 1.
5.3: Acronym	The meaning of abbreviations and acronyms can be programmatically located. (Level 1)	Unsure if this needs to be Level 1.
5.4: Short Quotations (future)	Structures and relationships within the content can be derived programmatically. (Level 1)	Unsure if this needs to be Level 1.
5.5: Long Quotations	Structures and relationships within the content can be derived programmatically. (Level 1)	Unsure if this needs to be Level 1.
5.6: Misuse of blockquote	Technologies are used according to specification without exception. (Level 3)	Unsure if this needs to be Level 1.
5.7: Markup and style sheets rather than images: The example of math	Structures and relationships within the content can be derived programmatically. (Level 1)
5.8: Eight other structural elements (to identify citations, code fragments, deleted text, and others)	Structures and relationships within the content can be derived programmatically. (Level 1)	Unsure if this needs to be Level 1.
Lists
6.1: Ordered lists	Structures and relationships within the content can be derived programmatically. (Level 1)
6.2: Use style sheets to change list bullets		Somehow we need a hook for techniques like this, even though it's just an expansion of the "use markup properly" requirement. We could map to that guideline, but not sure if that's the intent.
Data Tables
7.1: The caption element	Structures and relationships within the content can be derived programmatically. (Level 1)	Not sure if caption is a structure, but at least it's like a header, so I mapped it here.
7.2: The title attribute on the table element		The title attribute (with the exception of link titles) is a mess, I really don't see how it maps to any guidelines, and am not sure what guideline I would propose to map it to. But we need something to deal with this, we have to have title techniques (even if they are "don't use this, it's too confusing") or there will be a real mess out there.
7.3: Summarizing tables		We definately need a success criterion for this. Since this technique is about describing structure, rather than providing structure in markup, I didn't think it belonged with the existing structure guidelines.
7.4: Terse substitutes for header labels		This particular HTML feature has always annoyed me. It's the reverse of the <abbr> element. But if we want this technique, we'll need a success criterion that says "provide a contraction for long things" to complement the one that says "provide an expansion for short things".
7.5: Identifying groups of rows	Structures and relationships within the content can be derived programmatically. (Level 1)
7.6: Identifying groups of columns	Structures and relationships within the content can be derived programmatically. (Level 1)
7.7: Specifying the set of data cells for which each header cell provides header information.	Structures and relationships within the content can be derived programmatically. (Level 1)
7.8: Associating header cells with data cells.	Structures and relationships within the content can be derived programmatically. (Level 1)
7.9: Categorizing data cells.	Structures and relationships within the content can be derived programmatically. (Level 1)
7.10: Misuse of the pre element.	Technologies are used according to specification without exception. (Level 3)
7.11: Row and column headings.	Structures and relationships within the content can be derived programmatically. (Level 1)
Tables for layout
8.1: Table elements allowed in layout tables	Except where the site has documented that a specification was violated for backward compatibility or compatibility with assistive technology, the technology has: (Level 1)
8.2: Summaries of layout tables		This technique basically says "don't annoy screen reader users with frivolous summaries like 'this is a layout table'". We need a success criterion for things like that, I think. Something like "the road to inaccessibility is paved with good intentions."
8.3: Linear reading order of tables	Information is provided that would indicate at least one logical sequence in which to read a document. (Level 3)	This was the best place I could think to map this technique, but I think it should be level 1.
Links
9.1: Supplement link text with the title attribute.	The target of each link is clearly identified. (Level 3)
9.2: Text for images used as links	The target of each link is clearly identified. (Level 3)
9.3: Image and text links side by side	The target of each link is clearly identified. (Level 3)
9.4: Link Groups	Large blocks of material that are repeated on multiple pages, such as navigation menus with more than 8 or more links, can be bypassed by people who use screen readers or who navigate via keyboard or keyboard interface. (Level 2)
9.5: tabindex to skip link groups (future)	Large blocks of material that are repeated on multiple pages, such as navigation menus with more than 8 or more links, can be bypassed by people who use screen readers or who navigate via keyboard or keyboard interface. (Level 2)
9.6: Skipping Link Groups	Large blocks of material that are repeated on multiple pages, such as navigation menus with more than 8 or more links, can be bypassed by people who use screen readers or who navigate via keyboard or keyboard interface. (Level 2)
9.7: Hide link groups	Large blocks of material that are repeated on multiple pages, such as navigation menus with more than 8 or more links, can be bypassed by people who use screen readers or who navigate via keyboard or keyboard interface. (Level 2)
9.8: Keyboard access	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. (Level 1)
9.9: Anchors and targets	Any extreme change of context is implemented in a manner that can be programmatically identified. (Level 1)
9.10: Using FRAME targets (deprecated)	Any extreme change of context is implemented in a manner that can be programmatically identified. (Level 1)
Images
10.1: Short text equivalents for img elements ("alt-text")	Text-equivalents are explicitly associated with non-text content, except when the non-text content is intended to create a specific sensory experience (for example, music without words and visual art). (Level 1)
10.2: Image titles		Another title technique. Though this one says "don't use them because they confuse things".
10.3: Short text equivalents for object elements ("alt-text")	Text-equivalents are explicitly associated with non-text content, except when the non-text content is intended to create a specific sensory experience (for example, music without words and visual art). (Level 1)
10.4: Long descriptions of images	A text document (for example, a movie script) is provided that includes all important visual information, dialogue, and other important sounds. (Level 3)
10.5: Long description of objects	A text document (for example, a movie script) is provided that includes all important visual information, dialogue, and other important sounds. (Level 3)
10.6: D links (deprecated)	A text document (for example, a movie script) is provided that includes all important visual information, dialogue, and other important sounds. (Level 3)
10.7: Describe images without longdesc	A text document (for example, a movie script) is provided that includes all important visual information, dialogue, and other important sounds. (Level 3)
10.8: ASCII art	Diagrams are constructed so that they have structure that users can access. (Level 3)
10.9: Emoticons		I didn't see any good success criterion for emoticons and other text abuses.
Image Maps
11.1: Use Client Side Image Map	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. (Level 1) The target of each link is clearly identified. (Level 3)
11.2: Provide text links for server side image maps.	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. (Level 1) The target of each link is clearly identified. (Level 3)
11.3: Provide redundant text links for client side image map.	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. (Level 1) All of the functionality of the content is operable via a keyboard or keyboard interface. (Level 3)
11.4: Provide alt for area.	The target of each link is clearly identified. (Level 3)
Programmatic objects and applets
12.1: Text and non-text equivalents for applets and programmatic objects	Non-text content that is designed to create a specific sensory experience (such as music without words or visual art) has a text label or a text description explicitly associated with it. (Level 1)
12.2: Alt content for embed	A text document (for example, a movie script) is provided that includes all important visual information, dialogue, and other important sounds. (Level 3)
12.3: Alt text for embed	Non-text content that is designed to create a specific sensory experience (such as music without words or visual art) has a text label or a text description explicitly associated with it. (Level 1)
12.4: Embedding multimedia objects	Except where the site has documented that a specification was violated for backward compatibility or compatibility with assistive technology, the technology has: (Level 1)
Frames
13.1: Providing a frame title	Facilitate the ability of users to orient themselves and move within the content.	There didn't seem to be success criteria for FRAMEs, but it's pretty clearly related to this guideline.
13.2: Describing frame relationships (deprecated)	Facilitate the ability of users to orient themselves and move within the content.	There didn't seem to be success criteria for FRAMEs, but it's pretty clearly related to this guideline.
13.3: Writing for browsers that do not support FRAME	Text-equivalents are explicitly associated with non-text content, except when the non-text content is intended to create a specific sensory experience (for example, music without words and visual art). (Level 1)
13.4: Frame sources	At least one plug-in required to access 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 (j) (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. (Level 1)
13.5: Descriptive links for inaccessible frame source.	A text document (for example, a movie script) is provided that includes all important visual information, dialogue, and other important sounds. (Level 3)
13.6: Alternative content for iframe	A text document (for example, a movie script) is provided that includes all important visual information, dialogue, and other important sounds. (Level 3)
13.7: Longdesc for iframe	A text document (for example, a movie script) is provided that includes all important visual information, dialogue, and other important sounds. (Level 3)
Forms
14.1: Explicit form labels		I didn't see any guidelines or success criteria about forms.
14.2: Implicit labels for form controls (deprecated)		I didn't see any guidelines or success criteria about forms.
14.3: The title attribute to label form controls.		I didn't see any guidelines or success criteria about forms.
14.4: Grouping form controls		I didn't see any guidelines or success criteria about forms.
14.5: Grouping options of select elements		I didn't see any guidelines or success criteria about forms.
14.6: Tab order in forms	Logical tab order has been created. (Level 3)
14.7: Text equivalents for submit buttons	Non-text content that is designed to create a specific sensory experience (such as music without words or visual art) has a text label or a text description explicitly associated with it. (Level 1)
14.8: Place-holding characters in empty controls (deprecated)
Script techniques
15.1: Keyboard shortcuts for directly accessible scripts.	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. (Level 1)
15.2: Device independent event handlers	Wherever a choice between input device event handlers is available and supported, the more abstract event is used. (Level 2)