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

Re: Why are nested tables that bad

From: Phill Jenkins <pjenkins@us.ibm.com>
Date: Mon, 13 Jan 2003 16:26:44 -0600
To: "Jesper Tverskov" <jesper.tverskov@mail.tele.dk>
Cc: w3c-wai-ig@w3.org
Message-ID: <OFD3965DAB.70417EF3-ON86256CAD.007AE1A6@pok.ibm.com>


Jesper, I think you and the rest of us would be better served if you gave
the list a URI to the web site using the "seven tables on each web page".
Then the list can stop the speculation, guessing, and pontification and
give you a real lesson.

Regards,
Phill Jenkins
IBM Research Division - Accessibility Center
http://www.ibm.com/able




"Jesper Tverskov" <jesper.tverskov@mail.tele.dk>@w3.org on 01/13/2003
11:15:01 AM

Sent by:    w3c-wai-ig-request@w3.org


To:    <w3c-wai-ig@w3.org>
cc:
Subject:    Why are nested tables that bad




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 17:27:57 GMT

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