Map HTML Techniques for WCAG 2.0 to WCAG 2.0 Success criteria

HTML Techniques used: http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-HTML-TECHS-20031105.html
WCAG 2.0 Version used: http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20031117.html

The following is the HTML techniques as they appear in the above document. The mapping(s) to WCAG 2.0 follow the title of the technique. The mapping is formatted as several numbers separated by decimal points. The first position refers to the Principle, the second the Guideline, the third the Success Criterion, and the fourth a paragraph within the Success Criterion.

• 1 - Uncategorized techniques
  • 1.1 - Use of the title attribute: no mapping, maybe technique not needed (specific uses of title covered elsewhere)
  • 1.2 - Meta redirect: 3.4.2.3
  • 1.3 - Meta refresh: 3.4.2.3
• 2 - Metadata
  • 2.1 - The title element: 2.4.1.x – need to create a success criterion
  • 2.2 - The address element: 1.3.1.1 – but we should remove this as it’s not applicable to accessibility, or add it to the “other structural elements” category
  • 2.3 - The !doctype statement: 4.1.1.1
  • 2.4 - The link element and navigation tools: 2.4.2.1.c
  • 2.5 - The link element and alternative documents: ? – unsure if WCAG 1.0 checkpoint 11.4 should make its way into WCAG 2.0
• 3 - Structural Grouping
  • 3.1 - Section headings: 1.3.1.1.a
  • 3.2 - Style headers1.3.x.x – need success criterion
• 4 - Language
  • 4.1 - Identifying changes in language: 3.1.1.1
  • 4.2 - Identifying the primary language: 3.1.x.x – see ednote for technique
• 5 - Text Markup
  • 5.1 - Emphasis: 1.3.1.1.c
  • 5.2 - Abbreviations: 1.4.2.1 or 3.2.x.x – two checkpoints say the same thing, needs to be resolved
  • 5.3 - Acronym: same as above
  • 5.4 - Short Quotations (@@ future): 1.3.1.1.x – the sub-points in this success criterion don’t really cover quotes
  • 5.5 - Long Quotations: same as above
  • 5.6 - Misuse of blockquote: 4.1.1.1.b
  • 5.7 - Markup and style sheets rather than images: The example of math: no mapping, and should move to gateway techniques
  • 5.8 - Eight other structural elements (to identify citations, code fragments, deleted text, and others): 4.1.1.1.b – but we may remove this one as it’s not really applicable to accessibility
• 6 - Lists
  • 6.1 - Ordered lists: 1.3.1.1a and 2.4.3.2 (issue: the example shows a case where information would be lost if CSS were turned off)
  • 6.2 - Use style sheets to change list bullets: 1.3.1.1a
• 7 - Data Tables
  • 7.1 - The caption element 3.3.3.11 (this one is optional – are mappings needed in these cases?)
  • 7.2 - The title attribute on the table element: 3.3.3.11  (this is a what not to do technique, not sure it should be mapped, but could be with 4.1.1.1b)
  • 7.3 - Summarizing tables: 3.3.3.11
  • 7.4 - Terse substitutes for header labels: 2.4.????
  • 7.5 - Identifying groups of rows: 2.4.????
  • 7.6 - Identifying groups of columns 2.4.???? these three – 7.3-7.6 -- seem to fit best in 2.4, but don’t clearly map to any existing success criteria. Might be possible to say they map to 1.3.1.1b as well.
  • 7.7 - Specifying the set of data cells for which each header cell provides header information.: 1.3.1.1b
  • 7.8 - Associating header cells with data cells.: 1.3.1.1b
  • 7.9 - Categorizing data cells. : 1.3.1.1b
  • 7.10 - Misuse of the pre element. : 4.1.1.1b
  • 7.11 - Row and column headings. : 1.3.1.1b  and/or 4.1.1.1b
• 8 - Tables for layout
  • 8.1 - Table elements allowed in layout tables: 4.1.1.1b (note that there is a missing space after “tr” in the task on this one)
  • 8.2 - Summaries of layout tables: this one seems to be a special case in that it is driven more by user agent issues then it is by guidelines or success criteria.
  • 8.3 - Linear reading order of tables: 2.4.3.2
