W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > January to March 1999

last (fast) gasp for waicard10, closing Thursday a.m.

From: Judy Brewer <jbrewer@w3.org>
Date: Wed, 10 Feb 1999 22:40:50 -0500
Message-Id: <>
To: chisholm@trace.wisc.edu, po@trace.wisc.edu, w3c-wai-eo@w3.org, dd@w3.org
Wendy and Gregg were the only people who commented on waicard10.

The printers have to have it finalized by Thursday morning Feb 11. 

Here's where we are:

1) I've copied Wendy Chisholm's message below. Please look at Wendy's image
map comment. I think her comment has been accounted for in our discussions,
but if others agree it should be changed to read "Use client-side MAP and
alt text for hotspots," please let me know, & that's what we'll do.

2) Also please look at Wendy's image & animations comment. This gets back
to the awkwardness of "function," however I am not sure that her proposed
alternatives "replaces" or "provides" don't invite other kinds of
confusion. So, unless there is agreement from the list on either of these
alternatives, we will leave as is.

3) Page organization. I thought our last version had "where possible" after
"Use CSS for layout and style." I cannot find the reference on EOWG list
for dropping the "where possible" following CSS. While I do feel strongly
that we should mention CSS here, I also feel that the caution is necessary.
I will add "where possible" back in unless someone clarifies a resounding
reason to leave those two words out.

4) "For Complete..." Gregg Vanderheiden has expressed additional concern
about people thinking that the Quick Tips are the final say in Web
accessibility, based on his observations of how people respond to the pilot
version when visitors come in to Trace. He requested that we move the URL
back to the bottom of the back and label it "For the rest of the guidelines
and checkpoints..." However given our discussions about people never
noticing the URL at the bottom of the back, and based on space constraints,
I have recommended the following, which the designer has been able to fit
in caps, set in an inverted band below the title & logos. Looks good;
stands out well; should entice people with the thought of a handy checklist.

5) Gregg also raised a concern that the second phrase of "multimedia"
doesn't make any sense ("provide... accessible versions in case
inaccessible formats are used). I am not sure what we can do to clarify
this, nor what we lose if we take this out, since this does not clearly
enough address the pdf-type file format issue which has come up repeatedly
& was sometimes mentioned in conjunction with this. If there are no
additional comments, I will leave as is. If someone can propose a simple &
non-controversial clarification without adding more than three additonal
words, kindly do so.

5) Making sure people turn the card over: We're adding an arrow in lower
right of front side, and printing the conference literature stuffer with
one tear-off card facing front & one facing back.

Comments welcome to w3c-wai-eo@w3.org by Thursday 11:00 a.m. US EST.



Message-Id: <199902081516.JAA07602@trace.wisc.edu>
Date: Mon, 08 Feb 1999 14:13:25 -0600
To: w3c-wai-quicktips@w3.org
From: Wendy A Chisholm <chisholm@trace.wisc.edu>
Subject: feedback

I think the all of the P1 items as well as "major" P2 items are covered.
good to see.


1.  "Image maps. Use client-side MAP and text links for hotspots."
is it saying that *both* client-side image maps with alternative text for
each link as well as text links for each hotspot need to be provided on a
page?  If so, I think this has been misinterpretted and that it ought to be
recommending that client-side image maps ought to be used and to include
alt text for each hotspot in the image map.  Text links in addition to
well-designed client side imaps, is good, but not a highest priority
strategy to highlight.

2.  "Images & animations. Use the alt attribute to describe the function of
all visuals."
rather than "describing the function" I think that it "replaces" or
"provides" the function of the visual.  by saying "description" you may
have people providing too much detail. Also, we really  need to emphasize
the separation of function from presentation.

otherwise, looks great!  it's good to see that the whole doc can be boiled
down to these 10 points!

wendy chisholm
human factors engineer
trace research and development center
university of wisconsin - madison, USA
Judy Brewer    jbrewer@w3.org    +1.617.258.9741    http://www.w3.org/WAI
Director, Web Accessibility Initiative (WAI) International Program Office
World Wide Web Consortium (W3C)
MIT/LCS Room NE43-355, 545 Technology Square, Cambridge, MA,  02139,  USA
Received on Wednesday, 10 February 1999 22:43:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:29:27 UTC