I'm just guessing here, but JAWS could be identifying (hence reading) the table headers incorrectly. It could be a bug in the application that is presenting the tables or in JAWS itself. If it's a Web application, the developers need to follow certain standards in making the tables accessible.
Mr. Ed <[email protected]> wrote: > Hi Everyone, > > I have a friend that is having an issue using tables. Here is his issue > below. > > I am attempting to read some tables. Whether I use the layered JAWS > keystrokes or the old keyboard commands to read the table cells, this is > what I'm hearing. > > > > Column 2, Row 4 > Subject: No sort applied, activate to apply an ascending sort Subject: No > sort applied, activate to apply an ascending sort > Is roadmap still valid? > > > > The table reads beautifully except that JAWS is always saying, "No sort > applied, activate to apply an ascending sort Subject: No sort applied, > activate to apply an ascending sort". I want to get rid of this irritant! > > > > I have tried changing verbosity from beginner to advanced and vice versa, > and I still get this annoying message on every cell. I am running the latest > update of JAWS 18 on a Windows 10 Dell laptop. > > > > Thanks for any insights you may be able to share. > > > > > > > > For answers to frequently asked questions about this list visit: > http://www.jaws-users.com/help/ > For answers to frequently asked questions about this list visit: http://www.jaws-users.com/help/
