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

Testing #203089 : Alerts are read but text in editor is no longer read #203113

Closed
aiday-mar opened this issue Jan 23, 2024 · 6 comments · Fixed by #203357
Closed

Testing #203089 : Alerts are read but text in editor is no longer read #203113

aiday-mar opened this issue Jan 23, 2024 · 6 comments · Fixed by #203357
Assignees
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders verified Verification succeeded

Comments

@aiday-mar
Copy link
Contributor

Testing #203089

While testing I noticed that when I moved my cursor on a line with an error, the word error was read, but the contents of that line were no longer read. I was wondering if this is intended?

I noticed that sometimes the beginning of the text on the line is read, before it breaks off and reads the alerts.

Screen.Recording.2024-01-23.at.09.51.11.mov
@aiday-mar aiday-mar changed the title Alerts are read but text in editor is no longer read Testing #203089 : Alerts are read but text in editor is no longer read Jan 23, 2024
@aiday-mar
Copy link
Contributor Author

I noticed that sometimes when I put my cursor on a line with a breakpoint, it does not read the word Breakpoint. Is the alert only supposed to sound at specific moments? Ie, for example the first time the cursor is placed on an active line with a breakpoint?

Screen.Recording.2024-01-23.at.11.37.07.mov

@meganrogge meganrogge added info-needed Issue requires more information from poster and removed info-needed Issue requires more information from poster labels Jan 23, 2024
@meganrogge
Copy link
Contributor

@aiday-mar, alerts interrupt whatever else might be read by design.

And yes, it looks like in your case, you're using mouse clicks vs arrow keys to navigate between the lines. We listen to arrow keys, thus it's expected that you wouldn't hear the cues.

@meganrogge
Copy link
Contributor

Additionally, I have checked with our power SR users and the alerts are working as expected in the editor.

@meganrogge
Copy link
Contributor

I am going to open an issue to get more feedback on this.

@aiday-mar
Copy link
Contributor Author

Hi @meganrogge, thank you for the clarification, that makes sense.

@meganrogge meganrogge reopened this Jan 24, 2024
@meganrogge
Copy link
Contributor

We are going to use status instead here because editor content is the priority.

@meganrogge meganrogge added bug Issue identified by VS Code Team member as probable bug accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues labels Jan 24, 2024
@meganrogge meganrogge added this to the December / January 2024 milestone Jan 24, 2024
@vscodenpa vscodenpa added unreleased Patch has not yet been released in VS Code Insiders insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Jan 24, 2024
@aiday-mar aiday-mar added the verified Verification succeeded label Jan 25, 2024
@aiday-mar aiday-mar added this to the December / January 2024 milestone Feb 6, 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 bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants