-
-
Notifications
You must be signed in to change notification settings - Fork 655
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MS teams: NVDA does not announce the deleted character in compose box of personal/group chat. #15274
Comments
I can confirm the issue with latest version of teams. it doesn't occur 100% of the times, but it is quite frequent. It happens more frequently the first time we type something after the field receiving focus. |
I just noticed this issue using 2023.2 beta 3. It also occurs when composing a new public message or reply from within a channel. I also notice that I occasionally hear the expected characters but usually they are not announced. |
Will this be solved by #14888? cc: @michaelDCurran |
Have you by any chance set the NvDA advnaced option to access Chromium documents via UI Automation? This would cause Teams to be accessed by UI Automation also. And when doing this, I do see an error when backspacing:
However, by default NVDA will be using IAccessible2, which for me works fine when backspacing. If you have definitely not forced NVDA to use UI Automation in Teams, you may want to try increasing the Caret movement timeout value in NVDA's advanced settings. If this solves the problem we can consider increasing the timeout for this situation or more broadly. |
I doubt #14888 would solve this, as by default Teams is not accessed
with UI Automation.
|
The advance setting "Use UIA with Microsoft Edge and other Chromium-based browsers when available" was initially set to the option " default (used only when necessary)". I attempted to change the setting to "No," but the issue persisted. However, I noticed a particular problem with this adjustment: it fails to announce the first character of a word. For instance, if you attempt to delete the word "Hello," the initial character "H" will not be announced. Moreover, if someone attempts to delete characters rapidly using the "Backspace" key, the announcement of the deleted characters will not be accurate. |
The initial description of this issue suggests that this is a regression in 2023.2. Could someone experiencing this definitely confirm that removed characters were announced in 2023.1, and they no longer are in 2023.2? In that case this should probably be re-prioritised. |
Testing with NVDA last alpha, caret timeout is at the default value. However in the new Teams app (mini Teams) the characters are reported when using backspace apart from the very first character in the edit field which is the last to be deleted, is still not announced. |
@Adriani90 Since this is reproducible for you, could you test the same scenarios with 2023.1? This will allow us to understand if this is a regression in NVDA or not. |
This particular issue seems to have started in 2023.2.
Note that Teams classic will be discontinued as of end of June 2024 at latest for anyone, so users will be updated to the new Teams automatically. See this source: @jcsteh maybe you have any suggestions on how to solve this regression on a broader basis since you know in more detail how the key hook related behaviors could influence this. It might be useful for other applications as well. |
The only thing i can think is that the timing is different now. NVDA probably doesn't wait quite as long as it did previously. Increasing the caret movement timeout should fix this and maybe this is something that will need to be done in a Teams app module or similar. @gauravahir28, you noted a problem when backspacing the first character of a word in current NVDA versions with the timeout set to 200 ms. Can you reproduce this in 2023.1 with the caret movement timeout set to 100? |
This is not reproducible anymore in MS Teams Version 24335.208.3315.1951 / Clientversion 49/24120100212. Tested with NVDA alpha-34843,2477780d (2025.1.0.34843) Closing as works for me. |
Steps to reproduce:
Actual behavior:
NVDA does not announce the deleted character, but the character gets deleted.
Expected behavior:
NVDA should announce the deleted character.
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
Installed
NVDA version:
NVDA 2023.2-Beta 2
Windows version:
Windows 11.
Name and version of other software in use when reproducing the issue:
Microsoft Teams Version 1.6.00.20074 (64-bit).
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
working well with 2023.1
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Yes
The text was updated successfully, but these errors were encountered: