Well, it seems that with VoiceOver on *all the time* during testing with Accessibility Inspector and UI Browser, AXFocused is set to YES properly on text fields, and AXSelectedTextChanged is fired when moving cursor. So what I wrote probably does not apply. Sorry for the noise.
On Nov 30, 2015, at 11:34 PM, Boris Dusek < email@hidden> wrote:
Hi Nektarios,
I tried with Chrome and noticed that text fields with text focus (i.e. cursor blinking in them, pressing keys typing into them) still return AXFocused = NO. That is definitely wrong, text fields with keyboard focus should return AXFocused = YES. This could confuse VoiceOver / accessibility infrastructure as to whether to announce changes on the element etc.. (Note that I was also not able to get UI Browser to report AXSelectedTextChanged on a field in Chrome whereas in Safari I was on the very same text field on the very same webpage).
Tried with Chrome 46.0.2490.86 (64-bit) on OS X 10.11.1.
Not sure what would cause the change in OS X 10.11, based on the above, maybe VoiceOver stopped announcing changes on elements on which it has VO cursor when the element’s AXFocused = NO?
Hope this helps,
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|