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

Re: WAI card

From: Daniel Dardailler <danield@w3.org>
Date: Tue, 02 Feb 1999 11:47:56 +0100
Message-Id: <199902021047.LAA28473@www47.inria.fr>
To: Alan Cantor <acantor@oise.utoronto.ca>
cc: w3c-wai-eo@w3.org

> Although our efforts is constrained by the guidelines, must be genuflect
> before the guidelines when something is unclear? What are its authors
> trying to say here? I will re-read this section of the guidelines and see.
> "Function" of a visual means little to me. 

example: a magnifying glass: function is "search", a colorful logo,
function is "home page", little worker digging the ground: function is
"under construction", etc.
> "Use client-side MAPS and text links for each hotspot."

I don't see why we need to use plural here, it just makes it longer.
(MAPS is not a valid element name anyway)

Taking into account Len's comment, which I might have read the wrong
way since I removed "alternate" based on his input, I suggest:

  Use client-side MAP and alt text for hotspot.

> How about:
> "Structure pages with headings, lists & CSS. Use the lang attribute.

You don't really structure with CSS, you style. That's why it's a
separate sentence. lang is now gone.
> Summarize, or use the longdesc attribute.

I like this one better that what we have now.

We don't have "," anywhere in the card, so I'm not sure it's needed.
I've added "the" and it sort of fits, but as you say, the final
designer will make the cut if needed.

> Provide alternative representations in case features are

Hum, features doesn't quite convey the active nature of script, applet 
and pluging. A feature is really anything.

> True, but CSS is mentioned elsewhere in the card. 

CSS is operational for regular styling, but not really to replace
column layout.
> I don't think we should get too caught up with the issue of font size. 
> That's the job of the graphic designer. Graphic designers know how to play
> with typefaces, leading, kerning, scaling, etc. to make things fit. We
> should not compromise transparency of meaning for the sake of a handful of
> words. Our primary job is to distill the guidelines into a clear and
> succinct form. 

My reading of your comment is that we can err on the side of the "too
big" and trust the graphic designer to shrink it to fit, without
removing any word.
Received on Tuesday, 2 February 1999 05:48:09 UTC

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