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

Re: WAI card

From: Alan Cantor <acantor@oise.utoronto.ca>
Date: Mon, 1 Feb 1999 13:37:53 -0500 (EST)
To: w3c-wai-eo@w3.org
Message-ID: <Pine.SOL.3.91.990201125518.26680B-100000@tortoise>
> > 
> > "Use the alt attribute to concisely describe visuals."
> The guidelines insists that what goes in the ALT is the function of
> the visual, not the description of the visual. So you don't find "this 
> is a line of yellow duck", you find "" for ALT in that case.

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. 

> > "MAP" and "link" must agree in number with Image Maps. Therefore:
> > 
> > "Use client-side MAPs and text links for hotspots."
> Actually, it's one MAP with multiple hotspots. Does that change ?

The word should agree with the title, which is "Image Maps." How about:

"Use client-side MAPS and text links for each hotspot."

> > "Use headings, lists, the lang attribute, and a consistent structure. Use
> >  CSS for layout." 
> > 
> > "Use headings, lists, the lang attribute, and a consistent structure. Use
> >  CSS to layout pages." 
> I think Style is CSS is not obvious to everybody and needs
> to be mentioned.

How about:

"Structure pages with headings, lists & CSS. Use the lang attribute.

> > > 6 Graphs & Charts  
> > 
> > "Summarize the data, or use the longdesc attribute."
> The only reason I shortened this one is to fit in 9 pt.

Here's a shortened version:

Summarize, or use the longdesc attribute.

> > > 7 Scripts, Applets, & Plug-ins  
> > 
> > > Provide alternative representations in case active content is inaccessible 
> > > or unsupported.  
> > 
> > "Provide alternative representations in case the active content is
> > unsupported." 
> > 
> > "Provide alternative representations in case the content is unsupported."
> "content unsupported" feels awkward.

How about 

"Provide alternative representations in case features are unsupported."

> > "Ensure that data makes sense when read cell by cell. Summarize. 
> >  Use CSS to format columns." 
> Issue with that is that CSS is not really supported everywhere for us
> to ask specifically to use it.

True, but CSS is mentioned elsewhere in the card. 

> > > 10 Check your work 

> > > Validate the HTML. Use evaluation tools and textual browser to verify 
> > > accessibility.  
> > 
> > Change "textual" to "text."
> Last version has text-only. Is that better ?

Yes, I agree. "Text-only" is more precise.

> I would really like people to give opinion on the font size choice.

Personally, I did not find the original card challenging to read. It is,
however, preferable to err on the side of bigness than smallness. 

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. 

Received on Monday, 1 February 1999 13:41:12 UTC

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