• 9 - Links
  • 9.1 - Supplement link text with the title attribute.  3.3.3.1.11
  • 9.2 - Text for images used as links 1.1.1.1
  • 9.3 - Image and text links side by side  3.4.3.2 (?) (#9?? Could argue that this is an “unusual interface feature that could confuse first-time users)
  • 9.4 - Link Groups 2.4.2.2
  • 9.5 - tabindex to skip link groups (@@ future) 2.4.2.2
  • 9.6 - Skipping Link Groups 2.4.2.2
  • 9.7 - Hide link groups  2.4.2.2
  • 9.8 - Keyboard access 2.1.1.1
  • 9.9 - Anchors and targets  3.4.2.3.B (3.4.2.3.A currently has no techniques – we should create a list of success criteria and guidelines for which there are no techniques once this mapping has been completed)
  • 9.10 - Using FRAME targets (@@ deprecated) 3.4.2.3.B
• 10 - Images
  • 10.1 - Short text equivalents for img elements ("alt-text")  1.1.1.1
  • 10.2 - Image titles (4.1.1.B)
  • 10.3 - Short text equivalents for object elements ("alt-text") 1.1.1.(2) or (1) (we need to log UA issues on this – technique does not work reliably)
  • 10.4 - Long descriptions of images  1.1.1.1
  • 10.5 - Long description of objects 1.1.1.1
  • 10.6 - D links (@@ deprecated)  1.1.1.1 (gone)
  • 10.7 - Describe images without longdesc 1.1.1.1
  • 10.8 - ASCII art 2.4.2.2 (this success criteria may need to be expanded to include nonsensical material)
  • 10.9 - Emoticons    3.3.2.1.A     or ( 3.2.1???) (somewhat weak mappings, may also fit under 1.4.2.2 if emoticons can be equated to symbols)
• 11 - Image Maps
  • 11.1 - Use Client Side Image Map 2.1.1 (or 2.4.1.?  or 4.1.1.C?)
  • 11.2 - Provide text links for server side image maps. 1.1.1.1
  • 11.3 - Provide redundant text links for client side image map. 1.1.1.1, 2.1.1.1
  • 11.4 - Provide alt for area. 1.1.1.1
• 12 - Programmatic objects and applets
  • 12.1 - Text and non-text equivalents for applets and programmatic objects: 1.1.1.1, 1.1.1.2
  • 12.2 - Alt content for embed: 1.1.1.1, 1.1.1.2
  • 12.3 - Alt text for embed: 1.1.1.1, 1.1.1.2
  • 12.4 - Embedding multimedia objects: 4.1.1.1 – issue that this really “reverse-maps”
• 13 - Frames – need to discuss with larger group
  • 13.1 - Providing a frame title: 2.4.1.x
  • 13.2 - Describing frame relationships (@@ deprecated): 2.4.3.e
  • 13.3 - Writing for browsers that do not support FRAME: 2.4.2.1.e, 2.4.3.2, 4.3.2.1? – issue of requiring support for technology for accessibility
  • 13.4 - Frame sources: 4.3.2.1
  • 13.5 - Descriptive links for inaccessible frame source: ~4.3.2.1
  • 13.6 - Alternative content for iframe: 4.x.x.x, ~1.1.1.1
  • 13.7 - Longdesc for iframe: 2.4.3.e
• 14 - Forms
  • 14.1 - Tab order in forms: 2.4.3.4
  • 14.2 - Grouping form controls: ~2.4.2.2, ~2.4.3.1.x
  • 14.3 - Grouping options of select elements: ~2.4.3.1.x, 1.3.1.b (but shouldn’t be level 1)
  • 14.4 - Labeling form controls: 1.3.1.b
  • 14.5 - Place-holding characters in empty controls (@@ super-deprecated): 4.1.1.c
  • 14.6 - Text equivalents for submit buttons: 1.3.1.b