Details
-
Bug
-
Resolution: Fixed
-
Low
-
4.20.0, 5.3.1
-
Severity 3 - Minor
-
Description
Issue Summary
The element is not accessible by keyboard alone and there is no conforming accessible version of the same functionality reachable from the non-conforming page.
Elements:
- Key
- Label
Location:
Present in the table section
Steps to Reproduce
- Open the homepage
- Navigate to the "Assets" link and activate it
- Navigate to "Search for object" and activate it
- navigate to the input field and search for the objects
- Search a query "ORDER BY "KEY" ASC"
- Navigate to mentioned interactive elements and observe that sort functionality is inaccessible.
Actual Results
The table headers such as “Key” and “Label” are used to sort the table in ascending and descending order but have not been marked up as buttons and they do not communicate when the column is sorted. Also, a keyboard support is missing for these interactive elements.
Expected Results
The table headers such as “Key” and “Label” should be accessible via keyboard keys and the state of sort order should be conveyed by a screen reader.
- Code mentioned instances using native <button> element or alternatively use role="button" and tabindex="0" within <th> element.
- When the sortable table headers such as “Key” and “Label” receive keyboard focus, they should be announced as buttons to screen reader users.
- When the button is activated to sort the column, add aria-sort to the <th>.
- 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 to 2nd example in the link- https://w3c.github.io/aria-practices/examples/grid/dataGrids.html
Screenshot
Workaround
Not Available
Bug Ref: 746811
Bulldog Ref:
Attachments
Issue Links
- mentioned in
-
Page Loading...