This is a growing issue and I've seen a spike of complaints since we rolled out the high contrast accelerator. It's especially a problem in schools because key combos with quickly visible effects make for easy pranks. And...well..KIDS.

Adding a setting to disable a11y hotkeys would go a long way towards resolving the problem. We can discuss other options, but I don't think we can ignore this.

ChromeVox is a big issue especially in classrooms. Too many times have I witnessed a silent classroom being disturbed suddenly by someone turning on ChromeVox at full blast.

Also, high contrast, I have turned on as a joke (because I am, well, a kid) It is extremely easy to do.

For schools, administrators should control this through policy, so the features can be turned off globally with exceptions for specific students with legitimate disabilities.

Hi all

Yes this is a problem for us as a school, children will change the settings on the device before logging in and then the next user sharing the Chromebook wouldn't know how to change it back and have to call IT dept.

Would like a feature to disable it globally on the device level so user can't change it.

Thanks

Thanks for bumping up the priority

We are seeing a rather significant upsurge in High Contrast issues in CBC. I suspect many are simple typos - the search+shift+h hotkey is very easy to trigger while trying to simply type a capital "H". 

The notification seems pretty explicit about what is happening and how to turn it off, but users are in a panic and don't notice the notification until it goes away.

We are getting daily posts on Chromebook Central from users who have ended up activating High Contrast mode. I thought the hotkey was being changed to ctrl+search+h

Since this is Pri-1, I would hope for resolution.

I have to repeat previous user's comment, as it applies to our schools as well. It is a serious, disruptive problem that needs to be fixed!


This is a problem for us as a school, children will change the settings on the device before logging in and then the next user sharing the Chromebook wouldn't know how to change it back and have to call IT dept.

Would like a feature to disable it globally on the device level so user can't change it.

Thanks

I'd settle for a keyboard shortcut that a user can press to easily turn off all accessibility features in one action (which requires no mouse/screen use).   [I can understand why it may be problematic to permanently disable the features] 

Several times a year I get a phone call from my elderly grandmother because she has inadvertently turned on high contrast, screen reader, magnifier, etc.  In some of these cases she can't get me remoted in easily.  I'd love to be able to give her a keyboard shortcut to just reset everything... (similar to ctrl + shift + 0 to reset display resolution)

Maybe this can be developed in an extension using the a11y api's and then a keyboard shortcut mapped to the extension?  https://developer.chrome.com/apps/accessibilityFeatures

(Bulk Edit) Adding the new conops Chrome OS hotlist to all open issues with the "#CBC-RS/TC-watchlist" tag, our former tracking tag.

Yes this is a real problem at our school and is costing valuable teaching time. Students quit one anothers chromebooks as they walk past, change orientation and resolution as a prank.
I would like the ability to disable the keyboard shortcuts that we do not use.
Please allow this within G suit admin.
Can't wait for this feature request to be added. 
Thanks
Marnie

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.