Team A TO DO List.

From: Gregg Vanderheiden <gv@trace.wisc.edu> · Date: Thu, 29 Dec 2005 11:07:54 -0600

Team A

We are assigned with guideline 1.1

We need to be sure that we have at least one techniques/test doc for part of
one solution for each situation in each success criterion.    I have listed
the relevant section from our Understanding Doc below.  

I have marked one in each with yellow highlight and [Candidate]

The others are marked in Blue and [Alternate]

As you can see there are many techniques that are repeated in different
success criterion.  I have marked them {DUPLICATES}.  We only need to do
them once.

I have also marked the 'common failures'.    This goes beyond our "one way
to succeed" but if we think they are important we should do them too.  But
do them LAST .

We have 23   - most of them pretty straightforward.     3 of the 23 are
'common failures'. 

Please let me know which ones each of you can work on.  Post your choices to
the  TEAM-A list so we can all see and chose other ones. 

Gregg

1.1.1 For non-text
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20051123/appendixA.html#non-text-
content-informdef>  content that is used to convey information, text
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20051123/appendixA.html#text-altd
ef>  alternatives identify the non-text
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20051123/appendixA.html#non-text-
contentdef>  content and convey the same information. For multimedia
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20051123/appendixA.html#multimedi
adef> , provide a text-alternative that identifies the multimedia. For live
audio-only and live video-only, conform to success
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/#text-equi
v-live-media>  criterion 1.1.5. (Level 1) 

Note: For requirements for synchronized alternatives for multimedia refer to
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/#media-equ
iv> Provide synchronized alternatives for multimedia.: 

Situation A: If all information in non-text content can be conveyed in a
short description, the following would be sufficient:

*         Providing short text alternatives using a technology-specific
technique listed below. [Candidate]

Situation B: If all information in non-text content (except for multimedia)
can not be conveyed in a short description (e.g. a chart or diagram), the
following would be sufficient:

*         Providing short text alternatives using a technology-specific
technique listed below AND one of the following techniques for long
description:

1.      Providing long descriptions using a technology-specific technique
listed below. [Candidate]

2.      Providing
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  a long description in text adjacent to the non-text content
with a reference to the location of the long description in the short
description.   [Alternate]

3.      Providing
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  a long description in another location with a link to it that
is immediately adjacent to the non-text content with a reference to the link
in the short description. [Alternate]

Technology-Specific Techniques 

Providing short text alternatives in HTML

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-HTML-TECHS-20051123/Overview.html
#H45>  alt attributes on img elements.   [Candidate]

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-HTML-TECHS-20051123/Overview.html
#H63>  alt attributes on applet elements. [Candidate]

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-HTML-TECHS-20051123/Overview.html
#H48>  the body of the object element. [Candidate]

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-HTML-TECHS-20051123/Overview.html
#H62>  the body of the applet element. [Candidate]

Providing long descriptions in HTML

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  longdesc . [Candidate]

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-HTML-TECHS-20051123/Overview.html
#H64>  noembed with embed .   [Candidate]

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-HTML-TECHS-20051123/Overview.html
#H48>  the body of the object element. [Candidate]

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  the body of the applet element. [Candidate]

Common Failures Identified by the Working Group 

The following are common mistakes which are considered failures of this
success criterion by the working group.

*         Failure
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  due to using text alternatives that aren't alternatives (e.g.
filenames or placeholder text). [Candidate]

  _____  

How to Meet Success Criterion 1.1.2

1.1.2 For non-text
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20051123/appendixA.html#non-text-
content-functionaldef>  content that is functional, text
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20051123/appendixA.html#text-altd
ef>  alternatives serve the same purpose as the non-text content. If text
alternatives can not serve the same purpose as the functional non-text
content, text alternatives identify the purpose of the functional non-text
content (Level 1) 

Situation A: If text alternatives can serve the same purpose as the
functional non-text content:, the following would be sufficient:

*         Providing a text alternative that serves the same purpose as the
non-text content, using one of the technology-specific techniques below.
[Candidate]

Situation B: If text alternatives can not serve the same purpose as the
functional non-text content, the following would be sufficient:

*         Providing a text alternative that identifies the purpose of the
functional non-text content, using one of the technology-specific techniques
below. [Candidate]

Technology-Specific Techniques 

Providing short text alternatives in HTML

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  alt attributes on images used as submit buttons. [Candidate]

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  alt attributes on img elements used as links. [Candidate]

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  alt attributes on applet elements.   {DUPLICATE}

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  the body of the object element. {DUPLICATE}

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  the body of the applet element. {DUPLICATE}

Providing long descriptions in HTML

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  longdesc . {DUPLICATE}

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  noembed with embed . {DUPLICATE}

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  the body of the object element. {DUPLICATE}

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  the body of the applet element. {DUPLICATE}

Common Failures Identified by the Working Group 

The following are common mistakes which are considered failures of this
success criterion by the working group.

*         Failure
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  due to using text alternatives that aren't alternatives (e.g.
filenames or placeholder text). {DUPLICATE}

  _____  

How to Meet Success Criterion 1.1.3

