Open kelly987654 opened 5 years ago
Hi @kelly987654,
This appears to be an issue either with the Xamarin app platform or some issue within accessibility, as you stated that Inspect is reporting the same behavior.
We'll try repro'ing this on our end and getting the right folks from either Xamarin or Accessibility involved.
Thank you!
Hi @kelly987654,
I'm unable to reproduce the issue with the standard controls. Can you share the control that's exhibiting this behavior? It might be an issue with the control itself with how it disables items.
Thanks
Thanks for looking into this. I can't share the control unfortunately, but we are going to attempt to create a new sample solution to reproduce the issue.
The strange thing is that its not the control that we're tapping that falls off the accessibility tree, but a different control on the page. Also everything is still visible to the user and can be interacted with, so I don't think its an issue with us setting IsVisible or IsEnabled to false somewhere. Is it possible to set a GUI element to visible to the user but not the accessibility server in Xamarin Forms?
Is it possible to set a GUI element to visible to the user but not the accessibility server in Xamarin Forms?
Yes - it is possible to declare your own accessibility attributes, for example if you want to create a GUI element from scratch.
Environment Info Application under test: Xamarin Forms v3.4.0.1008975 UWP app WinAppDriver: v1.1.180918001 Device: Tablet running Windows 10 v1803
Steps to reproduce
If the above steps are repeated but step 4 is replaced with either a manual tap or a tap by coordinate (using the JWP touch/down, touch/up commands), no issues are observed, and button 'A' remains in the accessibility tree.