New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 757995 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

OOBE first focus should be on "Let's go"

Project Member Reported by mcirimele@chromium.org, Aug 22 2017

Issue description

Chrome Version: (copy from chrome://version)
OS: (e.g. Win7, OSX 10.9.5, etc...)

What steps will reproduce the problem?
(1) Reset device
(2) Get to the first screen of OOBE

What is the expected result?
Focus is on the primary action, in this case "Let's go".

What happens instead?
Focus is on the language selection in the bottom right corner.

Apologies if this is as intended, I know we had some back and forth around the focus through OOBE. If I recall correctly in the end we decided to default focus to the primary action to help users on a keyboard get through OOBE. 
 
OOBE-focus.jpg
2.8 MB View Download
Status: WontFix (was: Untriaged)
We are talking about keyboard focus. It was decided that keyboard navigation is important for accessibility, that is why we focus on the first control element of the active dialog. 
Can you explain more why we focus on the first control element of the active dialog for keyboard navigation? Most of the users do not need to switch to other languages, and they can go to the left for the additional options. 
We've gone back and forth on this in other bugs. 

In https://bugs.chromium.org/p/chromium/issues/detail?id=696898 we decided to focus on "Let's go!", but in https://bugs.chromium.org/p/chromium/issues/detail?id=707939 we said focus on the first element and maybe look into not having visible focus. 

My reaction is to having the visible focus on the first screen. I think it over-emphasizes a secondary action which decreases the visual clarity of the page. Is there a middle ground here where we can keep the focus on the first UI element but have it be invisible? Or is that not feasible? 

zalcorn@ what do you think?
Regular users will not usually use keyboard for navigation. Keyboard navivation is mostly used for accessible navigation. So "Tab" should reasonably navigate thouth the page. Per https://bugs.chromium.org/p/chromium/issues/detail?id=707939#c6 we focus on the first control element in the dialog.
In the old OOBE, Tab navigation was explicitly set to "OK" -> "Language selection" -> "keybord selection" -> "Network selection". Which did not match the order of UI elements either.

Sign in to add a comment