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

Discussion on image map item follows. Statement on waicard10 currently reads:

"Image maps. Use client-side MAP and text links for hotspots."

>> 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.
>>
>actually, it was pointed out on the GL list that depending on how people
>create client side image maps, there are two strategies they could use.
>One does not use "alt" and thus a more general statement should be made in
>regards to techniques.  We're proposing the following for the next version
>of the guidelines:
>For all image map links, provide text for each link (e.g., via the "alt"
>     attribute of HTML AREA elements or by using the MAP element with
>     anchors defined with the A element). 
>
>we're still working on the wording, but I hope the message is clear. 

Even if we know what we mean in real life, the challenge with the reference
card is to get this into an absolute minimum of words, as a conceptual
prompt, with the expectation that people will refer back to the guidelines
for additional information. 

We can't use a general statement as long as the one above. Do you have a
(short) proposal, or a reaction to Daniel's proposal? Here are Daniel's
comments from this morning:

>> ...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.
>
>with alt in bold or not ?
>putting it in bold clearly points at the attribute (used in AREA) and
>leave out both the inline alt text (that Len wanted to have expressed)
>and the new MAP content model with text in A (that wendy mentioned).
>
>I suggest we use this sentence with alt not in bold.

Replacement proposal is "Image maps. Use client-side MAP and alt text for
hotspots." Are we missing an obvious other approach? Is either version a
"show-stopper"? 

Judy
----------
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 Thursday, 11 February 1999 09:22:47 UTC