Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Issue 157477 OOBE: Select a network control is not labeled for a11y
Starred by 1 user Project Member Reported by, Oct 23 2012 Back to list
Status: Verified
Closed: Oct 2012
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Sign in to add a comment
Version: 24.0.1306.0

1. Open the first OOBE screen
2. Turn on spoken feedback with Ctrl+Alt+Z
3. Tab until the Select a network box is highlighted

It should say "Select a network" along with the value of the control, just like the previous two controls read both the label and the value.

Comment 1 by, Oct 24 2012
Labels: -OOBE Feature-Ash-OOBE
Status: Assigned
Currently when spoken feedback is enabled with CTRL+ALT+Z and user tabs to "Select a network", all it says is "Select", which is the value of the drop down field.

Why is "Select a network" not read by spoken feedback? Spoken feedback reads "Select you language" and "Select your keyboard" correctly. 

Can we look into whether there is some metadata or tag missing from the code for "Select a network?", compared to the other fields where it works correctly?

Comment 2 by, Oct 24 2012
Labels: -Pri-2 Pri-1 Mstone-24
nkostylev: what tricks do you use to debug OOBE pages? Are there some flags that would let me pop up a js debugger on my Chromebook? Or a harness that lets you run the oobe inside a normal Chrome window?

If I could examine the final generated html I could probably identify what needs to be changed really quickly. It's not always obvious from the source.

I built little harnesses when I was last fixing other oobe a11y issues, I probably should have asked earlier if there's a better way.

Dominic, there's a way to debug layout / js code but not whole flow.

What we do:

1. Launch on desktop as
out/Release/chrome --user-data-dir=[...]

Note that no other switches are passed which means Chrome OS is started in a "stub user" session.

2. This will allow to open chrome://oobe page with content inside user session.

3. Now you could use DevTools.
To show specific screen, run this in console (for Welcome screen):


Other screens IDs: eula, update, account-picker, gaia-signin

If you want to show login screen with users ('account-picker'), first run this code before showScreen to setup users:

login.AccountPickerScreen.loadUsers([{'username':'testuser11', 'displayName': 'Test User 1', 'emailAddress': '', 'nameTooltip': 'cr', 'oauthTokenStatus': 2, 'signedIn': false, 'canRemove': true}, {'username':'testuser2', 'displayName': 'Test User 2', 'emailAddress': '', 'nameTooltip': 'cr', 'oauthTokenStatus': 2, 'signedIn': false, 'canRemove': false}], false)

Could you help in fixing this issue? I've got a lot of other regression to fix.
Comment 5 by, Oct 24 2012
Labels: followup
Project Member Comment 6 by, Oct 25 2012
The following revision refers to this bug:

r164049 | | 2012-10-25T11:44:53.181695Z

Changed paths:

Fix accessible label for network select control in OOBE.

BUG= 157477 

Review URL:
Comment 7 by, Oct 25 2012
Thanks for your help, Dominic!
Labels: -Mstone-24 MStone-25
24 is now 25 for CrOS Ash/Aura issues
Status: Fixed
Status: Verified
Issue is not reproducible on Lumpy with:
-Chrome OS: 3156.0.0
-Google chrome: 25.0.1315.1
Project Member Comment 11 by, Mar 10 2013
Labels: -Area-UI -Feature-Ash-OOBE -Feature-Accessibility -MStone-25 Cr-UI-Shell-OutOfBoxExperience Cr-UI-Accessibility M-25 Cr-UI
Comment 12 by, Mar 12 2013
Labels: Cr-UI-Shell-OOBE
Comment 13 by, Mar 12 2013
Labels: -Cr-UI-Shell-OutOfBoxExperience
Sign in to add a comment