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

make expandable hover content accessible to screen reader users #207592

Closed
meganrogge opened this issue Mar 13, 2024 · 6 comments
Closed

make expandable hover content accessible to screen reader users #207592

meganrogge opened this issue Mar 13, 2024 · 6 comments
Assignees
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues feature-request Request for new features or functionality insiders-released Patch has been released in VS Code Insiders on-testplan
Milestone

Comments

@meganrogge
Copy link
Contributor

We will want to indicate that the expand / contract context actions in a hover exist to screen reader users.

When these are present, we should add an AccessibililtyVerbositySetting and hint to the hover's aria label that tells a user to open a help dialog, where we can indicate these actions, what they do, and the keybindings.

Image

@meganrogge meganrogge added accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues feature-request Request for new features or functionality labels Mar 13, 2024
@meganrogge meganrogge added this to the April 2024 milestone Mar 13, 2024
@meganrogge
Copy link
Contributor Author

We will also probably want to support these actions in the accessible view, similar to what we do with next and previous in the chat response accessible view so users don't have to navigate bw the widget and the accessible view.

@meganrogge
Copy link
Contributor Author

@aiday-mar I'm not sure what the current status of this is. Should we work on this in May?

@aiday-mar
Copy link
Contributor

Hi @meganrogge thank you for pinging on this issue. The PR on making the hover expandable is not merged yet, we are planning on merging it beginning of next iteration. Here is the link #204721. Perhaps after this is done, we can look into making the hover more accessible?

@meganrogge meganrogge modified the milestones: April 2024, May 2024 Apr 17, 2024
@meganrogge meganrogge modified the milestones: May 2024, June 2024 Apr 29, 2024
@aiday-mar
Copy link
Contributor

fixed by: #212783

@benibenj benibenj added the unreleased Patch has not yet been released in VS Code Insiders label May 28, 2024
@aiday-mar aiday-mar added verification-needed Verification of issue is requested on-testplan and removed verification-needed Verification of issue is requested labels May 28, 2024
@VSCodeTriageBot VSCodeTriageBot removed the unreleased Patch has not yet been released in VS Code Insiders label May 28, 2024
@VSCodeTriageBot
Copy link
Collaborator

Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting \closedWith someCommitSha, or directly add the insiders-released label if you know this has already been releaased

@VSCodeTriageBot VSCodeTriageBot added the unreleased Patch has not yet been released in VS Code Insiders label May 28, 2024
@aiday-mar
Copy link
Contributor

\closedWith 7f55a08

@VSCodeTriageBot VSCodeTriageBot added insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels May 28, 2024
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 feature-request Request for new features or functionality insiders-released Patch has been released in VS Code Insiders on-testplan
Projects
None yet
Development

No branches or pull requests

4 participants