gregnb / gregnb/mui-datatables
Initial sorting order not read by JAWS
- Dominant language
- JavaScript
- Stars
- 2.7k
- Forks
- 906
- PR merge metrics
- No merged PRs in 30d
Description
When you set an initial sorting order for a column, the arrow indicator shows that the column has been sorted but JAWS only reads Column 1 Sorted, it doesn't say if the sorting order (ASC or DESC). If you moved to the next column and then go back, then JAWS reads correctly the sorting order
## Expected Behavior
When JAWS reads correctly the sorting order on from the begining.
## Current Behavior
Explained at the begining
## Steps to Reproduce (for bugs)
1. Open a page that has a MUI-Datatable with at least a column that is sorted by the first column
2. Enable JAWS or NV Access
3. Navigate to the table using the keyboard and go to the sorted column
4. Hear that JAWS or NV Access say Column <> sorted
## Your Environment
| Tech | Version |
|--------------|---------|
| Material-UI | 4.11.1 |
| MUI-datatables | 3.7.7 |
| React | 17.0.5 |
| Browser | Firefox, Chrome, Chromium Edge |
| JAWS | 2021.2105.53 |
| NV Access | 2020.4 |
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the issue with a MUI-Datatable whose first column has an initial sort, using keyboard navigation with JAWS or NV Access in the listed browsers. Trace how the initially sorted column exposes its accessible sort state, then verify that the reader announces whether the order is ASC or DESC immediately, without leaving and returning to the column.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100