W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2001

RE: Comments on SUFFICIENCY for tomorrows COnf Call

From: Anne Pemberton <apembert@erols.com>
Date: Thu, 12 Jul 2001 09:51:01 -0400
Message-Id: <3.0.5.32.20010712095101.007e3b30@pop.erols.com>
To: <gv@trace.wisc.edu>, <jasonw@ariel.ucs.unimelb.edu.au>
Cc: "'GL - WAI Guidelines WG \(GL - WAI Guidelines WG\)'" <w3c-wai-gl@w3.org>
Greg, the earlier files you sent were in *.DAT format, and nothing I have
would let me see in them, except notepad, which was unusable. The last file
arrived as *.txt and was usable in Word. 

Looks like you did a lot of work. 

A few comments: First of all 1.1 is not sufficient because there is not
equivalent required for text content. For people who use text best, you
have covered all the bases here, but for people who use text inefficiently,
there is no requirement that text have an equivalent. 

On one of the tough ones: Gregg summarized:

>Checkpoint 3.4: 
>1. Illustrations must be designed to portray important concepts or
relationships employed in the content.   [SOUNDS LIKE ADVICE OR RULE RATHER
THAN SUFFICIENCY.] 
>2. Where appropriate, illustrations should be referred to in the text
(e.g., in a caption or as part of the textual exposition), to provide the
reader with an appropriate context in which to interpret the illustration. 
>[  I HAVE TROUBLE USING 'MUST' TERMINOLOGY FOR A PRIORITY 2 OR PRIORITY 3
LEVEL ITEM….
>[ AGAIN - IS THIS ALL I EVER NEED TO DO?]
>

Gregg, I have problems with the whole thing and would suggest it be totally
redone, starting with the purpose of the guideline, which is to
encourage/require that content include illustrations. Not all illustrations
must address only the important concepts and relationships, they can also
illustrate minor points and still aide in comprehension of the content. And
it really isn't necessary to mention the illustration in the text. Nice to
do, but certainly not anything close to a should or a must. 

What is a must, is that text have a non-text equivalent. It it is not
clearly stated in Guideline 1, as it should, then if it must be buried in a
substep of Guideline 3, then 3.4 should be unequivocal about what is
important. Dabbling in design of illustration and captioning isn't making a
web page more accessible to a  "skip the text" user. 

					Anne

At 12:41 AM 7/12/01 -0500, Gregg Vanderheiden wrote:
>I sent it in DOC , HTML and RTF.   
>
>It should not be in proprietary format.  
>
>Here it is in text.
>
>
>
>
>-- ------------------------------ 
>Gregg C Vanderheiden Ph.D. 
>Professor - Human Factors 
>Dept of Ind. Engr. - U of Wis. 
>Director - Trace R & D Center 
>Gv@trace.wisc.edu <mailto:Gv@trace.wisc.edu>, <http://trace.wisc.edu/> 
>FAX 608/262-8848  
>For a list of our listserves send “lists” to listproc@trace.wisc.edu
><mailto:listproc@trace.wisc.edu> 
>
>
>-----Original Message-----
>From: Jason White [mailto:jasonw@ariel.ucs.unimelb.edu.au] 
>Sent: Thursday, July 12, 2001 12:02 AM
>To: gv@trace.wisc.edu
>Cc: GL - WAI Guidelines WG (GL - WAI Guidelines WG)
>Subject: Re: Comments on SUFFICIENCY for tomorrows COnf Call
>
>I still can't read the document attached to Gregg's message. It is in
>some kind of proprietary format.
>
>Please, always send documents as plain text or in HTML.
>
>Attachment Converted: "c:\eud-anne\attach\WCAG 2 Sufficiency11.txt"
>
Anne Pemberton
apembert@erols.com

http://www.erols.com/stevepem
http://www.geocities.com/apembert45
Received on Thursday, 12 July 2001 09:43:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:11 GMT