W3C home > Mailing lists > Public > w3c-wai-er-ig@w3.org > January 2000

Re: Updated ERT

From: Leonard R. Kasday <kasday@acm.org>
Date: Mon, 03 Jan 2000 09:01:22 -0500
Message-Id: <4.2.2.20000103085345.00cca830@pop3.concentric.net>
To: "Chris Ridpath" <chris.ridpath@utoronto.ca>, "WAI ER IG List" <w3c-wai-er-ig@w3.org>
The description of "linearization" now reads

When a table is 'linearized' the cells are usually read a row at a time, 
starting at the left and             moving to the right.

That's true, but I'd suggest adding something like:

'More specifically, "linearized" means reading the cells in the order in 
which they appear in the HTML source of the table'.

This is equivalent to the Web Contents Accessibility Guidelines which 
defines a linearized table as

"A table rendering process where the contents of the cells become a series 
of paragraphs (e.g., down the page) one after another. The paragraphs will 
occur in the same order as the cells are defined in the document source.

(see
http://www.w3.org/TR/1999/WAI-WEBCONTENT-19990505/wai-pageauth.html#lineariz 
ed-table
)

(I changed it to fit in with your wording in terms of cells, which I like).

Len


At 11:55 AM 12/21/99 -0500, Chris Ridpath wrote:
>I performed a couple of tests with Lynx and it seems to read tables a row at
>a time. If cells are merged, it still tries to do this. For example, if a
>table is organized like a telephone keypad:
>1,2,3
>4,5,6
>7,8,9
>
>It will read 1,2,3,4,5,6,7,8,9
>
>If the cells 1 and 4 are merged such as:
>
>m,2,3
>m,5,6
>7,8,9
>It will read m,2,3,5,6,7,8,9

-------
Leonard R. Kasday, Ph.D.
Institute on Disabilities/UAP, and
Department of Electrical Engineering
Temple University
423 Ritter Annex, Philadelphia, PA 19122

kasday@acm.org
http://astro.temple.edu/~kasday

(215) 204-2247 (voice)
(800) 750-7428 (TTY)
Received on Monday, 3 January 2000 08:59:32 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 9 June 2005 12:10:34 GMT