https://github.com/xamarin/xamarin-forms-samples/tree/master/UserInterface/Accessibility
It seems the TabIndex is not working anymore, even in the sample provided by Microsoft regarding to Keyboard Accessibility it only focuses the first button, it works properly for entry or stepper tough.
The focus should move to the next button
The focus is stuck on the first button

@samhouts Id like to add some extra to this bug, in the same accessibility app we have two different pages, "Automation Properties" and "Tab Order". The bug was originally reported for TabIndex not working on the sample app. Testing the accessibility app in XF 4.3 I was not having any issues navigating on the Tab Order sample but I have encountered an interesting bug in the accessibility demo portion of the app, and its very similar to the one described here. When trying to navigate using a screen reader I have found that I cannot navigate past the "Enter your name:" label when its wrapped in a stack layout. However when I removed the stack layout i could freely navigate past this control. Ive found that wrapping other controls in stack layouts either perform identical or similar issues in regards to how the screen reader behaves with the ui elements.
However I have found that wrapping multiple elements in stack layouts at once also produces different results.
Not entirely sure if this warrants another bug or similar enough to this one. I can easily create another bug if need be.
@rnic99 Yeah, I would open a new bug for that. Thanks!!!
@davantigroup It looks like TabIndex behaves the same on iOS no matter what version I'm using. Are you really seeing this issue on iOS, too? Thanks!
@samhouts We had the same issue on iOS too, we can test it again if needed
Please do! If you can post a gif or video, too, that would be immensely helpful! Thanks!!
@davantigroup Also, if you could test with the package attached to https://github.com/xamarin/Xamarin.Forms/pull/9702#issuecomment-593727682 and let me know if it improves or worsens the situation, that would be great. Thanks!
@samhouts It doesn't work also in UWP app
Any updates? I think Accessibility should be prio high.
What thinks @magoolation about this?
Most helpful comment
Any updates? I think Accessibility should be prio high.
What thinks @magoolation about this?