Skip to content
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

Closed
meganrogge opened this issue Apr 12, 2024 · 6 comments
Closed

SCM accessibility feedback #210255

meganrogge opened this issue Apr 12, 2024 · 6 comments
Assignees
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@meganrogge
Copy link
Contributor

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.

  1. focus commit message
  2. focus staged changes (not tabbable)
  3. focus changes (not tabbable)

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" }

@meganrogge meganrogge added accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug labels Apr 12, 2024
@meganrogge meganrogge added this to the May 2024 milestone Apr 12, 2024
@rzhao271 rzhao271 added verified Verification succeeded verification-steps-needed Steps to verify are needed for verification and removed verified Verification succeeded labels May 29, 2024
@rzhao271
Copy link
Contributor

I wasn't able to find any commands about focusing the staged changes. What are some verification steps for this issue?

@lszomoru
Copy link
Member

Verification steps:

  • Setup keybindings for the following commands:
    • workbench.scm.action.focusNextInput
    • workbench.scm.action.focusPreviousInput
    • workbench.scm.action.focusNextResourceGroup
    • workbench.scm.action.focusPreviousResourceGroup
  • Verify that the keybindings are working as expected

@lszomoru lszomoru removed the verification-steps-needed Steps to verify are needed for verification label May 29, 2024
@rzhao271 rzhao271 added the verified Verification succeeded label May 29, 2024
@rzhao271
Copy link
Contributor

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.

@lszomoru
Copy link
Member

Correct. The behaviour that you are describing is the intended one.

@meganrogge
Copy link
Contributor Author

@lszomoru, JooYoung was describing that it's confusing to have next and previous in the command description. We should have a command to focus the current input. cc @jooyounsgeo

@jooyoungseo
Copy link

jooyoungseo commented Jun 14, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants