Issue metadata
Sign in to add a comment
|
Changing an accessibility setting in accessibility settings exits settings
Reported by
nimerjaber1@gmail.com,
Jul 31 2016
|
||||||||||||||||||||||
Issue descriptionMode: 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.
,
Aug 5 2016
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"?
,
Aug 5 2016
Correct. Is this intended?
,
Aug 11 2016
@tdanderson can you find someone to fix this please? I can repro as well.
,
Aug 11 2016
,
Aug 12 2016
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?
,
Aug 19 2016
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.
,
Aug 19 2016
,
Aug 19 2016
,
Sep 14 2016
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.
,
Oct 7 2016
,
Nov 10 2016
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.
,
Jan 31 2017
,
Jan 31 2017
,
Mar 27 2017
,
Mar 28 2017
,
Apr 21 2017
,
Aug 9 2017
Tom, Omri, and Zach: can you please help with re-triage?
,
Aug 10 2017
To lpalmaro@ for the rethinking of a11y effort.
,
Aug 1
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by pbath...@chromium.org
, Aug 1 2016Status: Untriaged (was: Unconfirmed)