Re: Table evaluation

>
> > I think what the flowchart leaves out is how to decide whether a table is
>a
> > data or layout table...
> >
>The only sure way is to ask the author. We should consider giving some
>guidance to the author so they can make the decision. But what is the
>difference? Does not a data table 'layout' the data?

By saying that there are two types of tables we are trying to identify if a 
cell can exist on its own.  Data tables usually rely on some relationship 
between cells, whereas the cells of layout tables can usually exist on 
their own.

for example, if a table is used to layout a navigation bar, there is no 
"relationship" between the cells.  Yes, they are all related and thus 
grouped into a table, but they could each exist "on their own" on the page 
as a single piece of information.

a cell in a data table on the other hand, often needs a header to make 
sense.  for example, "33" does not make sense until associated with its 
header "jersey numbers of heisman winners."

Yes, the only way _to be sure_ which type of table it is, is to ask the 
author.  However, a few things could be tested:
1. if there are no TH elements, it might be used for layout.
or vice-versa, if there are TH elements, it might be used for data.
2. if there is only one column or one row it might be layout.

> > 1. A layout table can have either data tables or layout tables within it.
> > 2. A data table also might have data tables or layout tables within it.
> >
>Yes, I think both cases can occur.

definitely.

> > This would apply to any number of levels of nesting. However, if it got
>more
> > than a couple levels deep we might start to question whether the outer
>table
> > actually is a data table.
> >
>Yes, it muddies the data/layout table distinction.

yes.

--wendy

--
wendy a chisholm
world wide web consortium
web accessibility initiative
madison, wi usa
tel: +1 608 663 6346
/--

Received on Friday, 17 December 1999 17:55:23 UTC