Skip to content

Issues: microsoft/vscode

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.

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

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

Issues list

Copilot insert code block keybinding overrides commit action in the scm view accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug confirmation-pending
#230537 opened Oct 4, 2024 by meganrogge
indicate next edit suggestion availability to screen reader users accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues feature-request Request for new features or functionality
#230322 opened Oct 2, 2024 by meganrogge On Deck
[Accessibility with screen reader] NVDA switch automatically the language in the accessible view of the embedded terminal accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug
#230114 opened Sep 30, 2024 by michael-beuve
Change key icon in a11y view accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug
#229827 opened Sep 26, 2024 by Tyriar
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
#229607 opened Sep 24, 2024 by TeamDman
Accessible view buttons are always enabled even if can not cycle further accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug
#229560 opened Sep 24, 2024 by aiday-mar
Should opening "getting started with accessibility features" walkthrough start reading out the first block? accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues under-discussion Issue is under discussion for relevance, priority, approach
#229550 opened Sep 24, 2024 by ulugbekna
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
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
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
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
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
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
[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
[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
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
[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
[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
[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
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
[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
[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
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
ProTip! Type g i on any issue or pull request to go back to the issue listing page.