add accessibility

docs/editor/accessibility.md

@@ -160,7 +160,7 @@ Certain features such as folding and minimap (code overview) are disabled when i
 
 Terminal accessibility help can be accessed via `kb(workbench.action.terminal.showAccessibilityHelp)` which describes some useful tips when using a screen reader. One of the tips described is to use `kb(workbench.action.terminal.focusAccessibleBuffer)` to access the terminal's buffer, this will enter the screen reader's browse mode automatically (depending on your screen reader) and provide an accessible view of the entire terminal's buffer.
 
-The legacy "navigation mode" allows navigating through terminal rows, press `kbstyle(F1)` to open the Command Palette and search for "terminal navigation mode" to find these commands. This mode will be removed soon in favor of the new accessibility mode.
+A useful accessibility setting, `terminal.integrated.tabFocusMode`, controls whether the terminal receives the tab key in favor of the workbench similar to the `editor.tabFocusMode` counterpart for the editor.
 
 ### Shell integration
 
@@ -174,7 +174,7 @@ Note that the `terminal.integrated.minimumContrastRatio` will not apply to `powe
 
 ## Status Bar accessibility
 
-Once a focus is in the Status bar via **Focus Next Part** (`kb(workbench.action.focusNextPart)`) arrow navigation can be used to move focus between Status bar entries.
+Once focus is in the Status bar via **Focus Next Part** (`kb(workbench.action.focusNextPart)`) arrow navigation can be used to move focus between Status bar entries.
 
 ### Diff editor accessibility
 

release-notes/v1_76.md

@@ -24,6 +24,35 @@ We really appreciate people trying our new features as soon as they are ready, s
 
 ## Accessibility
 
+### Context specific tab focus mode
+
+The `Toggle Tab Key Moves Focus` command is useful for determining whether the workbench or editor/terminal receive tab key input.
+
+We have added `editor.tabFocusMode` and `terminal.integrated.tabFocusMode` settings to allow users to control this by default.
+
+### Improved error audio cue responsiveness
+
+We now play `audioCues.lineHasError` during character navigation so that screen reader users have improved insight into where the errors are in the editor.
+
+### Terminal accessible buffer improvements
+
+Last iteration, we introduced the terminal accessible buffer, which provides screen reader users access to the terminal contents via `kb(workbench.action.terminal.focusAccessibleBuffer)`
+
+This iteration, we've improved the accessible buffer by adding selection & link support, making it readonly, and leveraging shell integration insights to provide only the important terminal content - the command that was run, the exit code if any, and the output. We plan to allow configuring this next iteration.
+
+### Terminal command failure audio cue
+
+When a command exits with a non-zero code in a terminal with shell integration, sighted users can glance at the command decoration to quickly understand this. To convey this information to screen reader users, we now play `audioCues.terminalCommandFailed`.
+
+### Screen reader shell integration support on Windows
+
+Shell integration was previously disabled when a screen reader was detected on Windows due to problems with Powershell support in this context. We have determined that this is no longer an issue in most cases, so have enabled it.
+
+
+### Terminal accessible help additions
+
+Discussions with the screen reader community have yielded additions to the terminal accessible help menu.
+
 ## Profiles
 
 ## Workbench