nvaccess / nvda

NVDA, the free and open source Screen Reader for Microsoft Windows
Other
2.03k stars 625 forks source link

Aria rowIndex not read correctly in table with pinned/frozen columns #11551

Open jmikolay22 opened 3 years ago

jmikolay22 commented 3 years ago

Grids with rows that are represented across two elements ( pinned row and unpinned row ) do not read out with the same row index despite having same rowIndex on each element.

Steps to reproduce:

  1. Go to https://www.ag-grid.com/javascript-grid-pinning/
  2. Select a cell in the table

Actual behavior:

Cells clicked on in an unpinned/unfrozen column readout there row index differently then what is assigned to the aria-rowIndex value in the dom.

Expected behavior:

Cells clicked on in an unpinned/unfrozen column should readout the row index that is assigned to them in the dom.

System configuration

NVDA installed/portable/running from source:

NVDA isntalled

NVDA version:

2020.2

Windows version:

Windows 10

Name and version of other software in use when reproducing the issue:

Google Chrome V85

Other information about your system:

Other questions

Does the issue still occur after restarting your computer?

Yes

Have you tried any other versions of NVDA? If so, please report their behaviors.

No

If addons are disabled, is your problem still occuring?

Yes

Did you try to run the COM registry fixing tool in NVDA menu / tools?

No

m4theushw commented 1 year ago

I also have this problem in https://github.com/mui/mui-x/issues/5568. It seems that NVDA ignores completely aria-rowindex and reads the row index as the index relative to all role=row elements.