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

Re: Why are nested tables that bad

From: philip steven lanier <planier@u.washington.edu>
Date: Mon, 13 Jan 2003 10:36:44 -0800 (PST)
To: Jesper Tverskov <jesper.tverskov@mail.tele.dk>
cc: w3c-wai-ig@w3.org
Message-ID: <Pine.A41.4.44.0301131029350.94068-100000@dante10.u.washington.edu>

The W3C guidelines have nothing to say about nested tables.  I think that
you would find that the majority of sites that use tables for layout have
nested tables.  If you are using the tables strictly for layout, the most
important thing is that they linearize correctly.  The only potential
problem that I can see would be nested data tables, as some screen readers
or other software may have trouble navigating between different levels of
tables in a table reading mode.  This is untested, pure speculation,
however.

-Phil Lanier


On Mon, 13 Jan 2003, Jesper Tverskov wrote:

>
> I am reviewing a web site using seven tables on each web page, one table having four nested tables, and two of these a nested table each.
>
> I would like to give this web site very bad marks, but the problem is that the the tables linearizes well, the web pages sounds right in a screen reader like JAWS, and all the web pages look nice in more than 99% of the browsers in use today.
>
> So what is the problem?
>
> The truth could be, that just one misspelled word on the front page is a greater offence or what? Please give me the facts about nested tables. Why are nested tables bad in the real world of accessibility? Teach me a lesson!
>
> Best regards,
> Jesper
>
>
Received on Monday, 13 January 2003 13:36:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:08 GMT