continuedev / continuedev/continue

A11Y: Continue sidebar doesn't work with screen readers in VS code

Open
#12,325 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:sidebar ide:vscode kind:bug
Dominant language
TypeScript
Stars
36k
Forks
5.4k
PR merge metrics
No merged PRs in 30d

Description

Before submitting your bug report
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
  1. Turn on a screen reader. On windows press control+windows+enter or on Linux press super+alt+s.
  2. Open VS Code.
  3. Press control+i to open the chat
  4. Notice how difficult it is to use
Log output

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.