W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 1998

RE: The problem with tables

From: david adam edelstein <davadam@well.com>
Date: Mon, 27 Jul 1998 07:28:21 -0700
To: "'WAI'" <w3c-wai-ig@w3.org>
Message-ID: <000101bdb96a$d04cadc0$a341fdd0@daveedhome>
> -----Original Message-----
> From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org]On
> Behalf Of Jon Gunderson
> Sent: Monday, July 27, 1998 6:35 AM
> Thank you for your comments.  I agree that tables were not orginally
> intended for page layout, but they have been coopted for that
> purpose.   I
> don't think WAI should encourage the use of tables for
> layout, but I think
> WAI should ignore the current practice in the use of tables
> for layout in
> the development of guidelines.

I tend to agree with this view.

To me, the use of tables for layout is not going to go away in HTML;
therefore, a more profitable direction would be to fix the relatively few
number of screen readers, rather than the nigh-unto-infinite number of web

Thanks to Charles McCathieNevile for the excellent example of the problem
with how screen readers deal with HTML content.  Why (he asked, getting
ready to duck) are screen readers so stupid?  A table of contents in a
left-most table cell is tagged as an identifiable HTML block.  Why haven't
any of the screen readers been written to deal with HTML blocks, instead of
just reading across and down?


david adam edelstein

"Most real growth involves an element of pain, certainly of confusion.
If you're comfortable with what you're doing, you've been there before."
--Jerry Uelsmann
Received on Monday, 27 July 1998 10:26:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:01 UTC