- From: Leonard R. Kasday <kasday@acm.org>
- Date: Fri, 09 Feb 2001 10:10:54 -0500
- To: "Fitzgerald, Jimmie" <Jimmie.Fitzgerald@jbosc.ksc.nasa.gov>, w3c-wai-ig@w3.org
Hi Jimmie, I'm glad those example were useful for you. I don't understand though why they make you think that you shouldn't use nested tables. Also, I hope people don't think I was saying to avoid tables altogether... just that you need to be aware of reading order when you use them. At least, that's what you need to get to double A compliance. To reach triple A compliance, you need to either avoid layout tables altogether, or have a linearized alternative, e.g. on a separate page, per Guideline 10.3. The URL is http://www.w3.org/TR/WCAG10/#gl-interim-accessibility Len At 08:44 AM 2/9/01 -0500, Fitzgerald, Jimmie wrote: >Hello all. Follow the link below for some good examples of how a screen >reader (like JAWS) deals with tables and forms. I will be using this data >to illustrate issues related to using tables for formatting a page. It >should be particularly useful when showing our team why we should not do a >bunch of nested tables. Enjoy > >http://astro.temple.edu/~kasday/wai/backwards.html > > >Jim Fitzgerald -- Leonard R. Kasday, Ph.D. Institute on Disabilities/UAP and Dept. of Electrical Engineering at Temple University (215) 204-2247 (voice) (800) 750-7428 (TTY) http://astro.temple.edu/~kasday mailto:kasday@acm.org Chair, W3C Web Accessibility Initiative Evaluation and Repair Tools Group http://www.w3.org/WAI/ER/IG/ The WAVE web page accessibility evaluation assistant: http://www.temple.edu/inst_disabilities/piat/wave/
Received on Friday, 9 February 2001 10:13:17 UTC