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

Not possible to trigger actions below reply input as a keyboard user? #194235

Closed
joyceerhl opened this issue Sep 26, 2023 · 7 comments
Closed

Not possible to trigger actions below reply input as a keyboard user? #194235

joyceerhl opened this issue Sep 26, 2023 · 7 comments
Assignees
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues polish Cleanup and polish issue
Milestone

Comments

@joyceerhl
Copy link
Contributor

joyceerhl commented Sep 26, 2023

Testing #194012

After I focus a comment, I can tab to the actions in the comments title area, but I don't see a way to get focus to the 'Resolve Conversation' button or the 'Make a Suggestion' button. 'Resolve Conversation' is at least exposed in the command palette, so it is triggerable with a keybinding, but I would expect the other actions to also be focusable or triggerable from the palette:

  • Make a Suggestion
  • Start Review
  • Add Comment

Image

@meganrogge
Copy link
Contributor

You need to enable tab moves focus mode, ctrl+m on windows.

We should probably add a keybinding for each of the actions.

@meganrogge
Copy link
Contributor

From a visual standpoint, the tab order looks funny (right to left), but IMO, it makes the most sense to have them prioritized as they are:

  • Add comment
  • Start review
  • Make a suggestion

@meganrogge
Copy link
Contributor

meganrogge commented Sep 26, 2023

We should also mention here that there are actions to be tabbed to and state that, to reach them, tab moves focus mode must be on.

Screenshot 2023-09-26 at 3 14 04 PM

@meganrogge meganrogge added bug Issue identified by VS Code Team member as probable bug accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues polish Cleanup and polish issue labels Sep 26, 2023
@meganrogge meganrogge added this to the September 2023 milestone Sep 26, 2023
@joyceerhl
Copy link
Contributor Author

I don't think we necessarily need keybindings for these, just exposing the functionality as commands in the palette would help

@alexr00
Copy link
Member

alexr00 commented Sep 27, 2023

These actions are contributed by GHPRI. I'll update their context so they show in the command palette when you're editing a comment.

@alexr00
Copy link
Member

alexr00 commented Sep 27, 2023

Actually, we close the comment editor when the command palette is shown, so I can't just make this change in the extension. I can look into this in October if we want to change it.

@alexr00
Copy link
Member

alexr00 commented Oct 4, 2023

I've looked into this further:

  • All the buttons are accessible when you use tab moves focus ✅
  • I can make the comment editor stay open when the command palette is opened, but any command executed from the command palette at this time will not have the correct comment context.

Since the buttons are accessible I'm going to close.

@alexr00 alexr00 closed this as completed Oct 4, 2023
@meganrogge meganrogge removed the bug Issue identified by VS Code Team member as probable bug label Oct 25, 2023
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 polish Cleanup and polish issue
Projects
None yet
Development

No branches or pull requests

3 participants