Re: Table accessibility (was Re: headers attribute)

Hi Aurélien,

These test cases are a good start, what is also needed are some tables that
test the limits of the scope attribute, ie.
a table where the headers cannot be unambiguously defined using the scope
attribute, but can be using id/headers
attributes. Then these can be tested using screen readers, to see if
the headers can be interrogated successfully
in either table.


On 03/06/07, aurélien levy <aurelien.levy@free.fr> wrote:
>
>
> Finaly i have found some time :
> here is the test case
>
> http://www.fairytells.net/table_test_case/
>
> Aurélien
> >
> > After a good sleep i think the test case need more case to be fully
> > revelent so here is what is propose :
> >
> > - table without summary, th, scope or headers/id
> > - table with just empty summary
> > - table with just summary
> > - table with just scope
> > - table with just headers/id
> > - table with summary and th, scope or headers/id
> > - table with summary, th, and scope with just vertical reading
> > - table with summary, th, and scope with just horizontal reading
> > - table with summary, th, and scope with just horizontal reading
> > - table with summary, th, and scope with both reading order
> > - table with summary, th, and headers/id with just vertical reading
> > - table with summary, th, and headers/id with just horizontal reading
> > - table with summary, th, and headers/id with just horizontal reading
> > - table with summary, th, and headers/id with both reading order
> > - table with summary, th, headers/id and scope with both reading order
> >
> > I will make it live as soon as i can but maybe not today because it's
> > mother's day in France ;)
> >
> > Aurélien
>
>
>


-- 
with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org