WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Reading tables in JAWS

for

From: Roger Hudson
Date: Feb 4, 2014 3:29PM

Not all screen readers have the same capabilities when it comes to data
tables, and we shouldn't assume all screen reader users use them in the same
way. I recently observed a sight impaired JAWS user, with many years
experience, who to my surprise used a data table with just the arrow keys.
This person seemed genuinely surprised when I demonstrated the
alt+cTRL+arrow keys and alt+crtl+5 shortcuts.

Roger

-----Original Message-----
From: Hewitt,Susan (DSHS) [mailto: <EMAIL REMOVED> ]
Sent: Wednesday, 5 February 2014 8:53 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Reading tables in JAWS

> Most of my users cannot afford JAWS, but they should be able to access my
content using NVDA or VoiceOver with a similar experience!

Semantic coding (scopes, header & id attributes on tables, etc.) is
definitely the best way to try and reach this goal. Personally, I don't
know of how to code specifically for one type of screen reader but I do know
how to write accessible, semantic HTML.

From Steve,
> The only person I can recall who did use table navigation was a JAWS
trainer, and even he could make no sense of complex tables with either
multiple levels of headings >or colspans or rowspans.

He must not have known of the Ctrl-Alt-Num Pad 5 shortcut which tells
exactly where you are in the table with all applicable headers. (Assuming
the person who made the site coded it accessibly. ;)

I'm curious to hear from actual AT users so shall say no more on this topic.
Also, it's time to go home.

Susan

-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of Ron Stewart
Sent: Tuesday, February 04, 2014 3:46 PM
To: 'WebAIM Discussion List'
Subject: Re: [WebAIM] Reading tables in JAWS

Good afternoon,

I think this reflects a common misconception of AT users that is very
detrimental to our ongoing accessibility work. The vast majority of users
of AT, like screen readers, tend to use less than 10% of their
functionality, just like most software users. It is critical to efficient
use of content that good semantic markup be used. Why should I have to hit
hundreds of keystrokes when if the content was properly marked up I could
get to it much more efficiently.

The second would be that you cannot just design for JAWS accessibility you
need to base your design on accepted standards using OS keyboard commands.
Most of my users cannot afford JAWS, but they should be able to access my
content using NVDA or VoiceOver with a similar experience!

Ron Stewart

-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of Hewitt,Susan
(DSHS)
Sent: Tuesday, February 04, 2014 3:34 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Reading tables in JAWS

That has not been my observation with JAWS users. Granted, it has a big
learning curve so newer users may be unfamiliar with all of its features.
But experienced users are not reading every page continuously (in fact I
think most rarely do this.) This is why it's important to use semantic
markup. It's much easier for the user to navigate the page by heading, or
links, or landmarks - whatever helps them find what they're looking for.

As far as tables...can you imagine just arrowing down or reading a large,
complex table continuously? Without the JAWS table commands - and a properly
marked up table - it easily can become impossible for a user to understand
that table..

-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of Andrews, David B
(DEED)
Sent: Tuesday, February 04, 2014 3:25 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Reading tables in JAWS

JAWS does have a set of "table reading commands," but it is my observation
that most users don't know, or use them. Most people just arrow down, or
read continuously, I suspect.

Dave



-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of Johnson, Melissa
Sent: Thursday, January 30, 2014 11:19 AM
To: <EMAIL REMOVED>
Subject: [WebAIM] Reading tables in JAWS

Hi all,

I'm trying to better understand how JAWS users read tables. I have my own
expectations of what I think JAWS should do, however, these are based on how
I view the Web as a sighted user. Any insight as to how actual users of JAWS
software scan and read tables is greatly appreciated, as are any links to
additional information. (Note that I have reviewed the WebAIM information,
WCAG 2.0, various YouTube videos, and a few other random sites.)

Thank you in advance,

Melissa

Melissa Johnson

Senior Instructional Designer | Professional Services | Pearson eCollege
tel: 303.658.1647 | email: <EMAIL REMOVED>

Pearson
Always Learning
messages to <EMAIL REMOVED>


messages to <EMAIL REMOVED>
messages to <EMAIL REMOVED>

messages to <EMAIL REMOVED>
messages to <EMAIL REMOVED>