-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
SCM accessibility feedback #210255
Comments
I wasn't able to find any commands about focusing the staged changes. What are some verification steps for this issue? |
Verification steps:
|
It seems like focusNextInput helps focus across repositories (such as in a multi-root workspace with changes in each repo) but that focusNextResourceGroup focuses across resource groups in a single repository. I initially expected focusNextResourceGroup to skip between repositories, but I think it is more structured to have one command skip between repositories and another command navigate within a repository. |
Correct. The behaviour that you are describing is the intended one. |
@lszomoru, JooYoung was describing that it's confusing to have |
Additionally, screen reader users and those who don’t have a visual perception of the Git tree layout need an explicit command to focus on the “Changes” and “Staged Changes” views. While the newly added "go to next" and "previous resource group" commands might serve as a workaround, they operate in a cycle mode rather than focusing directly on the user's intended target.
|
From @jooyoungseo
SCM view needs some commands exposed because atm, you have to focus the SCM view and then tab or use space/arrow keys to get to these.
We should add
!screenReaderEnabled
to this keybinding so users can review their commit messages without going up in history{ "key": "up", "command": "scm.viewPreviousCommit", "when": "scmInputIsInFirstPosition && scmRepository && !suggestWidgetVisible" }
The text was updated successfully, but these errors were encountered: