accessibility issue: screen reader can't access context/action menu for each requests/folder/collection
- Dominant language
- TypeScript
- Stars
- 40k
- Forks
- 2.4k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 61
Description
### Expected Behavior
The expected behaviour is screen reader able to activate the context/action menu or the menu next to the items (request, folder, collection or any elements that have menu).
The usual way is either pressing application key on keyboard to activate the menu, or pressing tab key to reach the menu then spacebar/enter to activate.
### Actual Behavior
Currently, I can press tab key to reach the request and collection sidebar, then I can use up down arrow key to move the focus.
However, when trying to access the context menu for each element (E.G request), There is no way to access it. in screen reader browse mode, it sometimes can read the context button menu , but when enter on it, it has no effect and disappear altogether.
As result, if I want to access the context/action menu to rename or perform the function located under the menu. It is not reachable.
### Reproduction Steps
1. Open a collection.
2. press tab key until screen reader reads 'request and collection table'
3. we can up down arrow to move through the items in the table.
4. But, when I want to activate the context/action menu of each item, could not do so.
### Is there an existing issue for this?
- [x] I have searched the [issue tracker](https://www.github.com/Kong/insomnia/issues) for this problem.
### Which sync method do you use?
- [ ] Git sync.
- [ ] Insomnia Cloud sync.
- [x] Local only
### Additional Information
_No response_
### Insomnia Version
Version: Insomnia 12.1.0 Build date: 11/21/2025 OS: Windows_NT x64 10.0.26200 Electron: 38.4.0 Node: 22.20.0 Node ABI: 139 V8: 14.0.365.10-electron.0 Architecture: x64
### What operating system are you using?
Windows
### Operating System Version
Windows 11 pro 25H2 (OS Build 26200.7171)
### Installation method
download from official site
### Last Known Working Insomnia version
_No response_
Contributor guide
Research direction
Start by reproducing the issue in the request, folder, and collection sidebar on Windows with a screen reader, using keyboard navigation and activation. Done means each item's context or action menu can be reached and activated reliably with the keyboard and announced correctly by the screen reader.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, typescript
- Domain
- accessibility, desktop, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100