From: Jeremy McAnally Date: 2008-02-11T08:51:20+09:00 Subject: Re: Introducing Waves - Web App Framework From a designer's perspective, tables are not accessible since they don't retain the semantic structure of the document. I don't really know a whole lot about accessibility and what have you, but I would imagine that a screen reader treats tabular structured markup differently than layout structured markup (and would, presumably, treat a page laid out with tables incorrectly). --Jeremy On Feb 10, 2008 6:33 PM, Marc Heiler wrote: > > Tables are more brittle and make the code itself harder to read. > > This is incorrect if anyone asks me. > I am generating tables programmatically from ruby, and on the layout > question, it is simply a lot easier to have a table arranged nicely with > columns rather than messing with multiple divs. You can use CSS in both > cases anyway. > > The "harder to read" argument is really a no argument as far as I see > it, and I will even go as far as to suggest to compare a specific table > with 8 rows and 18 columns with the equivalent div solution. > I would be curious to see the solution so I can compare but until I have > seen it I will claim, based on my own experience, that the table > solution is the better one. > -- > Posted via http://www.ruby-forum.com/. > > -- http://www.jeremymcanally.com/ My books: Ruby in Practice http://www.manning.com/mcanally/ My free Ruby e-book http://www.humblelittlerubybook.com/ My blogs: http://www.mrneighborly.com/ http://www.rubyinpractice.com/