W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2000

Re: Screen readers and simple data tables

From: Steven McCaffrey <smccaffr@MAIL.NYSED.GOV>
Date: Thu, 06 Apr 2000 15:28:43 -0400
Message-Id: <s8ecad4c.076@mail.nysed.gov>
To: <paulb@cpd2.usu.edu>, <w3c-wai-ig@w3.org>

Paul:
I'll elaborate more tomorrow.
First, what version of JFW do you have?  I use 3.2, not the latest, and table support for web pages is virtually non-existent, (except for Reformat, Insert+f5 - have you tried this?.
It is important for all to keep in mind that all disabled persons do not have the latest versions of assistive tech.
Did you try viewing the table in Lynx, reading the Lynx transformed table with JFW?
Try saving the table as a MS Word doc, and reading the Word table with JFW.  Any better?
then, try saving the Word table as HTML and viewing this with JFW in IE.  Any difference?
I'll try all this myself tomorrow.  I'm just curious about a few things.
-Steve
 
 

   



Steve McCaffrey
Senior Programmer/Analyst
Information Technology Services
New York State Department of Education
(518)-473-3453
smccaffr@mail.nysed.gov
Member,
New York State Workgroup on Accessibility to Information Technology 
Web Design Subcommittee 
http://web.nysed.gov/cio/access/webdesignsubcommittee.html


>>> "Paul Bohman" <paulb@cpd2.usu.edu> 04/06/00 03:02PM >>>
I have a question about tables for those who use screen readers. Although,
for the most part, tables seem to be accessible with current screen reader
technology, there are definitely times when this is not the case. Even
simple data tables can be problematic due to the way which screen readers
read them.

For example, I have a page which has a simple table with four columns and
two rows. The first row consists of the headers and the second row consists
of the data. In this case, the data consists of links to issues of
newsletters. The column headers are the titles of the newsletters, and the
cells beneath them have links to the "current issue" and to "all issues".

The problem is that neither of the screen readers that I tested it on (JAWS
and Home Page Reader) gave enough information about the table to easily
decipher its structure. Even though JAWS told me that I was entering a table
with four columns and two rows, it did not tell me where one column started
or ended. Nor did it tell me where the first row ended and the second row
began.

I was frustrated. In my mind, there is no reason why the screen reader
wouldn't be able to give me this information. All of the information is
already in the code itself. JAWS knows where each row and column begin and
end. It just doesn't tell me what it knows.

As it stands right now, the simple table that I created is reduced to a
guessing game for those using screen readers. They have to try to figure out
what row and what column they are in. I see this as a problem with the
screen readers, rather than with the coding itself. I understand that I may
have to create a workaround. I am willing to do that, but I wanted to get
some feedback from those on the list who use screen readers to see what they
thought.

By the way, the table in question is found on the following page:
http://www.cpd.usu.edu/newsletters. To get to the table quickly, click on
the first link, which allows you to skip past the main navigational menu.

Thanks
Paul Bohman
Received on Thursday, 6 April 2000 15:31:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:13:48 GMT