Bug 59414 - On UWP, the tab sequence seems to include three non-visible or non-actionable controls
Summary: On UWP, the tab sequence seems to include three non-visible or non-actionable...
Status: CONFIRMED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.3.4
Hardware: PC Windows
: Normal enhancement
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-09-12 12:45 UTC by John Hardman
Modified: 2017-09-14 17:49 UTC (History)
3 users (show)

Tags: UWP, focus, tab, accessibility, narrator, ac
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 59414 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:
Status:
CONFIRMED

Description John Hardman 2017-09-12 12:45:20 UTC
On UWP, on a ContentPage, repeatedly hit the Tab key to cycle through the focusable views. Even on the simplest of ContentPages the focus disappears for three tab clicks at some point during the cycle. I don't know whether the focus is on three invisible controls, or attempting to focus the minimise, restore and close buttons on the title bar, but wherever it is, the focus should not go anywhere without there being some visual feedback (or audio if using Narrator) to tell the user where the focus is.

May be related to 39830
Comment 1 Paul DiPietro [MSFT] 2017-09-14 17:49:36 UTC
The current behavior is "intended" in that everything is focusable; if the Narrator is on, it should read whatever it's focusing on, even if that's a ToString of the control (which might sound a bit odd). We'll look into this further though to see if there are enhancements we can make here.