I’m pretty much a standards advocate, but I suggest using tables for
that make sense for tables.
Tables shouldn’t be used to lay things out. You want to be able to
your design from your presentation.
That said, “tablular data” could be expanded to mean anything that is
two-dimentional. This can include name/value pairs, so it might be
appropriate to use a table to display the show page if you really are
to represent it in a tabular manner.
The same goes for forms, as you have names and values there too.
Standards advocates tend to hate tables for two reasons:
Excessive markup. A lot of times you have way more markup than is
necessary. Standards-based design is all about semantic markup - using
for their intended purpose. However, if you end up using a ton of divs
spans and css to get it to look right, do you still, in the end, have
Accessibility concerns, especially for screen readers. You have to
through a lot of hoops to get a screen reader to read the tables in the
order you think they should be read. When sites use tables completely
the layout, it’s a terrible mess.
My opinion on this boils down to this:
You have requirements. It has to look this way and it has to be done by
time. The only people who are going to pick on you for using a table for
layout are standards advocates and other web developers. How much do
opinions matter to you, and how much time / money do you have to burn to
it the “right” way in their eyes? I break the “rules” from time to time
because I have to GET STUFF DONE.
Just throwin’ my .02 around.
On Fri, Jul 11, 2008 at 3:48 PM, Phillip K. <