WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Reading tables in JAWS


From: Bryan Garaventa
Date: Feb 4, 2014 4:46PM

It depends on the type of content and the interaction model.

For example, the following table is an interactive ARIA Data Grid
and is designed to have one tab stop and to allow screen reader access using
the arrow keys.

However, the most basic types of table, as seen at
require the use of the Virtual Cursor to navigate them effectively.

Standard table navigation commands have existed for many years now, so it
really comes down to whether or not the AT user has had introductory
training on this type of screen reader functionality.

----- Original Message -----
From: "Olaf Drümmer" < <EMAIL REMOVED> >
To: "WebAIM Discussion List" < <EMAIL REMOVED> >
Sent: Tuesday, February 04, 2014 3:09 PM
Subject: Re: [WebAIM] Reading tables in JAWS

> On 4 Feb 2014, at 23:59, Don Mauck < <EMAIL REMOVED> > wrote:
>> Anyone that just uses the arrow keys or the tab keys will never be able
>> to successfully use and navigate tables using a screen reader.
> why is that? Aren't arrow keys a good default method to walk through a
> table?
> It would be a matter of setting user preferences to control how much
> accompanying information - on top of the cell's content - would be
> presented (like type of cell, applicable header cells, etc.)
> Olaf
> > >