Jaws is skipping from Row 1 to Row 3 when using table shortcut Ctrl + Alt + Down arrow

[sarahkang58]

Summary

1. Go to https://developer.microsoft.com/en-us/fluentui#/controls/web/detailslist
2. Press T to navigate to the table (located in the section titled 'Usage'
3. Use Ctrl + Alt + Right arrow to navigate to the second column with the header 'Name'
4. Use Ctrl + Alt + Down arrow to navigate to the next row
5. Notice how JAWS skips to the 3rd row and reads out 'Amet consectetur.one'

Expected result

Starting from Row 1, Column 2, when using Ctrl + Alt + Down, I expect JAWS to navigate to the 2nd row and read out 'Lorem ipsum.csv'

Actual result

Instead, JAWS skips Row 2 and navigates straight to the 3rd row and reads out 'Amet consectetur.one'

Example

See Summary section above

Additional Information

JAWS version and build number

I am using version JAWS 2020

Operating System and version

Edition: Windows 10 Enterprise Version: 20H2

Browser and version:

Chrome, Version 88.0.4324.104

[JAWS-test]

This is a bug of the Microsoft table.

The error is that the second row is marked with aria-rowindex=1 and not with aria-rowindex=2. That is why it is skipped. If the wrong rowindex is removed, JAWS navigation is correct because JAWS always switches from the first to the second row.

Freedom Scientific should check that tables are correctly navigable regardless of rowindex and colindex, and rowindex and colindex are only used to output the number of row and column. Because: if rowindex=1 is followed by rowindex=3, JAWS will not output an empty row.

[JAWS-test]

JAWS skips certain rows, e.g. with the same aria-rowindex or with aria-rowindex larger than the largest implicit rowindex. I.e. JAWS does not output certain rows. This does seem to be a bug that should be fixed.

See https://codepen.io/jaws-test/pen/oNYvaRj and https://github.com/w3c/aria/issues/1386

[accessiblecohn]

Still an open issues in the standards body.