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
Upgrading from 4.4.2 to 5.0.0 results in the picker no longer being accessible to TalkBack or Appium. This prevents native tests from being able to exercise this component and vision impared users being able to interact with it.
I'm currently looking through the diff between 4.4.2 and 5.0.0 to see if I can work out what's changed to stop these elements from being exposed, but figured I'd report this while I investigate.
Testing the library on a physical Android device, it looks like there has been some accessibility regressions which are probably related. I'm able to focus the currently selected values, but cannot edit them, while on 4.4.2 I can select both the before and after element in each wheel, then click to select that value.
Manually updating these to info.setVisibleToUser(true) fixes the issue, though I imagine we'd probably want to restore the original isVisibleToUser() behaviour.
levibuzolic
changed the title
[5.0.0] Android picker no longer accessible via Appium
[5.0.0] Android picker no longer accessible via TalkBack or Appium
Apr 4, 2024
Upgrading from 4.4.2 to 5.0.0 results in the picker no longer being accessible to TalkBack or Appium. This prevents native tests from being able to exercise this component and vision impared users being able to interact with it.
I'm currently looking through the diff between 4.4.2 and 5.0.0 to see if I can work out what's changed to stop these elements from being exposed, but figured I'd report this while I investigate.
With the following code:
4.4.2
On version 4.4.2 while using
androidVariant="nativeAndroid"
the following accessibility tree is produced:5.0.0
In the above you can see that
pickerWrapper
is the final element exposed with none of theandroid.widget.NumberPicker
made available.System:
The text was updated successfully, but these errors were encountered: