Re: Checkpoint 3.3

I think the word "preserve" seems to indicate the original intent is that
somebody has done something somewhere else to add accessibility information
to the object and this checkpoint seems to be saying make sure you keep it
around for use in this authoring tool.  

In the excel case I stated nobody really did anything special for
accessibility, but there is information available that can be used to
generate accessible markup.  I think a term like "generate" accessible
markup is a different concept than the current word "preserve".

You may want to describe more the difference between "human authored" and
"automatically generated" accessibility information.  I would suggest this
be done through checkpoints, since it seems like two fundamentally
different concepts to me.

I think the use of multi-media in 3.3 is limiting.  Why not "pre-written"
accessibility information for any object be used as the default?  Is there
something special about mult-media?

Jon


At 12:48 PM 9/21/99 -0400, Charles McCathieNevile wrote:
>The intent of this technique is to require information that the authoring
>tool can understand, and that has been hhuman authored, specifically in the
>context of mulitmedia objects although there may be other applicable
>situations.
>
>In the case where information can be automatically generated (ie it is
>included in the native format which is imported or converted) it should be
>covered by checkpoint 1.4, as you suggested in your previous email. Do you
>have a suggestion about  how we could clarify this? (Beyond including your
>example in the techniques, which I suggest we do - thank you.)
>
>regards
>
>Charles McCN
>
>On Tue, 21 Sep 1999, Jon Gunderson wrote:
>
>  Checkpoint 3.3 Provide pre-written alternative information for all
>  multimedia files packaged with the authoring tool. 
>  
>  This checkpoint doesn't seem to make sense to me.  To me it sounds like you
>  are trying to say that if an object being inserted already has
>  accessibility information associated with it, use that information as the
>  default accessibility information.  The words "Provide pre-written" sound
>  like the authoring tool should have some special knowledge of the object
>  being inserted.
>  
>  Maybe reqording the checkpoint to read:
>  
>  "Use imported information to automatically generate accessible markup"
>  
>  This would also incompass more than just mult-media objects.  Any object
>  that has information that could be used to generate accessibility markup
>  could be used.  In a previous e-mail I discussed a excel chart as an
example.
>  
>  
>  
>  
>  Jon Gunderson, Ph.D., ATP
>  Coordinator of Assistive Communication and Information Technology
>  Chair, W3C WAI User Agent Working Group
>  Division of Rehabilitation - Education Services
>  University of Illinois at Urbana/Champaign
>  1207 S. Oak Street
>  Champaign, IL 61820
>  
>  Voice: 217-244-5870
>  Fax: 217-333-0248
>  E-mail: jongund@uiuc.edu
>  WWW:	http://www.staff.uiuc.edu/~jongund
>  		http://www.w3.org/wai/ua
>  		http://www.als.uiuc.edu/InfoTechAccess
>  
>
>--Charles McCathieNevile            mailto:charles@w3.org
>phone: +1 617 258 0992   http://www.w3.org/People/Charles
>W3C Web Accessibility Initiative    http://www.w3.org/WAI
>MIT/LCS  -  545 Technology sq., Cambridge MA, 02139,  USA

Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Chair, W3C WAI User Agent Working Group
Division of Rehabilitation - Education Services
University of Illinois at Urbana/Champaign
1207 S. Oak Street
Champaign, IL 61820

Voice: 217-244-5870
Fax: 217-333-0248
E-mail: jongund@uiuc.edu
WWW:	http://www.staff.uiuc.edu/~jongund
		http://www.w3.org/wai/ua
		http://www.als.uiuc.edu/InfoTechAccess

Received on Tuesday, 21 September 1999 13:51:31 UTC