Keyboard and visual users are unaware of the shortcut key to navigate in 'Text view'.
Reproducible in vscode.dev or in VS Code Desktop?
- [X] 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 (microsoft.github.io)
Monaco Editor Playground Code
const value = /* set from `myEditor.getModel()`: */ `test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test test `;
// Hover on each property to see its docs!
const myEditor = monaco.editor.create(document.getElementById("container"), {
value,
language: "javascript",
automaticLayout: true,
readOnly: true,
wordWrap: "on",
});
Reproduction Steps
- Open the URL- Monaco Editor (microsoft.github.io)
- Monaco Editor page will appear navigate inside 'Preview' Section.
- Navigate to source code and observe the issue whether there is any information provided to access the tooltip or not.
Actual (Problematic) Behavior
Keyboard and visual users are unaware of the shortcut key to navigate in 'Text view'. Here when the screen reader focus on source code the screen reader announces the short cuts keys information, but the information of the tooltip short cut is not visually displayed on the screen. Here screen reader is announcing as "Editor content; Press Alt+F1 for Accessibility Options. edit has auto complete multi line".
Attachment:
https://github.com/microsoft/monaco-editor/assets/93735775/91f12eb2-a398-4da1-b68c-780887a5bceb
Expected Behavior
The information of the tooltip short cut should be visually displayed on the screen. |
Additional Context
No response
Hi @hediet, is any update on this issue? could you please provide the ETA to fix this issue?
Hi @rzhao271, is any update on this issue? could you please provide the ETA to fix this issue?
Hi @meganrogge, is any update on this issue? could you please provide the ETA to fix this issue?
Hi, this was fixed a long time ago. Check the latest build.