W3C home > Mailing lists > Public > wai-xtech@w3.org > August 2008

Re: table headers - clear description of problem

From: Gez Lemon <gez.lemon@gmail.com>
Date: Fri, 29 Aug 2008 12:40:06 +0100
Message-ID: <e2a28a920808290440w265292ceidb6cc30ba201a674@mail.gmail.com>
To: "Henri Sivonen" <hsivonen@iki.fi>
Cc: "HTML WG" <public-html@w3.org>, "W3C WAI-XTECH" <wai-xtech@w3.org>

2008/8/29 Henri Sivonen <hsivonen@iki.fi>:
> On Aug 26, 2008, at 18:53, Gez Lemon wrote:
>> This can sometimes be overcome (if there are no totals or
>> other aggregate data that usually go in the last columns) by
>> reordering the columns, but using conceptual headers marked up as tds
>> with headers/id to create the association allows analysts to order the
>> columns how they want.
> Isn't the markup abusing the semantics of HTML if cells that are
> conceptually header cells aren't marked up as <th>?

The cells contain data, so should be marked up with <td>.

> Why not mark all the header cells as <th> and enable hierarchical headers by
> allowing a <th> cell to point to another <th> using the headers attribute?

At the moment, nested headers aren't allowed. If the spec is changed
so that they are allowed, I wouldn't want header elements in the
middle of a data table, as the header wouldn't apply to the row or
column it's in, but a conceptual header for the cells that reference
it. Allowing the headers attribute to reference a td is logical,
simple, and it works in current implementations.


Supplement your vitamins
Received on Friday, 29 August 2008 11:40:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:25:22 UTC