Change:
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== <del> xterm@5.2.0-beta.17: version "5.2.0-beta.17" resolved "https://registry.yarnpkg.com/xterm/-/xterm-5.2.0-beta.17.tgz#034bf7cac9aff2adc0f2958e09a62203ace7c48e" integrity sha512-pLkLhWh1XPkZnSNyxY1A/2WOzMRq0axJO69vCV+gu6/do3W/EeMtyPqwZSmIHF9s37t3CQlN8RsMHUpdR61VCQ== </del> <ins> xterm@5.2.0-beta.19: version "5.2.0-beta.19" resolved "https://registry.yarnpkg.com/xterm/-/xterm-5.2.0-beta.19.tgz#b3fd2eda3d9aa2672abaf03e864fafe64269c8a0" integrity sha512-3U+NYHjnIdUQf+MXiitmoFAcBOaLFHid3R/LzzvELjMwQx227EFk+3OmQjkBt7eH/IR+A4VlP5aPGmgriyLtGQ== </ins>

Discussion:
Terminal a11y buffer is not read-only. Since this is contenteditable textbox, unintended delete key can mess up the output content. I confirmed that delete key works inside the buffer. It would be even nicer if this buffer could be marked up with readonly to prevent users from accidentally deleting their output content.
did you notice that when you toggle the mode it comes back as the original? so while it seems like editing of the buffer is possible, it's not actually making any changes.
-- You are correct. If you press tab and come back to the buffer via Shift+Tab, it comes back to the original content. However, the content is editable when it gets focused.
Not sure if it's possible to change this, but will investigate
Looks like this is easy to do - just disabling and setting
-- To give you prompt testing results, I have just built the latest main branch on my end (this issue will also be found tomorrow once insider is released). I have found the following inadvertent regression (tested with NVDA and JAWS on Windows): a11y buffer is not readable via standard arrow keys. input -terminal a11y buffer: only requires one Shift+Tab. However, from terminal a11y back to terminal input requires two tab key press. Note that aria-live is now working!
I have already caught that regression, you can build based on this PR to see that I've fixed it
i'll investigate: when I investigate
As of today's insider build (Commit: ), it appears that the accessibility buffer can still be modified accidentally. Additionally, if the buffer has been altered, tabbing to the shell and then shift-tabbing back does not restore the buffer to its previous state, as it did in previous versions. Furthermore, if the buffer has been modified, subsequent command output will not be reflected in the buffer.
see for why we didn't go with readonly. the actual buffer is never modified - the text area element is. focusing the terminal buffer via mouse click for example and shift+tabbing again will restore the contents to what they were before.
Is there a way to reset the state of the buffer without using the mouse? As of the version on the main branch, I am unable to reset the buffer by tabbing and shift-tabbing back to it.

Just hitting tab works for me
Can you get the buffer to reset after tabbing into it after modifying the buffer? I cannot get the buffer to reset with the NVDA on Windows 11; not sure weather there is something wrong on my ends.
-- I can reproduce your issue. Please file a separate issue and provide minimal reproducible steps so that can fully replicate this issue.
I have created the issue at .