I'm still troubled by using tables to implement a song chart as the semantic meaning behind each row's position (eg. Row 2 is there cos it's ranked LOWER than row 1) is lost.
Not if one of your columns is specifically for the chart position. Then, on the first row the data will be 1, on the second 2, etc. Lists are all nice an well, but can be taken to the extreme sometimes (heck, sentences are ordered lists of individual words, etc etc). I stand by the statement that a single table, correctly marked up with adequate headers, is the most semantic way to mark this up.
Also, as for accessibility issues, would a blind man get tired of reading n-lines of Song Name: XXX, Singer: YYY etc? :)
Don't make assumptions about how a blind person would or wouldn't be reading it. Depending on the screenreader they use, and the specific verbosity settings, they can read the data, then only prompt the screenreader to inform them of the header if they need it.
Using a screenreader is an interactive process. Blind users don't simply get to a page and have it read out top to bottom. Particularly when working with data sets in tables, there are a great number of functions available to the user in order to efficiently navigate around.
And in any case, it's a silly question: that *is* the way tabular data has to be marked up accessibly. It's the software the visually impaired use that takes care of whether it's "tiring" or not.
If you're still unconvinced, though...here's a scenario where the tabularlist thing falls apart completely and becomes a pain for any non-sighted user: say you're in one of the rows, in the column with the artist name. Now, you want to go down the rows, but stay within this column (i.e. you're skimming the artist names, until you hit your favourite artist). If it's marked up as a single table, that's a piece of cake: screenreaders like JAWS offer simple ways to navigate up/down/left/right within a table. Simply jump down, and you're still in the artist column. Now, tabularlists? As it's only a one row table you're always in, the screenreader would announce "end of table" or similar; you then have to exit the table, go to the next list item, enter the table, navigate to the artist column (and remember, none of these columns have headers defined, so it's a case of counting or guessing)...etc
Now, *that* is tiring.
Tabularlists are a perversion, in the sense that they use markup structures in ways in which they were not meant to be used...and then use heavy styling to *visually* make them right. Sorry, but no, it's still rubbish...the usual "everything can be boiled down to a list" approach that seems to be "de rigeur"...
-- Patrick H. Lauke _____________________________________________________ re�dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com
****************************************************** The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
