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

Re: Why are nested tables that bad

From: David Poehlman <poehlman1@comcast.net>
Date: Mon, 13 Jan 2003 12:39:08 -0500
To: Jesper Tverskov <jesper.tverskov@mail.tele.dk>, w3c-wai-ig@w3.org
Message-id: <003601c2bb2a$ad2fb280$6501a8c0@handsontech>

testing on lots of plat forms might reveal that they in fact are not handled
well.  Are you talking data or lay out?
sounds like data but in any case, there is lots of equipment when used in
conjunction such as older browsers and assistives that this may not do well
with.

----- Original Message -----
From: "Jesper Tverskov" <jesper.tverskov@mail.tele.dk>
To: <w3c-wai-ig@w3.org>
Sent: Monday, January 13, 2003 12:15 PM
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 12:41:27 GMT

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