VS Code accessibility community where users can share feedback, issues, and accessibility practices.
Inlay hints add additional inline information to source code to help you understand what the code does. This can help you understand the meaning of each argument at a glance, which is especially helpful for functions that take Boolean flags or have parameters that are easy to mix up.
For example this.tokens.forEach(t => t.cancel()); with inlay hints would become this.tokens.forEach(callbackfn: t : CancellationTokenSource => t.cancel());
So visually we add grayed out hints in the line. These hints are not accessible so we were thinking how to make them accessible, and for now we went with the command
"Read Line With Inlay Hints" that would move focus to the HTML elements that has this additional richness. This is still in early development so we are very much looking for feedback.
Have in mind that inlay hints are currently only supported by TypeScript and JavaScript. Java and Python will probably come in the future. To turn on this setting you can add the following settings:
"editor.inlayHints.enabled": true,
"typescript.inlayHints.enumMemberValues.enabled": true,
"typescript.inlayHints.parameterNames.enabled": "all",
"typescript.inlayHints.parameterTypes.enabled": true,
"typescript.inlayHints.functionLikeReturnTypes.enabled": trueFor javascript just search for the javascript inlayHints settings.
So if you are using js/ts try it out and let us know what you think.
- On mac try cmd+shift+e to move focus into explorer and then cmd+down to move focus back into the editor. Let me know if it works
- I am not a Python expert, I suggest that for the Anaconda issue you simply open a new issue in the Python repo and ping me @isidorn on the issue https://github.com/microsoft/vscode-python
And ping me on it and we can work with the Jupyter team.
VS Code supports multiple cursors. More about this feature can be found here https://code.visualstudio.com/docs/editor/codebasics#_multiple-selections-multicursor
The idea behind multiple cursors is what you type at one cursor the other cursors will replicate. So it makes refactorings faster.
When you have multiple cursors there is still a “primary” cursor and screen reader will read what is on the line of the primary cursor.
Because of this we have introduced “Focus Next Cursor” and “Focus Previous Cursor” commands. So you can change what is the active cursor, so that you can choose based on which cursor line does the screen reader read.
You can try it out in latest VS Code Insiders and let us know what you think about this feature.
Hello,
I am fairly new to coding, and was hoping for some advice from this community. I can't figure out how to read my output when I use VS code Jupyter Notebooks extension to run my code. Control+shift+U brings me to the pannel that says tasks - output editor and jaws asks me to use arrow keys to read the text. But there's nothing there even though I'm pretty sure there should be (tested it using Jupyter Notebook application).
Thanks for the advice in advance!
In the meantime, the output is unrelated to the notebooks, it has output from different channels. For the Notebook output you should be able to just navigate to it using Tab / Up / Down
I hope this doc can help as well https://code.visualstudio.com/docs/datascience/jupyter-notebooks
Try it out and let me know how it goes.
4 replies
let age=42;, it should say age, variable, number or something like that, basically type inference as offered by the extensions already. This feature could be very useful for other things as well, dk the full extent of what mouseover can do because obviously I can't perform it.
2 replies
1 reply
5 replies