While it is appropriate to treat large parts of VS Code as an application for screen readers, there are areas where it makes sense to suggest to screen readers to use their browse mode (AKA virtual cursor) mode navigation paradigm instead. Places I've found this to be the case are, among possibly more:
- The Welcome page.
- Details for an extension.
- After an extension has been installed, the ReadMe HTML output.
All of these are places where structured HTML output is generated for pure consumption and possibly following links or initiating things like installing or uninstalling an extension, etc., but not more complex interactions.
I found this while trying out Code for the first time for real, using current 1.44 Insider builds.
While it is appropriate to treat large parts of VS Code as an application for screen readers, there are areas where it makes sense to suggest to screen readers to use their browse mode (AKA virtual cursor) mode navigation paradigm instead. Places I've found this to be the case are, among possibly more:
All of these are places where structured HTML output is generated for pure consumption and possibly following links or initiating things like installing or uninstalling an extension, etc., but not more complex interactions.
I found this while trying out Code for the first time for real, using current 1.44 Insider builds.