E-mail List Archives
Thread: summary attribute on layout vs data tables
Number of posts in this thread: 2 (In chronological order)
From: Leo Smith
Date: Wed, Nov 27 2002 8:51AM
Subject: summary attribute on layout vs data tables
No previous message | Next message →
Hi Folks,
I remember a while back there was some discussion on the list
about the usefulness of providing summary attributes on layout
tables.
Is it generally the consensus that summary attributes for layout
tables of the type "this table is for layout purposes only" are
somewhat redundant, and even annoying for screen reader users to
have to listen to?
(as long as the information laid out in the table linearizes OK, is
there any use in telling screen reader users that the table is for
layout purposes only?).
Is the summary attribute only really useful when describing data
tables?
Thanks and Happy Holidays!!
Leo.
Leo Smith
Web Designer/Developer
USM Office of Publications and Marketing
University of Southern Maine
207-780-4774
----
To subscribe, unsubscribe, or view list archives,
visit http://www.webaim.org/discussion/
From: John Foliot - bytown internet
Date: Wed, Nov 27 2002 9:08AM
Subject: RE: summary attribute on layout vs data tables
← Previous message | No next message
Short answer... yep. you got it.
In my demonstration sessions, whenever I encounter this type of redundancy,
I turn to the authors/group and say "This is a pen... I use it to write...".
It kinda drives home the point.
Some policies however insist that a Table Summary be present on *ALL*
tables, to which I can only say that the attribute 'summary="" ' will both
validate and satisfy 'ol Bobby (the none-thinking robot-tool with too much
clout)
(Interesting aside... if you run the Bobby on-line test, the resulting page
returns the following <title>Untitled</title>. Yep, real accessible...)
JF
>