Again, completely agree, Gary. There is another reason why tabular data is more beneficial if marked up using tables - accessibility!
When a blind user comes to a table, they cannot *see* it as one unit, so they need ways of tying columns and rows together. You can do this with tables, you cannot with lists. Admittedly, we have been talking about two columns, so there is not a great deal of need, but worth keeping in mind when pushing envelopes :) When you use a table correctly (not for page layouts but for true tabular data) you should also use most/all the accessibility features that go with it including: - summary - caption - thead and tbody - th - id - headers You can even use the more obscure ones like: - scope="col" - scope="row" Russ > > And why not a table of events ? (as in this instance) > > First column is "event date", second column is "event title". The rows > are the events. > > It if looks like a table and smells like a table...... > > I have seen a lot of wonderful stuff in the last 6 months done with HTML > and CSS. > > I have also seen a lot of horrid efforts to change things into things that > they dont need to be. > > [No offence Peter] But I just cannot see myself marking up that event data > in anything but a table - unless I wanted to display it in some other way > (that would be a different story all together - but my first instinct > would be to call that data tabular unless there were some requirement that > indicated it wasn't). > ***************************************************** The discussion list for http://webstandardsgroup.org/ *****************************************************
