Re: WCAG Checkpoint 5.3

I can understand the example in data tables, but
Checkpoint 5.3 seems to deal only about tables for
layout. I think often layout table cells are very
context independent and can be understood anyway you
should linearize.

For example, a typical 4-row 2-columns web page layout
table could contain another nested tables like that:

           header-table (colspan=2)

      topnavigationbar-table (colspan=2)

leftnavigationbar-table    contents-table

          feet-table (colspan=2)

When linearized this should be perfectly understable: 

header-table topnavigationbar-table
leftnavigationbar-table contents-table feet-table.
All the contents of these nested tables should be read
before starting to read another table. So anyone who
should read 5.3 could think he can use this kind of
layout for priority 2, when in other checkpoints (3.1
and 3.3) its said he can't. This way it seems a
contradiction for me.

Pablo Enríquez.

 --- Isofarro <>
escribió: > 
> From: "Pablo Enríquez" <>
> Subject: Re: WCAG Checkpoint 5.3
> > Those say that you must use StyleSheet to control
> the
> > layout, this says you can use tables which make
> sense
> > linearized. something sounds wrong.
> Why? Tables are for the structure of tabular data
> (like a league table) -
> not just for layout.
> Nested tables are a good way of messing with the
> linearisation of tables.
> Take for example a two column table:
> row1col1    row1col2
> row2col1    row2col2
> row3col1    row3col2
> row4col1    row4col2
> When using proper table markup, it linearises to
> row1col1 row1col2 row2col1 row2col2 row3col1
> row3col2 row4col1 row4col2
> Now sometimes some gung-ho webdesigner prefers a
> nice blue background around
> the first column entries, and a nice green outline
> on the collection of col2
> elements, and instead of using stylesheets, he
> decides to use nested table -
> cos its easier.
> So the outer table has two cols and one row, and
> inside each cell he creates
> a four row one celled table.
> That linearises to
> row1col1 row2col1 row3col1 row4col1 row1col2
> row2col2 row3col2 row4col2
> Completely different to the first linearisation
> example - and its very hard
> for a non-visual browser user to make the correct
> relationship between the
> elements.
> The real world analogy to this is when reading a
> book, the first example you
> read starting from the first line and read all the
> words on that line, when
> you reaches the end of a line, you go back to the
> left hand side and start
> on the next line.
> The second example you must start at the top left,
> but you must read the
> first word on each line from top to bottom. When you
> reach the bottom of the
> page, you must go back to the top of the page, then
> read the second word in
> each line - as you can imagine, not an easy task to
> understand the content
> of the page at all.

Yahoo! Messenger - Nueva versión GRATIS
Super Webcam, voz, caritas animadas, y más...

Received on Friday, 27 June 2003 08:03:20 UTC