1.1.3 For non-text
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20051123/appendixA.html#non-text-
content-sensoryexpdef>  content that is intended to create a specific
sensory experience, text
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20051123/appendixA.html#text-altd
ef>  alternatives at least identify the non-text content with a descriptive
label. (Level 1) 

Techniques for Addressing Success Criterion 1.1.3

The following combinations of techniques are deemed to be sufficient by the
WCAG Working Group for meeting success criterion 1.1.3.

*         Providing the descriptive name or the name the artist (or another)
gave to the non-text content [Candidate], using a technology-specific
technique for providing short text alternatives listed below.

Technology-Specific Techniques 

Providing short text alternatives in HTML

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  alt attributes on img elements. {DUPLICATE}

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  alt attributes on applet elements. {DUPLICATE}

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  the body of the object element. {DUPLICATE}

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  the body of the applet element. {DUPLICATE}

Common Failures Identified by the Working Group 

The following are common mistakes which are considered failures of this
success criterion by the working group.

*         Failure
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  due to using text alternatives that aren't alternatives (e.g.
filenames or placeholder text). {DUPLICATE}

How to Meet Success Criterion 1.1.4

1.1.4 Non-text
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20051123/appendixA.html#non-text-
contentdef>  content that is not functional
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20051123/appendixA.html#functiond
ef> , is not used to convey information, and does not create a specific
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20051123/appendixA.html#non-text-
content-sensoryexpdef>  sensory experience is implemented such that it can
be ignored by assistive technology. (Level 1) 

Techniques for Addressing Success Criterion 1.1.4

The following combinations of techniques are deemed to be sufficient by the
WCAG Working Group for meeting success criterion 1.1.4.

*         Marking the non-text content using one of the technology-specific
techniques listed below. [Candidate]

Editorial Note: Not all mechanisms for including non-text content have a
convention similar to empty alt for img elements (object and embed are two
examples). Are there additional strategies/techniques for addressing this
criterion that should be included here to address this?

Technology-Specific Techniques 

HTML Techniques

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  null alt text and no title attribute on img elements for spacer
images.  [Candidate]

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  null alt text and no title attribute on img elements for images
that are purely decorative. [Candidate]

CSS Techniques

*         Including
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  background images with CSS. [Alternate]

Common Failures Identified by the Working Group 

The following are common mistakes which are considered failures of this
success criterion by the working group.

*         Failure
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  due to providing a text alternative that is not null. (e.g..
alt="spacer" or alt="image" ). [Candidate]

  _____  

How to Meet Success Criterion 1.1.5

1.1.5 For live
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20051123/appendixA.html#live-audi
o-onlydef>  audio-only or video-only
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20051123/appendixA.html#live-vide
o-onlydef>  content, text
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20051123/appendixA.html#text-altd
ef>  alternatives at least identify the purpose of the content with a
descriptive label. (Level 1) 

Note: Refer to
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/#media-equ
iv> Provide synchronized alternatives for multimedia.: for guidance on
content that combines live audio and video. 

Techniques for Addressing Success Criterion 1.1.5

The following combinations of techniques are deemed to be sufficient by the
WCAG Working Group for meeting success criterion 1.1.5.

*         Providing a descriptive label that describes the purpose of live
audio-only and live video-only content, using a technology-specific
technique listed below. [Candidate]

Technology-Specific Techniques 

Providing short text alternatives in HTML

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  alt attributes on img elements. {DUPLICATE}

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  alt attributes on applet elements. {DUPLICATE}

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  the body of the object element. {DUPLICATE}

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  the body of the applet element. {DUPLICATE}

Common Failures Identified by the Working Group 

The following are common mistakes which are considered failures of this
success criterion by the working group.

*         Failure
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  due to using text alternatives that aren't alternatives (e.g.
filenames or placeholder text). {DUPLICATE}

  _____  

How to Meet Success Criterion 1.1.6

1.1.6 For prerecorded multimedia content, a combined document containing
both captions
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20051123/appendixA.html#captionsd
ef>  and transcripts of audio
<http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20051123/appendixA.html#audiodesc
def>  descriptions of video is available. (Level 3) 

Techniques for Addressing Success Criterion 1.1.6

The following combinations of techniques are deemed to be sufficient by the
WCAG Working Group for meeting success criterion 1.1.6.

*         Providing
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  a collated script of captions and audio descriptions
[Candidate]AND one of the following:

o        placing
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  a link to the script immediately next to the non-text content;
[Candidate]

o        linking to a collated script, using a technology-specific technique
listed below. [Alternate]

Technology-Specific Techniques 

Linking to a collated script in HTML

*         Using
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  noembed with embed . [Alternate]

*         Providing
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  alternatives for object. [Alternate]

Common Failures Identified by the Working Group 

The following are common mistakes which are considered failures of this
success criterion by the working group.

*         Failure
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20051123/tech-place
holder.htm>  due to not collating captions and audio descriptions (for
example, first section includes a transcript of captions, second section
includes a transcript of audio descriptions). [Candidate]

Gregg

------------------------

Gregg C Vanderheiden Ph.D. 
Professor - Depts of Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 
< <http://trace.wisc.edu/> http://trace.wisc.edu/> FAX 608/262-8848  
For a list of our list discussions http://trace.wisc.edu/lists/

 <http://trace.wisc.edu:8080/mailman/listinfo/>  