W3C home > Mailing lists > Public > public-html@w3.org > May 2007

Re: <table summary> and <td headers> (was: Re: <font> (was Support Existing Content))

From: Charles McCathieNevile <chaals@opera.com>
Date: Wed, 02 May 2007 18:25:07 +0200
To: "public-html@w3.org" <public-html@w3.org>
Message-ID: <op.trpjv5ejwxe0ny@widsith.local>

On Wed, 02 May 2007 15:03:01 +0200, Anne van Kesteren <annevk@opera.com> wrote:

>
> On Wed, 02 May 2007 14:59:46 +0200, Ray Dickman <rdickman@ramius.net>
> wrote:
>>> Indeed. At least summary= is often abused by authors: "Table used for
>>> layout", "Grid of 3 by 2 cells", etc. Given how determining cell headers
>>> is defined I wonder about use cases for headers=.
>>
>> In the case of complex data tables (where there may be headings that span
>> multiple sub-headings for example), people can use the headers attribute
>> to link that data to a <th>'s id value.  Basically, in a table that isn't
>> simple enough to just use scope, associating data to headings using
>> headers and ids is very useful.
>
> I'm aware how headers= works. I don't think your use case is one where it
> is needed though. Could you give a concrete example (maybe even in code)?

If you are using a screen reader to explore a table, finding relevant headers via the headers attribute has been an important use case for some time (as in, years). Unfortunately the more powerful and less code-heavy approaches such as the use of scope and axis attributes have not had nearly the same level of implementation, so in practical terms this attribute is important to accesibility (as in "don't break the web").

cheers

Chaals

-- 
  Charles McCathieNevile, Opera Software: Standards Group
  hablo español  -  je parle français  -  jeg lærer norsk
chaals@opera.com  Catch up: Speed Dial  http://opera.com
Received on Wednesday, 2 May 2007 16:25:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:44 UTC