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

Issue 632994 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug
Team-Accessibility

Blocked on:
issue 614453
issue 686948



Sign in to add a comment

Changing an accessibility setting in accessibility settings exits settings

Reported by nimerjaber1@gmail.com, Jul 31 2016

Issue description

Mode: force_next
Version: 54.0.2809.0
Reproduction Steps: 
1. Enable Chromevox next and navigate to status tray with Alt+Shift+S
2. Navigate to accessibility
3. Check high contrast mode
Expected: High contrast mode is checked, the status is announced, and I can check or uncheck other options.
Actual: As soon as I check an option, I am returned to where I was last at before going to accessibility settings.

 
Cc: lpalmaro@chromium.org dtseng@chromium.org
Status: Untriaged (was: Unconfirmed)
Able to reproduce in 54.0.2813.0
Labels: Phase3
Status: Available (was: Untriaged)
Just to confirm, this is happening in the short list of accessibility settings directly in the system tray menu, right? The one that appears when you have the setting enabled to "show accessibility options in the system menu"? 
Correct. Is this intended?
Components: UI>Shell>StatusArea
Owner: tdander...@chromium.org
@tdanderson can you find someone to fix this please?

I can repro as well.

Comment 5 Deleted

Blocking: -632102
Cc: tdander...@chromium.org
Labels: Needs-Feedback
Owner: lpalmaro@chromium.org
Status: Assigned (was: Available)
Looking at the code, it appears this is not a recent regression; the code which closes the menu when an item is selected has been around since 2012. However, that doesn't mean the behavior shouldn't be changed.

Laura, can you please clarify what the correct behavior should be?
Right, this is not a new behavior -- just a behavior we should rethink. In my opinion, once you change a setting in the status tray menu > accessibility, the menu should simply stay open until you press escape (or click that status area) to close it. This way, the checkboxes should behave like typical checkboxes that you can check and uncheck without the menu going away.
Labels: -cvox2
Labels: -Phase3
Blocking: 632102
Cc: yiyix@chromium.org
Labels: -Needs-Feedback M-55 Proj-MaterialDesign-CrOS
Owner: yiyix@chromium.org
Yi is looking at the a11y detailed view now. Yi, can you take a look and see what is causing the menu to close when selecting an item / assess how easy of a change this would be to make?

Adding Proj-MaterialDesign-CrOS for tracking, but if you find a simple fix for this it wouldn't need to land behind --ash-md.
Labels: -M-55 M-56
Owner: tdander...@chromium.org
Blockedon: 614453
Blocking: -632102
Labels: -M-56 -Proj-MaterialDesign-CrOS
This is a symptom seen for more detailed views than just a11y, and is a side effect of the way checkable rows are implemented by different surfaces. It's not feasible to get this fixed in time for the MD system menu launch (M-56) and I would not want to tackle this until MD system menu has had time to bake in front of users. I'm going to track this as part of our planned cleanup once the non-MD code has been ripped out.
Blockedon: 686948
Cc: zork@chromium.org
Labels: NewComponent-Accessibility NewComponent-Accessibility-ChromeVox
Labels: -NewComponent-Accessibility-ChromeVox NewComponent-Accessibility-Browser
Labels: -newcomponent-accessibility-browser -newcomponent-accessibility
Cc: omrilio@chromium.org
Owner: tbuck...@chromium.org
Status: Untriaged (was: Assigned)
Tom, Omri, and Zach: can you please help with re-triage?
Owner: lpalmaro@chromium.org
To lpalmaro@ for the rethinking of a11y effort.
Status: Assigned (was: Untriaged)

Sign in to add a comment