microsoft / microsoft/monaco-editor
[Bug] Screen Readers do not announce error description in the "View Problems" widget
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 46.8k
- Forks
- 4.1k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 1
Description
Reproducible in vscode.dev or in VS Code Desktop?
- Not reproducible in vscode.dev or VS Code Desktop
Reproducible in the monaco editor playground?
- Not reproducible in the monaco editor playground
Monaco Editor Playground Link
Monaco Editor Playground Code
Existing code in the Model Markers Example
Reproduction Steps
- Go over to the Monaco Playground example
- In the "preview" editor on the right-hand side, hover over the string with the error (with red squiggly lines), and in the error tooltip click on "View Problems" - this will open the "View Problems" widget with a description of the error.
- Now start the Narrator app in windows
- Select the view problems widget and wait for Narrator to capture the contents and read them back
Actual (Problematic) Behavior
Observe that Narrator reads out a few details (like the snippet of code, the line:column) but never reads the description in the View Problems widget.
The highlighted section (in the red rectangle) is not read out by narrator.
Expected Behavior
Narrator has to read out the error description shown in the view problems widget
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Monaco Editor Playground Model Markers Example linked in the issue and reproduce the problem in the View Problems widget using Narrator. Trace how the widget exposes the error details to screen readers; done means Narrator reads the error description as well as the code snippet and line:column information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- accessibility
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100