-
Notifications
You must be signed in to change notification settings - Fork 39.3k
Accessible view / Open Detected Link iteration #196644
Copy link
Copy link
Closed
Labels
accessibilityKeyboard, mouse, ARIA, vision, screen readers (non-specific) issuesKeyboard, mouse, ARIA, vision, screen readers (non-specific) issuesbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insidersterminal-accessibilityIssues related to the terminal help widget, accessibility buffer, or navigation modeIssues related to the terminal help widget, accessibility buffer, or navigation modeverifiedVerification succeededVerification succeeded
Milestone
Metadata
Metadata
Assignees
Labels
accessibilityKeyboard, mouse, ARIA, vision, screen readers (non-specific) issuesKeyboard, mouse, ARIA, vision, screen readers (non-specific) issuesbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insidersterminal-accessibilityIssues related to the terminal help widget, accessibility buffer, or navigation modeIssues related to the terminal help widget, accessibility buffer, or navigation modeverifiedVerification succeededVerification succeeded
Testing #193988
It seems like the accessible buffer always open in screen reader accessibility mode after the link quickpick is closed, even if it was not open before. This seems like a bug.
Also: it seems like Gitlens uses Ctrl+Shift+G as the start of its chords. With Gitlens installed, it overrides the keybinding, causing the editor to wait for another keypress.