JAWS grid navigation is incorrect, when grid support custom keyboard navigation

[kolaps33]

Summary

1. Go to grid example: https://k2sc4d-5173.csb.app/
2. Navigate into the grid in virtual cursor mode
3. Use in the grid the ctrl+alt+up/down arrows key navigation to navigate in column 3

Expected result

User navigate in the column

Actual result

Navigation is broken and JAWS doesn't navigate to previous/next cell in the same column. JAWS navigates to different column. Please see enclosed video: https://github.com/FreedomScientific/standards-support/assets/22620150/836fc0a5-03ff-4664-8f61-eeef250bbba7

Example

code: https://codesandbox.io/p/devbox/k2sc4d?file=%2Fpackage.json example: https://k2sc4d-5173.csb.app/

Additional Information

During investigation we recognized that JAWS is broken because of one element which we use to support custom keyboard navigation for this grid. Please see screenshot below. The element has role="none" and has aria-hidden="true", so shouldn't be considered to the navigation during virtual cursor navigation with JAWS. The element looks like: <i tabindex="0" role="none" data-tabster-dummy="isFirst=true, isOutside=false, (Mover, tabbable=true), (Groupper, tabbable=true)" aria-hidden="true" style="position: fixed; height: 1px; width: 1px; opacity: 0.001; z-index: -1; content-visibility: hidden; top: 0px; left: 0px;"></i>

JAWS version and build number

2024.2312.53

Operating System and version

Windows 11 Enterprise

Browser and version:

Chrome Version 121.0.6167.185 (Official Build) (64-bit)