Change:
resolved "https://registry.yarnpkg.com/xterm-addon-unicode11/-/xterm-addon-unicode11-0.5.0.tgz#41c0d96acc1e3bb6c6596eee64e163b6bca74be7" integrity sha512-Jm4/g4QiTxiKiTbYICQgC791ubhIZyoIwxAIgOW8z8HWFNY+lwk+dwaKEaEeGBfM48Vk8fklsUW9u/PlenYEBg== <del> xterm-addon-webgl@0.15.0-beta.4: version "0.15.0-beta.4" resolved "https://registry.yarnpkg.com/xterm-addon-webgl/-/xterm-addon-webgl-0.15.0-beta.4.tgz#d03a98e446372a5dbb7d92075d1f125eec23b030" integrity sha512-W9N0+5i3trQhgBOHDsnNiBbBiJpleFenY668wWaZ9GlvWseCTnjnWis1kfnM9WASDh/0+7aOjWrD089o+QeHGQ== xterm-headless@5.2.0-beta.21: version "5.2.0-beta.21" resolved "https://registry.yarnpkg.com/xterm-headless/-/xterm-headless-5.2.0-beta.21.tgz#e58ecb5a0899c2af3b0b53e147cb56fb02e35a93" integrity sha512-GpJbHoXBxIOMoomBaLCpo1vs15YYMdJGz3gpUrVhHuJSnqANmrgOHbJCe16p1cQ/oGAdr2C/ePvu+XGXzmNBAA== xterm@5.2.0-beta.21: version "5.2.0-beta.21" resolved "https://registry.yarnpkg.com/xterm/-/xterm-5.2.0-beta.21.tgz#13462f37e7030897f5aacb3f27f524db530273dd" integrity sha512-7KsDc+goSKIuV1s9mhU/o3iXN0f/PHfB0/11zsN2jADlGZGAO9Xe58pZXd35P8AgLsl4w7HctrMXW6t25l3ExQ== </del> <ins> xterm-addon-webgl@0.15.0-beta.5: version "0.15.0-beta.5" resolved "https://registry.yarnpkg.com/xterm-addon-webgl/-/xterm-addon-webgl-0.15.0-beta.5.tgz#2c174d03bb200af5d40ba63f01fcae05fd259ba1" integrity sha512-6OSwdjgSeJzME37gdg6LTKt7VfYIZG1T5cFe9g4uCXEsefyPCReRWhjLgBbTrYpBAVJ4UdHsnZoR1PU90+uaRQ== xterm-headless@5.2.0-beta.22: version "5.2.0-beta.22" resolved "https://registry.yarnpkg.com/xterm-headless/-/xterm-headless-5.2.0-beta.22.tgz#ed12b8f91a631539bf7dd9abef57ba1821bcdb26" integrity sha512-o9zb5yqsFDax2rUa7BtlHFiURJARJ4tOmYtDG/DUXllvinFP6ylva0o35AfDuqw9A1TUYfbdckZdlarOV6ZsAg== xterm@5.2.0-beta.22: version "5.2.0-beta.22" resolved "https://registry.yarnpkg.com/xterm/-/xterm-5.2.0-beta.22.tgz#2002bc1c4f1931c7ade676d5940e2c120ee9eb20" integrity sha512-/MjF1GSwgowVXT7SsvjjZs5fKuz0oN8gvd7Pga4aYSq2ViXDhvkyhZYa7Suj03oFUosNh2VqaAImzxE80eatlQ== </ins> y18n@^3.2.1: version "3.2.2"

Discussion:
Type: <bBug</bAfter mutating the accessibility buffer for the integrated terminal in the latest iteration of VS Code, the state of the buffer does not restore after tabbing away and refocusing the terminal accessibility buffer using the keyboard. This makes it so that screen reader users cannot get the correct information after inadvertently modifying the buffer. Additionally, if the buffer is in an incorrect state, newly coming output from the terminal will not be reflected in the buffer, making that particular terminal session unusable for screen reader users. Steps to Reproduce: VS Code in the screen reader optimized mode a new integrated terminal a command that outputs text to the terminal, such as -tab to the accessibility buffer and observe that the information is presented correctly the buffer by typing arbitrary characters (or in the extreme case, press ctrl+a and delete the entire buffer) back to the shell and shift-tab to the buffer again, observe that the buffer remains in the incorrect state back to the shell and type in the command that outputs to the terminal again -tab back to the buffer, observe that the buffer remains in the incorrect state and the newly output information does not appear in the buffer. Actual result: The buffer do not return to its correct state after edit. Expected result: After the buffer has been modified, refocusing the buffer via keyboard should return it to its correct state. Note: This used to work during the early iteration of the accessibility buffer. Tested using NVDA 2022.4 on Windows 11 Pro and the latest commit on the main branch at the time of this report (commit: ) VS Code version: Code - OSS Dev 1.75.0 (Commit unknown, Date unknown) OS version: WindowsNT x64 10.0. Modes: Sandboxed: No <details<summarySystem Info</summary </details<!-- generated by issue reporter --
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.74.3. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
The problem still occurs as of the latest version of VS code.