RE: Accessible tables

Hello,

I think you should follow W3C guidelines, as close as possible. I have never
tried using an empty summary attribute.

I know how the screen reader I use responds, and since I write the help for
it, I code for it. Since it is Microsoft HTML help, CHM format, I only have
to take into account IE - which is also the recommended browser for use with
my screen reader. So I am saying my perspective is rather restricted. I only
have to code for one browser, and my primary focus is only one disability
group.

I am a pragmatist. Writing perfectly compliant code seems to me an
intellectual excercise seldom applicable in the real world. In the real
world, there are stiff deadlines, resource limitations, and statistical
information on the audience who will use a site. I think accessible web
design is essential, but is most effective when the emphasis it receives
reflects the reality of the situation.

I think no matter how much we wish to strive towards universal
accessibility, these factors do come into play.

If I were writing a commercially accessed web site, I would code for the big
three browsers - market share wise - using JavaScript to sniff out the
browser in use and apply the best external style sheet I could devise for
it. Then I would make sure that with no JavaScript and no style sheet, the
site was still useable.  And it probably still would not be totally
accessible in Lynx, though I would try.

Brian

-----Original Message-----
From: Gerhard Schoening [mailto:g.sch(at)onlinehome.de]
Sent: Tuesday, February 26, 2002 6:36 PM
To: brian walker
Cc: aware-techniques(at)hwg.org
Subject: Re: Accessible tables


Hello Brian,

On Tuesday, February 26, 2002 at 23:58 you wrote:

> 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


Does that mean I should use an EMPTY summary attribute for non-data
tables, just like the empty alt attribute for non-relevant images
(like a spacer.gif)?


Gerhard



http://www.cp-web.com
gerhard(at)cp-web.com

http://www.schoening-online.com
gerhard(at)schoening-online.com

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