WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: JAWS Table behavior

for

From: Ted
Date: Sep 24, 2010 2:57AM

Please be aware that there was a bug in the first version of JAWS 11 with
respect to reading table headers properly.
There was an update in April which fixed the problem.

For more details please see
http://www.pws-ltd.com/sections/articles/2010/jaws_update.html

Ted Page
Director, PWS Ltd

Registered in England no. 06508410.
Registered office: 4 Riverview, Walnut Tree Close, Guildford, Surrey GU1 4UX


-----Original Message-----
From: David Farough [mailto: <EMAIL REMOVED> ]
Sent: 23 September 2010 18:28
To: <EMAIL REMOVED>
Subject: Re: [WebAIM] JAWS Table behavior


I tried your tables using versions 9 10 and 11 of Jaws.
Both tables were read properly in all versions of jaws when using the proper
table navigation keys. (control + alt and left, right, up and down arrow
keys) is it possible that the user was just arrowing through the text
without using the control + alt arrow keystrokes? Jaws should be set to
announce tables using both row and column or marked headers. the other
settings include announcing table rows or announce table titles off. .

David Farough
Application Accessibility Coordinator/coordonateur de l'accessibilité
Information Technology Services Directorate /
Direction des services d'information technologiques
Public Service Commission / Commission de la fonction publique Email /
Courriel: <EMAIL REMOVED>
Tel. / Tél: (613) 992-2779

>>> Mary Stores < <EMAIL REMOVED> > 12:38 PM Thursday, September 23,
2010 >>>
Hello,

I'm fairly new to list.

I'm using JAWS 11, IE 8, and Windows XP. When I used the table reading

keystrokes (ctrl+Alt+ Left, Right, Up, or Down arrow), JAWS did
announce when you move to a new column or when you were at the end of

a row for both tables. In the first table, for example: JAWS reads the

following in the 2nd row:

Categories. Major Column 1
Categories. Minor. Column 2
Past. FY 01. Column 3
Past. FY 02. Column 4
Future. FY 03. Column 5
Future. FY04 Column 6

If I read the second row in the second table, JAWS reads the same
imformation as above in the very same way.

Mary

Quoting "Langum, Michael J" < <EMAIL REMOVED> >:

> James,
>
> Thanks for the heads up on the case sensitivity issue. I have
updated
> the file.
>
> But I don't think that explains why JAWS is not voicing the column and
> row head information when it moves from cell to cell.
>
> Do you have any insight on that?
> -- Mike
>
> -----Original Message-----
> From: <EMAIL REMOVED>
> [mailto: <EMAIL REMOVED> ] On Behalf Of James
> Nurthen
> Sent: Thursday, September 23, 2010 12:05 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] JAWS Table behavior
>
> Mike,
> In the second table your ids are not of consistent case. id is
> case-sensitive yet you have some references to them in the headers
> attribute with initcap and some in all lower case. Regards,
> James
>
>
> On Thu, Sep 23, 2010 at 08:44, Langum, Michael J
> < <EMAIL REMOVED> >wrote:
>
>> I have created a page to test alternate ways of coding a complex
data
>> table. In one case I use "scope" attributes. In the second case, I
use "id"
>> and "headers" attributes. The page is at
>> http://www.opm.gov/_mike/jaws-test/tabledemo.asp. I wanted to
compare
>> the way JAWS provides column and row header information in these
two
>> constructions.
>>
>> When I asked a friend who is a JAWS user to test the page, JAWS did
>> not voice any of the column and row heads. It has always been my
>> understanding that when JAWS navigates from data cell to data cell,
it
>> would voice the column or row head value that changed before it
voiced
>> the value of data cell. Am I misinformed about how JAWS handles
>> column and row heads?
>>
>> Can someone look at the code, and tell me why JAWS did not voice
the
>> values of the column and row heads
>>
>>
>> -- Mike
>>
>>