RE: Accessible tables

As a screen reader user, I personally do not want layout tables identified
as such. It is just extra verbiage.

The table specific commands available through my screen reader are
intentionally not functional in tables with only one row. This works very
well.

I do not use summary attributes in the tables I create unless they are:

1. data tables
2. complex enough that a summary truly adds value, i.e. makes the table
easier to understand.

I may be blind, but I do not think it is that difficult to figure out.

However, I recognize that mileage may vary for others.

Brian

-----Original Message-----
From: owner-aware-techniques(at)hwg.org
[mailto:owner-aware-techniques(at)hwg.org]On Behalf Of Barry Johnson
Sent: Tuesday, February 26, 2002 3:05 PM
To: aware-techniques(at)hwg.org
Subject: Re: Accessible tables


Until all browsers recognize CSS, the Accesibility
Community has nothing against using tables for layout,
as long as they are identified as such...

Barry

--- Pam Ware <tam(at)gn.apc.org> wrote:
> At 10:59 26/02/02, Barry wrote:
> >But don't forget to use the summary attribute!
> ><table (size) (border) (etc) summary="Table used
> for
> >layout.">
> I thought the goal was to use tables only for table
> data, not for layout -
> and move towards CSS positioning? If so, any
> suggestions of how best to do
> that in order to include navigation bars, related
> links etc. as well as
> main page content?
> TIA,
> Pam
>


__________________________________________________
Do You Yahoo!?
Yahoo! Greetings - Send FREE e-cards for every occasion!
http://greetings.yahoo.com

HWG: hwg-basics mailing list archives, maintained by Webmasters @ IWA