RE: Proposed reorganisation of media accessibility [ related to issue 2393]

I do no see this in this week's survey, so I am responding to the list.
 
On the call last week I brought up the following examples (expanded a
little here).  I am a little concerned that the current wording for the
success criteria and definitions do not sufficiently reflect these usage
cases.  Per the call, there seemed to be agreement that these were all
situations where descriptive identification of the non-text content was
appropriate.

*	
	Images that visually reflect extra-sensory experiences (e.g.,
x-ray, sonogram, MRI).
*	
	Test *results* that must be presented visually because that is
the only way we know how to capture the information (e.g., EKG,
seismograph, lie-detector).
*	
	Live video-only content (e.g., weather or traffic camera, a
self-running game-of-life).

 
I believe there may be further gray areas, for example hand writing,
graffiti, and other text-heavy artwork.
 
My proposal for resolving this is to include each of the above example
into the Understanding document.  We may need to discuss which SC to
associate each with.  We added an SC for live audio-only.  I think we
may need an SC for video-only (recorded or not).  As with the web-cam
examples above, descriptive identification is sometimes enough, but
sometimes captioning or a full transcript would be required.

________________________________

From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On
Behalf Of Gregg Vanderheiden
Sent: Wednesday, March 05, 2008 12:53 AM
To: w3c-wai-gl@w3.org
Subject: Proposed reorganisation of media accessibility [ related to
issue 2393]



 Based on last weeks discussion - a revised reorganization is provided
below


 

This version pulls language from TEITAC that makes our provisions read a
bit better.

 

[snip]

 

1.1.1 Non-text Content: All non-text content
<http://www.w3.org/WAI/GL/WCAG20/#non-text-contentdef>  that is
presented to the user has a text alternative
<http://www.w3.org/WAI/GL/WCAG20/#text-altdef>  that presents equivalent
information, except for the situations listed below. (Level A) How to
Meet 1.1.1
<http://www.w3.org/WAI/WCAG20/quickref/20071218/Overview.php#qr-text-equ
iv-all>  Understanding 1.1.1
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20071218/text-e
quiv-all.html> 

*	Controls, Input: If non-text content is a control or accepts
user input, then it has a name
<http://www.w3.org/WAI/GL/WCAG20/#namedef>  that describes its purpose.
(See also Guideline 4.1 <http://www.w3.org/WAI/GL/WCAG20/#ensure-compat>
.) 

*         Media: If non-text content is media then text alternatives at
least provide descriptive identification of the non-text content. (See
Guideline 1.2 for additional requirements for media.)

*	Test: If non-text content is a test or exercise that must be
presented in non-text format
<http://www.w3.org/WAI/GL/WCAG20/#must-nontextdef> , then text
alternatives at least provide descriptive identification of the non-text
content. 
*	Sensory: If non-text content is primarily intended to create a
specific sensory experience
<http://www.w3.org/WAI/GL/WCAG20/#sensoryexpdef> , then text
alternatives at least provide descriptive identification of the non-text
content. 
*	CAPTCHA <http://www.w3.org/WAI/GL/WCAG20/#CAPTCHAdef> : If the
purpose non-text content is to confirm that content is being accessed by
a person rather than a computer, then text alternatives that identify
and describe the purpose of the non-text content are provided, and
alternative forms of CAPTCHA using output modes for different types of
sensory perception are provided to accommodate different disabilities. 
*	Decoration, Formatting, Invisible: If non-text content is pure
decoration <http://www.w3.org/WAI/GL/WCAG20/#puredecdef> , or used only
for visual formatting, or if it is not presented to users, then non-text
content is implemented in a way that it can be ignored by assistive
technology <http://www.w3.org/WAI/GL/WCAG20/#atdef> . 

 

[snip]