> Unfortunately, moving by character doesn't actually report the character to which you've moved. This probably requires us to fire a notification for the caret move
This might not be due to a missing notification. Unlike on Mac, WebKit on iOS doesn't seem to pass any data other than the fact that the caret moved and on which element. If I use a braille display on iOS, the caret moves as expected. This suggests that VO does realise the caret has moved.
I did try implementing the private _accessibilityCharacterRangeForPosition and _accessibilityValueForRange methods. They do get called, but this doesn't seem to help. :(
Bug 1866793 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> Unfortunately, moving by character doesn't actually report the character to which you've moved. This probably requires us to fire a notification for the caret move
This might not be due to a missing notification. Unlike on Mac, WebKit on iOS doesn't seem to pass any data other than the fact that the caret moved and on which element. If I use a braille display on iOS, the caret moves as expected. This suggests that VO does realise the caret has moved.
I did try implementing the private _accessibilityCharacterRangeForPosition, _accessibilityValueForRange and _accessibilityAttributedValueForRange methods. They do get called, but this doesn't seem to help. :(