- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 03 Jul 2008 16:54:20 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5822 --- Comment #12 from Gez Lemon <gez.lemon@gmail.com> 2008-07-03 16:54:19 --- (In reply to comment #11) > The header cells aren't associated with other header cells, sorry if that > wasn't clear in my earlier comments. I'm sorry, that's my fault - I misread what you said. > > It sounds to me like the actual data cell here is the top-left one. Maybe that > is the cell that should be included in every line. What would happen if a table > included multiple types of investments? > The problem is when a user is in a particular cell. For example, if a user is in the data cell containing the value 32,321.11, they should be able to query the cell to get the context for that cell. For example, it's the running cost (that's not a static value, so could change in similar tables) for the 19th December 2005 and is the actual value for Partner portal 2. If a user can't query these details, they have to query the whole row and the whole column, which is too cumbersome. As these tables are generated on the fly, it's simple to provide the headers attribute to ensure context is available. If hierarchical headers were allowed (which I misread in your previous reply), that would also allow the association to work, except current screen readers wouldn't work with that. I'm not so keen on hierarchical headers, as it doesn't make sense to mark data up as a header, but I could live with it. I would prefer that the headers attribute could also reference a td element, as that very neatly solves the problem, and also allows us to markup irregular tables. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 3 July 2008 16:54:55 UTC