W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2000

RE: Linearizing Tables

From: Bruce Bailey <bbailey@clark.net>
Date: Tue, 11 Apr 2000 09:18:34 -0400
To: <w3c-wai-ig@w3.org>
Cc: <kford@teleport.com>, "Steven McCaffrey" <smccaffr@MAIL.NYSED.GOV>
Message-ID: <000801bfa3b8$704f0500$53fe330a@msde>
Dear Steve,

> Bruce:
> with your code:
> I heard, with JFW 3.2 and IE 4.01:
> Chino: Plain front, Pleated, Drawstring, Cargo.
> Poplin: Plain front, Pleated, Drawstring.
> Active: Ripstop Hikers, Cargo Water, Tactel Adventure, Knit Sport, Knit
> I still can't completely make sense of this, but it is a little better.
> -Steve

Right, but I should think it would be MUCH better than hearing:
Chino: Poplin: Active:
Plain front, Plain front, Ripstop Hikers.
Pleated, Pleated, Cargo Water.
Drawstring, Drawstring, Tactel Adventure.
Cargo, , Knit Sport.
, , Knit Cargo.
Which is how my first example would be read.  (For the sake of space
considerations, I've converted cells to commas, row endings to periods, and
indicated header cells with a colon.)

Please note that my code fragments (from my previous post) would have the
same visual orientation: six rows, three columns, with the items organized
(grouped) by column.

I am just trying to highlight the importance of Checkpoint 5.3, tables
should linearize.

Ideally, screen readers would do something with TH versus TD.  Shan Sasser's
post that you reference (regarding the example in the techniques document)
is basically of an intelligent (but wholly theoretical) transformation (via
screen reader) that uses proper markup to convert tables of the one type to
the other.
Received on Tuesday, 11 April 2000 09:21:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:35:55 UTC