EASI Archives

Equal Access to Software & Information: (distribution list)

EASI@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
David Poehlman <[log in to unmask]>
Reply To:
* EASI: Equal Access to Software & Information
Date:
Mon, 17 Feb 2003 21:42:15 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (39 lines)
I see no value for this at all.  It clutters the braille display for one
thing and Where I have seen it all over the place, some times half a dozen
times on a page, it is a down right nuisence.

-----Original Message-----
From: Alan Cantor [mailto:[log in to unmask]]
Sent: Tuesday, 18 February 2003 4:18
To: [log in to unmask]
Subject: Web page layout tables


In an ideal world, web developers would never use tables to layout pages.
But we don't live in an ideal world, and web developers do organize web
pages visually using tables.

I have noticed that Jaws 4.5 does a pretty good job of navigating through
layout tables. I am curious whether people who rely on screen readers have
noticed this. Or are layout tables continue to be a bane.

I have been asked to comment on a proposed web standard. The standard
mandates that layout tables should only use the TABLE, TR, and TD elements;
and most interestingly, that the summary attribute always be used with
TABLE, and that it always say two words: "layout table." (Jaws and HPR both
detect the summary attribute; the current version of Window-Eyes does not.)

Screen reader users: would table attribute summary="layout table" be an
accessibility enhancement for you?

Alan



Alan Cantor
Project Manager
Strategic e-Government Implementation
e-Government, OCCS
416-212-1152
[log in to unmask]

ATOM RSS1 RSS2