microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
163.63k stars 29.04k forks source link

A11y_VisualStudioCodeClient_Debugging_StatusMessage:Screen Reader is not announcing about the current status of action in the code editor window #141873

Closed kupatkar99 closed 2 years ago

kupatkar99 commented 2 years ago

GitHubTags:

A11yMAS; #A11yTCS; #A11ySev2; #DesktopApp; #Visual Studio Code Client; #BM-VisualStudioCode-Win32-Nov2021; #Win32; #StatusMessages; #WCAG2.1; #AINotInScope; #FTP; #STP;

Environment Details:

Application Name: Visual Studio Code Client Windows Version: Windows 11

Repro Steps:

1.Open Visual studio code editor. 2.Using "Ctrl+Shift+D" key navigate to the debug side view bar option. 3.Open the launch.json file under the "Configure or Fix: launch.json"button and select "Node.js" from the drop down list

  1. Add configurations to "launch.json" utilizing IntelliSense with CTRL+SPACE
  2. Parse launch.json with keyboard and observe if ATs will provide stock debugging information under "configurations" properties. 6.Start debugging by pressing F5.
  3. Set a breakpoint and pause exceution at the breakpoint by issueing an request/command to your Node process that triggers the line you got the breakpoint 8.Toggle/add/remove breakpoints 9.Verify whether screen reader is announcing the current status of action in the code editor window or not.

Actual Result:

No Confirmation of action is heard when made changes in the code editor window.

Expected Result:

There should be a confirmation of action informing user of the current state.

User Impact:

Screen reader users will be confused if screen reader does not announce the current action/edition in the code. A11y_VisualStudioCodeClient_Debugging_StatusMessage

isidorn commented 2 years ago

The description and the gif do not seem aligned.

Your description says that adding a breakpoint should notify the user that the breakpoint got added. But this is against vscode design - we do not announce confirmation after an action has been successfully performed. The same issue can be applied to all the other hundreds of actions. We have recieved no user feedback that we should confirm action completion. Thus closing this as designed.

Please let me know if I misunderstood the issue. Thanks