[Accessibility] Tab focus order and screen reader text for column headers

[ashutosh100]

Please make sure each of the following is true before submitting a new issue. We are a small team with limited time and it is very difficult to manage issues if they aren't reported correctly.

• This is a bug report, not a question on how to use the grid.
  Use Stack Overflow or Gitter for questions.
• You have searched the open issues to see if this bug has been filed before. We don't want duplicate issues.
• You have reviewed the tutorials and documentation to ensure you are using the grid correctly. ui-grid.info
• You are using the latest version of the grid. Older versions are not patched or supported.
• You have provided steps to recreate your bug. A plunkr is even better.

http://ui-grid.info/docs/#!/tutorial/Tutorial:%20121%20Grid%20Menu

Here's a gif from the tutorials site. As it can be seen, there are two issues:

• When the keyboard focus is on the checkbox in the header row, on pressing the tab key, focus goes to the checkbox in the next row instead of moving to the next column header.
• When the keyboard focus reaches the column headers, the screen reader announces the row and the column numbers incorrectly: In case of the 'Gender' header (3rd column header including the checkboxes), 'Column 2' is announced and for the complete header row, excluding the checkboxes is read as 'Row 19', counting 18 rows for the check boxes.

[Vijay-Panneerselvam]

Hi @mportuga , Even myself facing the same issue. Having a editiable ui-grid with "enableRowSelection" attribute value as true in gridOptions. Tried to Navigate using keyboard "tab" button, grid cell focus happening to the rowselector (selection) column by default.
At one point, focus randomly jumps to the different row selection cell as like as image attached by @ashutosh100 and same is happening if I simply scrolls the grid to the selection cell.

[lNarayananG]

+1.
Hi @mportuga, Even I face the same issue. In fact I have the grid display inside a modal dialog and have a custom logic to control the tab/focus retention with in the dialog. While trying to do so, facing issue in identifying whether the next focusable DOM element is within the dialog or not. It would be helpful if any sort of fix/workaround is provided for this observation.

Thanks and Cheers!!

[fsteffi]

hi when shall this issue be resolved as the primary bug is dependent on this fix to close their bug could we get the ETA please

[mohdsaad17]

Does the issue still exists?
If yes,i would like to take it up.
@fsteffi

[Vijay-Panneerselvam]

@mohdsaad17
Yes, Issue still exist.

[rohit-batra]

Any Updates on this ? @mohdsaad17

[prabhudevu]

Hi @mohdsaad17 Issue is still repro could you please take action and provide ETA of the fix. Because primary bug is dependent on this fix

[mohdsaad17]

Okay will work on it.thank you

…

On Fri, May 12, 2023, 16:05 prabhudevu ***@***.***> wrote: Hi @mohdsaad17 <https://github.com/mohdsaad17> Issue is still repro could you please take action and provide ETA of the fix. Because primary bug is dependent on this fix [image: 7147_Issue repro] <https://user-images.githubusercontent.com/98821792/237947128-626dea2b-758f-447f-88ab-0dc39c9c0ae8.png> — Reply to this email directly, view it on GitHub <#7147 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALQVUJJYATHGYZOS6AVMWZ3XFYG7HANCNFSM46BEBFKA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[prabhudevu]

Hi @mohdsaad17 could You please provide us the ETA for the fix. Because primary bug is dependent on this bug fix

[Vedant767]

Hi @prabhudevu , is this issue still open? can I take this issue?

[OmkarJ13]

+1 We are also facing this issue