Bug 41074 - The tab order followed when the user hits the tab key on the keyboard follows no clear pattern
Summary: The tab order followed when the user hits the tab key on the keyboard follows...
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows ()
Version: 2.2.0
Hardware: PC Windows
: Normal enhancement
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-05-13 13:49 UTC by John Hardman
Modified: 2017-11-23 09:18 UTC (History)
4 users (show)

Tags: Keyboard tab order accessibility xamarin.forms ac uwp
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 41074 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description John Hardman 2016-05-13 13:49:16 UTC
When using the keyboard to navigate around interactive controls on Windows (both WinRT 8.1 and UWP), the order that the controls are focused in (the tab order in Windows parlance) does not seem to follow any particular pattern.

It is not the order that controls appear in the UI hierarchy following either a depth first or breadth first traversal.
It is not the order that controls are created.
It is not left->right, top->down
It is not top->down, left->right

The result is that developers using Xamarin Forms, without creating custom layouts etc, have no predictability over what tab order will be followed at run time. This means that implementing accessibility is an issue.

Either an int property needs to be added to all interactive controls, that can be used to identify the order to use, or some predictability about the traversal order based on the UI hierarchy needs to be implemented.