search

FreedomScientific / standards-support

Contains documentation for Vispero software support of Web standards
https://freedomscientific.github.io/standards-support/
GNU General Public License v3.0
111 stars 12 forks source link

JAWS in Chrome reads incorrect row and column in <tr> <td> elements #523

Open NicholasEckardtEpic opened 3 years ago

NicholasEckardtEpic commented 3 years ago

Summary

Brief description of the issue. Please list any specific steps.

When you use JAWS to tab through an HTML table of elements which contain tags, JAWS will only sometimes read out row and column information. When JAWS does read out row and column information, it does so only when tabbing forward, and outputs incorrect row and column number.

Expected result

  1. I expected JAWS to read out the correct row and column when I tab to a specific item.
  2. I expected JAWS to either always read out column and row number when tabbing through, or never reading out column and row numbers.

Actual result

  1. JAWS reads out column and row numbers as if they were zero indexed, which does not seem right.
  2. JAWS only reads out column + row information when entering the second element of a row which is confusing.

Example

Example:

  1. Go to https://codepen.io/NicholasEckardtEpic/pen/NWpWqgP
  2. Tab through the table using JAWS in Chrome
  3. When you reach the second row and second column, JAWS reads out "Column 1 Row 1"
  4. Jaws also reads out incorrect rows/columns when you tab from Column 1 row n to column 2 row n where n > 1.

Additional Information

JAWS version and build number

Operating System and version

Edition Windows 10 Enterprise Version 20H2 Installed on ‎4/‎22/‎2021 OS build 19042.928 Experience Windows Feature Experience Pack 120.2212.551.0

Browser and version:

Google Chrome 90.0.4430.93 (Official Build) (32-bit)

JAWS-test commented 3 years ago

I can confirm the bug.

However, I would like to point out that the example is not entirely correct: In a grid, you do not navigate with Tab key, but with the arrow keys. It would be necessary to check whether the problem also occurs with arrow key navigation (see https://www.w3.org/TR/wai-aria-practices-1.2/#grid)

The problem does not occur if role=table is used instead of role=grid.

The problem also does not occur with role=grid when navigating through the table with the virtual cursor (with Ctrl+Alt+Arrow keys).

NicholasEckardtEpic commented 3 years ago

However, I would like to point out that the example is not entirely correct: In a grid, you do not navigate with Tab key, but with the arrow keys. It would be necessary to check whether the problem also occurs with arrow key navigation (see https://www.w3.org/TR/wai-aria-practices-1.2/#grid)

Internally where I work the issue also appears when I use the arrow keys to navigate the grid. I can't paste our internal code to a third party site, but if it is necessary to solve the issue I can add arrow key navigation support to my grid example. Let me know if I should do this.

JAWS-test commented 3 years ago

Let me know if I should do this.

I am not from Freedom Scientific, so I cannot answer the question

HarrisonPretel-EpicSystems commented 1 year ago

Confirming that this bug affects JAWS 2022.2207.25 Browser: Chrome 107.0.5304.122 OS: Windows 10