Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Table navigation (ctrl+alt+arrow keys) is not working after column headers are sorted while JAWS is running #856

Open
ashankggupta opened this issue Jul 30, 2024 · 1 comment

Comments

@ashankggupta
Copy link

Summary

While JAWS is running and after we activate the sortable table headers (column headers), table navigation keys (Ctrl+Alt+arrow keys) are not working as expected. The virtual focus does not moves to the cells in the table.
The table navigation keys works fine once 'Escape' key is pressed.

Please note that this is working fine with w3c sortable table example provided in the given URL: https://www.w3.org/WAI/ARIA/apg/patterns/table/examples/sortable-table/

Expected result

After activating the sortable table columns, table navigation keys should move the focus to the respective cells in the table.

Actual result

After activating the sortable table columns while JAWS is running, table navigation keys does not move the focus to the respective cells in the table unless 'Esc' key is pressed.

Example

<------Code Snippet----->

<table>
          <caption> Account Details </caption>
          <thead>
                 <tr>
                        <th role="columnheader" scope="col" aria-label="Account Number" tabindex="0" aria-sort="none">
                          Account Number
                          <span></span> // for sort icons
                        </th>
                        [...]
                 </tr>
          </thead>
          <tbody>
                      [...]
          </tbody>
</table>

Additional Information

JAWS version and build number

JAWS version 2024.2405.83

Operating System and version

Windows 10

Browser and version:

Chrome 127.0.6533.73

@BrettLewisVispero
Copy link
Collaborator

Can you provide a working example of where this fails? The APG page works as you said.
Thanks,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants