- From: Judy Brewer <jbrewer@w3.org>
- Date: Thu, 15 Jul 1999 11:11:16 -0400
- To: w3c-wai-eo@w3.org
- Cc: Michael_Muller@lotus.com
WAI EOWG: Forwarding some Quick Tips comments. - Judy At 03:07 PM 7/14/99 -0400, Michael_Muller@lotus.com wrote: > >Hi Judy, > >Thanks for the chance to comment. I've added three suggestions to the >original text that you sent us (I had other comments, but you've >anticipated them in your plans for changes). My suggestions are indicated >below on lines that begin with "<comment #>" and end with "</comment #>" >(where "#" is the number of the comment). > >Best wishes, >--michael >----- >Michael Muller >Lotus Research >Lotus Development Corporation >55 Cambridge Parkway >Cambridge MA 02142 USA >+1-617-693-4235 (voice) +1-617-693-1407 (fax) >mullerm@acm.org or michael_muller@lotus.com > >Judy Brewer <jbrewer@w3.org>@w3.org on 07/09/99 10:57:29 AM > >Sent by: w3c-wai-gl-request@w3.org > > >To: w3c-wai-eo@w3.org, w3c-wai-gl@w3.org >cc: (bcc: Michael Muller/CAM/Lotus) > >Subject: Questions on Quick Tips revisions > >[Excerpt with comments:] > >- Images & animations. Use the alt attribute to describe the function of >all visuals. ><comment 1> Perhaps replace "the function" with "both content and function" ></comment 1> >- Image maps. Use client-side MAP and text for hotspots. >- Multimedia. Provide captioning and transcripts of audio, descriptions of >video, and accessible versions in case inaccessible formats are used. >- Hypertext links. Use text that makes sense when read out of context. For >instance, do not use "click here." >- Page organization. Use headings, lists, and consistent structure. Use CSS >for layout and style where possible. >- Graphs & charts. Summarize or use the longdesc attribute. >- Scripts, applets, & plug-ins. Provide alternative content in case active >features are inaccessible or unsupported. >- Frames. Label with the title or name attribute. >- Tables. Make line by line reading sensible. Summarize. Avoid using tables >for column layout. >- Check your work. Validate the HTML. Use evaluation tools and text-only >browsers to verify accessibility. ><comment 2> Perhaps append (at the end of "Check your work") "Navigate >using mouse only." </comment 2> ><comment 3> Perhaps further append "If you can't validate with a screen >reader, ask your colleague to play the role of screen reader software and >operate with your eyes closed." (I realize that this is probably too long.) ></comment 3> > > > > > ---------- 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, 15 July 1999 11:12:09 UTC