I just filed this issue against VS Code where I suggest to use targeted role="document" in those places that produce HTML output for consumption, to make NVDA switch in and out of browse mode in a smart, automated, manner, reducing the number of times one has to use NVDA+Space to toggle modes. Examples I found while using the 1.44 VS Code Insider builds were:
- The Welcome page
- The details page for an extension
- The ReadMe file that may be displayed after an extension has been installed.
@LeonarddeR suggested that, once this lands in stable, a modification might be needed for the VS Code app module. So filing this issue here.
I just filed this issue against VS Code where I suggest to use targeted role="document" in those places that produce HTML output for consumption, to make NVDA switch in and out of browse mode in a smart, automated, manner, reducing the number of times one has to use NVDA+Space to toggle modes. Examples I found while using the 1.44 VS Code Insider builds were:
@LeonarddeR suggested that, once this lands in stable, a modification might be needed for the VS Code app module. So filing this issue here.