Skip to content

Issues: microsoft/vscode

Iteration Plan for September 2024
#228053 opened Sep 10, 2024 by kieferrm
Open 4
September 2024 Endgame
#229337 opened Sep 23, 2024 by bpasero
Open
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
264 Open 2,382 Closed
264 Open 2,382 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

accessibility.signals.progress gets stuck in an always-chiming state accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug notebook-accessibility triage-needed
#229607 opened Sep 24, 2024 by TeamDman
@amunger @meganrogge
1
[Accessibility] quick chat accessibility help has wrong keybindings for going bw chat response and input accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug
#229527 opened Sep 24, 2024 by jooyoungseo October 2024
@meganrogge
3
Screen reader is not announcing control name present in top menu navigation and left navigation on hovering with mouse in mouse tracking on mode:A11y_Visual Studio Code Client_Home screen_ScreenReader accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues
#229478 opened Sep 24, 2024 by kapilvaishna
@meganrogge
3
Remove auto as a type for accessibility.voice.autoSynthesize accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues feature-request Request for new features or functionality
#229403 opened Sep 23, 2024 by meganrogge October 2024
@meganrogge
3
REPL editor - allow sending focus to the added cell when executing from another file accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues feature-request Request for new features or functionality
#229182 opened Sep 20, 2024 by amunger Backlog
@amunger
REPL editor - play accessibility signals to indicate execution accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues feature-request Request for new features or functionality interactive-window
#229181 opened Sep 20, 2024 by amunger Backlog
@amunger
[Accessibility] Accessible Help contains deprecated info in Chat accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug
#229059 opened Sep 19, 2024 by jooyoungseo October 2024
@meganrogge
2
Edit Context: Screen Reader Users Feedback accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues editor-edit-context
#229051 opened Sep 19, 2024 by aiday-mar
@aiday-mar
7
Consider how we might improve navigation to chat response content for screen reader users accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues under-discussion Issue is under discussion for relevance, priority, approach
#228599 opened Sep 13, 2024 by meganrogge
@roblourens @meganrogge
1
Chat: Next File Tree does not work accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug
#228597 opened Sep 13, 2024 by meganrogge
@roblourens
[Accessibility] Chat show: make delete key work to remove focused history accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues feature-request Request for new features or functionality under-discussion Issue is under discussion for relevance, priority, approach
#228035 opened Sep 9, 2024 by jooyoungseo Backlog Candidates
@TylerLeonhardt @meganrogge
5
[Accessibility] Support Accessible Help (Alt+F1) in Merging Editor accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues feature-request Request for new features or functionality merge-editor
#227844 opened Sep 6, 2024 by jooyoungseo October 2024
@hediet @meganrogge
Accessibility] Add aria labels to each of the merging editor split panes accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug merge-editor
#227843 opened Sep 6, 2024 by jooyoungseo October 2024
@hediet @meganrogge
[Accessibility] Use more descriptive command names in merging editor accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug merge-editor
#227842 opened Sep 6, 2024 by jooyoungseo October 2024
@hediet @meganrogge
[Accessibility] Add focus right or left merging editor command accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues feature-request Request for new features or functionality merge-editor
#227841 opened Sep 6, 2024 by jooyoungseo October 2024
@hediet @meganrogge
[Accessibility] No progress indicator is provided for Copilot review accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug workbench-notifications Notification widget issues
#227823 opened Sep 6, 2024 by jooyoungseo October 2024
@meganrogge
10
Create command for go to current /active break point in the editor accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality
#227775 opened Sep 6, 2024 by balajip881 Backlog Candidates
@connor4312 @meganrogge
3
[Accessibility] The tree structure following anyfileName or when the three dots are expanded lacks a proper organization. accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues confirmation-pending
#227582 opened Sep 4, 2024 by Krituhar
@meganrogge
2
[Accessibility] The Explorer section view needs role and name information. accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug
#227580 opened Sep 4, 2024 by Krituhar
@lramos15
[Accessibility] The dragging movement in split panel functionality needs a single pointer trigger. accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug sash-widget
#227579 opened Sep 4, 2024 by Krituhar
@joaomoreno @meganrogge
2
Content Lacks Proper Heading Markup accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug settings-editor VS Code settings editor issues
#227528 opened Sep 4, 2024 by Bluefish0558 Backlog
@rzhao271
Headings with Mismatched Levels Affecting Accessibility accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues under-discussion Issue is under discussion for relevance, priority, approach
#227522 opened Sep 4, 2024 by Bluefish0558
@meganrogge
1
Controls Missing Proper Menu Structure and ARIA Attributes accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug
#227521 opened Sep 4, 2024 by Bluefish0558
@jrieken @meganrogge
1
Buttons with Insufficiently Descriptive Accessible Names accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues feature-request Request for new features or functionality under-discussion Issue is under discussion for relevance, priority, approach
#227519 opened Sep 4, 2024 by Bluefish0558 Backlog Candidates
@meganrogge
3
Status Bar Updates Missing Live Region Indication accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug under-discussion Issue is under discussion for relevance, priority, approach workbench-status Status bar
#227512 opened Sep 4, 2024 by Bluefish0558
@meganrogge
3
ProTip! Exclude everything labeled bug with -label:bug.