DataTables / DataTables/FixedHeader
Keyboard Accessibility
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 73
- Forks
- 83
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Description
I want to address three issues related to keyboard accessibility of the fixed header here. All of them can be seen in datatables_fixed_header_keyboard.zip.
- When activating a sort button in the fixed header using the keyboard, focus is lost.
- When tabbing through the complete page, the header is encountered twice, first in-place and then floating. This is because the fixed header is placed at the end of the body. Ideally, the fixed header should appear at the position in the tab order as the original header. When tabbing through the page in reverse order while the page is scrolled to the top, neither of the two headers will receive focus.
- Focus is not retained when switching between in-place and fixed header.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached datatables_fixed_header_keyboard.zip reproduction and inspect the fixed-header behavior for keyboard sorting, tabbing, and scrolling between the in-place and floating headers. Verify each of the three reported focus and tab-order problems, then confirm that focus is retained correctly and the header is encountered only in the intended position.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100