Change:
When a screen reader user creates or focuses a terminal, they hear the that we set which includes keybindings for how to navigate in the terminal etc. Since creating terminals is a pretty frequent occurrence, I imagine that they will have heard this info repeatedly within their first few uses of VS Code. Should we have a way for screen reader users to disable meta info to reduce the noise they must filter through to hear relevant/important info? Should we just remove the extra info after creating X terminals? The editor should follow suit here - ATM, the same info is presented repeatedly. would love to hear your thoughts and feedback - would this be of interest to screen reader users?
cool idea. I think I was debating something similar - that the aria label of the editor should not be read all the time. But so far no user has complained about this. So I never pursued this more. Overall I think this makes sense, but in practice this might be useful, and when not users just press to stop the announcment.
thoughts?
Let's include this as a question in our survey
I am on the fence because some novice users might find the instructions provided by aria-label helpful whereas some experienced uses would find it redundant. That's why some popular screen reader, such as JAWS, have verbosity setting where users can customize the control instruction details following their needs. However, aria-label cannot easily be filtered through screen reader itself. Maybe, VSCode team can implement an a11y verbosity setting to toggle the aria-label attachment.
It would be great, at least in my opinion, to have a way to inhibit this information after some time of use. Perhaps an option in accessibility settings. The help text read when the terminal receives focus, could also contain instructions on how to silence it.
suggested we could possibly pull the setting from the OS and use that within VS Code instead of adding one
suggested that it would be great if audio cues could be played in place of reading "left bracket", "period" and other punctuation
To be clear, replacing punctuations with earcons are possible with screen readers. is a good example. However, there are some color coding and semantics in VSCode to indicate their symbol groups, such as function, class, variable, etc. which are all ignored in screen reader. It would be so nice if there would be a way to provide such information to screen reader. Voice-fonts (using different speech syntehsizer for different semantic symbols) would be nice, but we may need to work closely with each screen reader vendors to achieve this. Currently, it is possible to force screen readers to switch between different syntehsizer engine by using lang attribute: Some synthesizers support this, such as . is one of the most accessible editors that uses both voice-fonts and earcons.
With the initial small set that we allow configuring in , we should find other components that would benefit from: setting like this with helpful information and then a setting like this
Verify that when focusing a diff editor with the setting enabled, you hear a hint about . With that disabled, you do not. Verify that when focusing a terminal with the setting enabled, you hear a hint about about and with it disabled, you do not.
/closedWith
! Seems to work for terminal, but not diff.
are you sure you had saved the setting? it's working for me https://user-
Yes I'm sure the setting is saved. I created a diff by right clicking a file in the explorer and selecting "select for compare" and then selecting a different one and doing "compare with selected"
At the beginning of the tests I had the feeling that it was not working correctly, but after repeating the tests a few times I came to the conclusion that everything was right. Would it be possible to clarify the meaning of the message 'undefined use Shift + F7 to navigate changes'? More specifically why the word undefined in the message?
Yes making a new issue for that and should be easy to fix. Thanks for testing

Discussion:
renderOverviewRuler: true, diffWordWrap: 'inherit', diffAlgorithm: 'advanced', <del> accessibilityVerbose: true </del> <ins> accessibilityVerbose: false </ins> }); if (typeof options.isInEmbeddedEditor !== 'undefined') {

renderOverviewRuler: (a.renderOverviewRuler !== b.renderOverviewRuler), diffWordWrap: (a.diffWordWrap !== b.diffWordWrap), diffAlgorithm: (a.diffAlgorithm !== b.diffAlgorithm), <ins> accessibilityVerbose: (a.accessibilityVerbose !== b.accessibilityVerbose), </ins> }; }

dimension: { height: this.cell.layoutInfo.metadataHeight, width: this.cell.getComputedCellContainerWidth(this.notebookEditor.getLayoutInfo(), true, true) <del> }, accessibilityVerbose: this.configurationService.getValue<boolean>('accessibility.verbosity.diff-editor') ?? false </del> <ins> } </ins> }, { originalEditor: getOptimizedNestedCodeEditorWidgetOptions(), modifiedEditor: getOptimizedNestedCodeEditorWidgetOptions()

dimension: { height: Math.min(OUTPUT_EDITOR_HEIGHT_MAGIC, this.cell.layoutInfo.rawOutputHeight || lineHeight * lineCount), width: this.cell.getComputedCellContainerWidth(this.notebookEditor.getLayoutInfo(), false, true) <del> } </del> <ins> }, accessibilityVerbose: this.configurationService.getValue<boolean>('accessibility.verbosity.diff-editor') ?? false </ins> }, { originalEditor: getOptimizedNestedCodeEditorWidgetOptions(), modifiedEditor: getOptimizedNestedCodeEditorWidgetOptions()