Details
-
Bug
-
Resolution: Duplicate
-
High
-
None
-
8.20.1
-
- 4.1.2
- AXSR-15
- Level-A
- WCAG21
- accessibility
- ax-at-JAWS
- ax-at-NVDA
- ax-at-VO
- ax-at-user
- ax-bug
- ax-customer-escalated
- ax-desktop
- ax-dev-ready
- ax-esc-boa
- ax-high-priority
- ax-jira
- ax-kb-user
- ax-macos-safari
- ax-platform-dc
- ax-qa
- ax-qa-bl
- ax-qa-prioritised
- ax-vpat-serious
- ax-windows-chrome
- ax-windows-firefox
- axsr-high-priority
- axsr-march-22
- ozghonnyk
-
8.2
-
Severity 2 - Major
-
Description
Steps to reproduce:
- Navigate to the "Assign to me" data table present in the main region of page.
- Using Tab key try to navigate to the "P" column’s sort by priority interactive element.
Screen recording:
Actual behaviour:
Keyboard users are unable to use the sort functionality as the sort interactive element fails to receive Tab focus. In addition, when screen reader users try to navigate to the sort element, it does not announce correct role of button to them. Thus they might have difficulties in accessing the sort functionality.
Expected result:
Expected result:
The sort functionality should be accessible for keyboard only as well as screen reader users.
- The "P" sort button should receive a tab stop when users try to navigate through the table using Tab key.
- When the sortable table headers such as "P" receive keyboard focus, they should be announced as buttons to screen reader users.
- When screen reader users navigate through the table columns in "Read" mode, the current sort order should be announced to them.
- On activating the sort button, the value of "aria-sort" should be updated programmatically with the focus staying on the sort button itself.
For more information on implementation, please refer 2nd example in link- https://w3c.github.io/aria-practices/examples/grid/dataGrids.html
AXQA Ref:AXQA-143
Attachments
Issue Links
- is duplicated by
-
JRASERVER-73400 Browse Pojects : Inaccessible by keyboard and no conforming alternative.
- Closed
- is resolved by
-
JRASERVER-73287 System Dashboard - Assigned to me : sortable table headers are not accessible for keyboard & screen reader users.
- Closed