Steps to reproduce the problem

1. Open NVDA.
2. Open the html file that is present in: "[wijmo-grid-sample.zip].
3. Open the sample in Chrome.
4. Move focus to the table by pressing TAB key.
5. Press ArrowLeft. Observation: The rowIndex part is announced as "row header row 8". Expected: The rowIndex part should be announced as "row header row 2".

Problem Description

Actual behavior:

The announcement that is done by NVDA for the focused gridcell is as follows (Speech Viewer Output with command keys ON):

tab
main landmark
table
US  row 2  Country  column 1
left arrow
row header  row 8
right arrow
US  row 2

Here, when "left arrow" key is pressed, rowIndex is identified as "8". Pressing the "right arrow" key announces the rowIndex as "2". In the same row two different index announcements for row are done.

Expected behavior:

The announcement that is done by NVDA in Firefox for the focused gridcell is as follows (Speech Viewer Output with command keys ON):

tab
main landmark
table
US  row 2  Country  column 1
left arrow
row header  selected
right arrow
US  selected

Here, no change in rowIndex is reported by NVDA when selection is shifted from gridcell to rowHeader cell. This is the expected behavior.

System configuration

NVDA installed

NVDA version: 2024.4 (2024.4.0.34423)

Windows version: Windows 11 Version 22H2 (OS Build 22621.2283)

Additional Information:

As this behavior is specific to Chrome/Edge + NVDA combination, I tried to look into the "Accessibility Internals" tab for the sample page (chrome://accessibiilty). I think that this might be related to how some other unexposed properties of Accessibility tree is calculated in Chromium. Therefore, I am reporting this issue here. Following are the findings from the accessibility tree displayed on "Accessibility Internals" page:

1. The value of ariaRowCount on the element with role grid is set as 14 instead of "7", the value that is explicitly provided using aria-rowcount attribute.
2. Even though the value of ariaCellRowIndex is "2" for an element with role row, but the internal calculated value for ariaCellRowIndex is "8" for the rowheader element present in that row. Below is the screenshot that demonstrates the same: [different_value_of_ariaCellRowIndex_for_row_and_rowHeader_cell_present_in_that_row.png]

Because of this I think NVDA is not able to convey the expected rowIndex for rowHeader cells.

Note: Currently the cells present in rowHeader and the first data cell (gridcell) in each row has aria-colindex as "1". I think this is not correct. But even after correcting the value of aria-colindex, the issue still persists. Also, Firefox is able to correctly identify the rowIndex for the rowHeader cells. So, I think this is something related to chromium.

Thank you.

Summary

aria-rowindex is not considered for calculating current rowIndex of a row in a grid.

Custom Questions

Which component does this fall under?

Not sure - I don't know

Does this work in other browsers?

Yes - This is just a Chrome problem

Additional Data

Category: API
Chrome Channel: Stable
Regression: No