continuedev / continuedev/continue
A11Y: Continue sidebar doesn't work with screen readers in VS code
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Before submitting your bug report
- I've tried using the "Ask AI" feature on the Continue docs site to see if the docs have an answer
- I'm not able to find a related conversation on GitHub discussions that reports the same bug
- I'm not able to find an open issue that reports the same bug
- I've seen the troubleshooting guide on the Continue Docs
Relevant environment info
- OS: Ubuntu 26.04
- Continue version: any
- IDE version:
- Model:
- config:
OR link to agent in Continue hub:
Description
I am blind so use the Orca screen reader on Ubuntu. I set up Continue in VS Code and can't really use the chat interface. It seems like there are pretty much no labels on things, I can't read the chat response/history, and it seems like the chat doesn't interact with VS Codes accessibility settings so none of the audio announcements work to help me have more context.
To reproduce
- Turn on a screen reader. On windows press control+windows+enter or on Linux press super+alt+s.
- Open VS Code.
- Press control+i to open the chat
- Notice how difficult it is to use
Log output
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
Start by reproducing the issue from the VS Code chat opened with Ctrl+I, using Orca on Ubuntu and checking VS Code accessibility settings. Inspect the chat interface entry points and compare labels, chat response/history reading, and audio announcements with accessible VS Code behavior. Done means the reported chat interactions are usable with a screen reader.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- accessibility, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100