Terminal accessibility buffer does not read output upon enter

[meganrogge]

Terminal live output is not announced.
As far as I tested on Windows with JAWS and NVDA, terminal aria-live event is not auto-announced. I typed "echo hello" in terminal, but there was no read-aloud feedback.

#171914 (comment)

[meganrogge]

@jooyoungseo, since the buffer will now be readonly, I think this can be closed. Voice over and NVDA are announcing as I type

[jooyoungseo]

@meganrogge Aw, I think there was a miscommunication between us. The issue that I highlight here is not the input announcement. I am talking about the auto output announcement. For example, if you open an external terminal on Mac or cmd.exe or powershell.exe on Windows outside VSCode, executing any command, such as echo hello will make your screen reader read aloud the output as soon as you hit return key. The VSCode terminal was behaving like this before the a11y terminal buffer. What you have seen is that screen-reader users want this real-time output announcement per command execution just like before. This no longer works as far as I tested with NVDA and JAWS on Windows.

[meganrogge]

Thanks for clarifying. I was confused by:

I typed "echo hello" in terminal, but there was no read-aloud feedback.

Now I understand

[meganrogge]

I can repro this not working in the latest stable VS Code as well. I type echo hello and it does not read hello

[jooyoungseo]

@meganrogge -- Aw, that's my bad! Sorry for confusing you. I assume that aria-live = "assertive" attribute got broken somewhere for the terminal a11y buffer.

[meganrogge]

@jooyoungseo I have just spent the last 2 hours looking into the output not being read issue and am stumped 🤔 . since I can repro in Stable, I don't think this is a regression. We're doing the right thing here and debugging showed the element's text content is updated to be the output on enter, but the browser /screen reader is not reading it

https://github.com/meganrogge/xterm.js/blob/01b0eb615c0491135c350a28553ff947a266f0fa/src/browser/AccessibilityManager.ts#L83-L86

[jooyoungseo]

@meganrogge -- I would try the following:

1. See if aria-live works when terminal buffer container is marked with div instead of textarea (also need to remove role = "textbox" for this testing).

2. If 1. works, just add textbox role and see if it works.

[meganrogge]

@jooyoungseo thanks for the suggestion. still does not work with that. I'm going to try to find the last commit where this was working - which will be at least a month ago

[meganrogge]

in version 1.72 of VS Code stable, it similarly does not work for short output, but does read the message "too much output to announce for the command ls -la for example.

[meganrogge]

also just tried reverting all of my changes (adding the accessibility buffer) and that does not fix it

[meganrogge]

navigation mode also works in 1.72

[meganrogge]

the .xterm-accessibility element doesn't exist in insider's with screen reader mode on while it does exist in version 1.72