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 11:25:03 -0500 (EST)
To: w3c-wai-eo@w3.org
Message-ID: <Pine.SOL.3.91.990201101133.15753B-100000@tortoise>
Fantastic work summarizing the discussion, Daniel.

>           Quick HTML tips for Accessible Web Site
> 
>           Quick HTML tips to make your site accessible

Why Quick? The word "Tips" -- not to mention the size of the card! --
signal its intent. I think it's good to say HTML. I never liked the
rationale in the title; it was a grammatical quagmire: .... including
people with disabilities, handheld devices... etc. It read as though
handheld devices need quick tips! 

"HTML tips to ensure your Web site is accessible (to everyone or everybody
or to all)" 

or 

"HTML tips to make your Web site accessible (to everyone or everybody or
to all)" 

>      Complete Guidelines at www.w3.org/WAI
> 
>      Guidelines & Techniques: http://www.w3.org/WAI

Every sentence needs a verb. Don't omit articles when they fit.

"See the complete guidelines at www.w3.org/WAI"
"See the guidelines and techniques: www.w3.org/WAI"

I prefer the first.

> 1 Images & Animations 
> 
>    Use the alt attribute to describe the function of all visuals. 

Some visuals create functionality. Other visuals are purely aesthetic,
which may or may not be functional. 

Is it desirable that web-authors describe ALL visuals? "This is an
aquamarine, 4-point line section-separator with ice cream and a cherry on
top?" What do the guidelines say about this? Anyway, I propose:

"Use the alt attribute to concisely describe visuals."

> 2 Image Maps 
>  
>    Use client-side MAP and text link for hotspots.

"MAP" and "link" must agree in number with Image Maps. Therefore:

"Use client-side MAPs and text links for hotspots."

> 3 Multimedia 
> 
>    Provide captioning and transcripts of audio, and descriptions of video. 

Should it be captioning AND or captioning OR? 

"Provide captioning or transcripts of audio, and descriptions of video."

> 4 Page Organization
> 
>     Use headings, lists, lang attribute, for structure. Use CSS for
>     layout and style. Be consistent
> 
>     Use headings, lists, lang attribute and consistent structure. Use
>     CSS for layout and style.  

I find the second example clearer. I would add "a" and "the" 
where needed to improve readibility. "Style" may be too techie; is
"look-and-feel" better? Or just drop style -- CSS says it.

"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." 

> 5 Hypertext Links 
> 
> Use link text that makes sense when read out of context. 

> Use meaningfull link text. No "Click Here".

> Use text that makes sense read out of context.

"Use link text that makes sense when read out of context."

or revisit the first draft:

"Ensure that each link makes sense when read alone."

> 6 Graphs & Charts  
> 
> Provide summary or use longdesc attribute. 
> Use summary or longdesc attribute.

"Summarize the data, or use the longdesc attribute."

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

Remove the comma after Applets, add "the" after "in case." I think we can
drop "inaccessible." If scripts and applets were well-supported, they
would be accessible. Can we leave out "active?"

"Provide alternative representations in case the active content is
unsupported." 

"Provide alternative representations in case the content is unsupported." 

> 8 Frames 
> 
> Label each frame with title or name attribute to allow access
to individual pages. 
> Label each frame with title or name attribute.

Add "the" if it will fit:

"Label each frame with the title or name attribute."

> 9 Tables 
> 
> Avoid using tables to format columns or navigation bars. Make
> cell by cell reading of tabular data sensible. 

> Have data make sense when read cell by cell. Provide a Summary. Avoid
> using tables for columns. 

"Ensure that data makes sense when read cell by cell. Summarize. 
 Use CSS to format columns." 

> 10 Check your work 
> 
> Validate the HTML & CSS of your site. Test with images, sound, and 
> animation off. Use evaluation tools to verify accessibility. 

> Validate the HTML. Use evaluation tools and textual browser to verify 
> accessibility.  

Change "textual" to "text."

"Validate the HTML. Use evaluation tools and a text browser to verify
accessibility."

Alan
Received on Monday, 1 February 1999 11:26:55 UTC

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