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

Re: WAI card

From: Charles McCathieNevile <charles@w3.org>
Date: Mon, 1 Feb 1999 08:34:49 -0500 (EST)
To: dd@w3.org
cc: w3c-wai-eo@w3.org
Message-ID: <Pine.LNX.4.04.9902010830180.26535-100000@tux.w3.org>
On Mon, 1 Feb 1999, Daniel Dardailler wrote:

  
  Title: 
  
            Quick HTML tips for Accessible Web Site
  
    I really think it has to 9 point, so we definitively need
    to drop the rationales (see above) 
    It could also be what Charles has used:
  
             Quick HTML tips to make your site accessible
  
    but I prefer to mention "Web Site" than "to make".

CMN::

Quick tips to make Websites accessible

DD::  
  
  Pointer:
  
       See http://www.w3.org/WAI for the complete Guidelines & Techniques
  
    is way too long for 9 point, I have shorten it to:
  
       Complete Guidelines at www.w3.org/WAI
  
    and William to:
  
       Guidelines & Techniques: http://www.w3.org/WAI
  
    I think http:// can safely be dropped.
    I prefer to mention "Complete" than "Techniques", but not strongly.
CMN:: I'm with Daniel on this one  
  
DD::  
  
  4 Page Organization
     rationales need to go.
  
     Charles proposes:
  
      Use headings, lists, lang attribute, for structure. Use CSS for
      layout and style. Be consistent
  
     which is a close fit at 9 point, and I have
  
      Use headings, lists, lang attribute and consistent structure. Use
      CSS for layout and style.  
  
     which is a little shorter and is I think better because it's not
     bound to "just" heading, list and lang *for* structure, but open with an
     "*and* consistent structure" which can include fieldset, quote, etc.

CMN::
how about

Use headings, lists, lang, etc. for structure. Use CSS for layout. Be
consistent.
  
DD::
  Now on the verso side: as I said, we can keep it with rationales at 8
  point, but I have made an attempt to shorten for 9 point as well,
  while using some of William and Len's comments.
  
  
  5 Hypertext Links Use  link text that makes sense 
    when read out of context. 
    -- becomes
  5 Links  Use meaningfull link text. No "Click Here".
    -- also fit:
           Use text that makes sense read out of context.
CMN:: I prefer the original or the second option
  
DD::
  
  9 Tables  Avoid using tables to format columns or 
    navigation bars. Make cell by cell reading of tabular
    data sensible. 
    -- becomes
  9 Tables Have data make sense when read cell by cell.  
    Provide a Summary.Avoid using tables for columns.
CMN::
I would still like to push for 'row by row' or 'line by line'

DD::  
  10 Check your work  Validate the HTML & CSS of your site. 
     Test with images, sound, and animation off. Use evaluation 
     tools to verify accessibility. 
    -- becomes
  10 Check your work Validate the HTML. Use evaluation
     tools and textual browser to verify accessibility.  
   
  
  HTML visible at /WAI/EO/waicard6.htm (with pointer to gif file of
  preprint, which I also added to waicard5 for comparison)
  
Received on Monday, 1 February 1999 08:34:52 UTC

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