You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While integrating AccessKit with my own GUI lib, using the egui integration as reference, I noticed that narrator (the screen reader I am using for testing) is not working correctly with a textbox (TextField role with InlineTextBox child). The characters are not read when shifting the cursor with the arrow keys or when selecting the text. To make sure this wasn't a problem on my end I ran the egui example and found the same problem.
I don't know if this problem is specific to Windows 11 but I can check on a Windows 10 machine tomorrow.
The text was updated successfully, but these errors were encountered:
This coincides with my own experience trying to implement ITextRangeProvider. I'm curious how things work for you on Windows 10.
@geom3trik does Narrator say anything at all? Does it read the label of the text field correctly?
Managed to test it on Windows 10 and it works as expected with the egui hello_world example, so it seems like this might be an issue only on Windows 11 or the W11 version of narrator.
In answer to your question, it reads the text content as if it was a label but will not read out any changes to the text or while navigating through it with the arrow keys. It also does not highlight the individual characters like it does in Windows 10.
While integrating AccessKit with my own GUI lib, using the egui integration as reference, I noticed that narrator (the screen reader I am using for testing) is not working correctly with a textbox (TextField role with InlineTextBox child). The characters are not read when shifting the cursor with the arrow keys or when selecting the text. To make sure this wasn't a problem on my end I ran the egui example and found the same problem.
I don't know if this problem is specific to Windows 11 but I can check on a Windows 10 machine tomorrow.
The text was updated successfully, but these errors were encountered: