Chat messages are not accessible via keyboard navigation
Open
Nobody has claimed this yet.
accessibility
bug
design
feature: chat 💬
feature: frontend 🖌️
medium
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
Steps to reproduce
- Open a Talk conversation
- Use only the keyboard with Tab-navigation and enter
- Try to go to a link in a message or use the reply button (e.g. try shift-Tab from inside the new message input field)
Expected behaviour
It works just fine to navigate between messages, replying as well as going to links and opening files which were sent.
Actual behaviour
It is impossible to navigate the message list via keyboard. Shift-Tab from the message field doesn’t go further up than the attachment button.
(This is on our own instance so easy to test @ma12-co )
Contributor guide
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
Reproduce the issue in a Talk conversation using only Tab, Enter, and Shift-Tab, including links, reply controls, and sent files. Trace the message list and new-message input focus order; it is done when messages, links, files, and reply actions are reachable and usable entirely from the keyboard.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100