Issue metadata
Sign in to add a comment
|
Chrome Vox being enabled during SBA testing
Reported by
dkawam...@kwes.k12.hi.us,
May 10 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0 Steps to reproduce the problem: 1. Keyboard shortcut enabled Ctrl + Alt + z during testing. 2. 3. What is the expected behavior? enabled screen reader. What went wrong? Screen reader began to talk during the test session. User can enable and disable Chrome Vox while taking the test. Test session will be invalid if witnessed. Did this work before? N/A Chrome version: 51 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 25.0 r0 Add a way in the admin console to disable individual accessiblility feature and or keyboard shortcuts. Chrome vox screen reader in particular.
,
Jun 27 2017
,
Aug 7 2017
Thanks for this feedback. Question for you - what if a student needs to enable this feature to be able to take the test, though? Why would that invalidate the test? We can look into adding this into the admin console, but I'm simply curious. abodenha@, any idea who might be able to work on this change?
,
Aug 7 2017
This seems like it should be rolled into bug 724164. Display and input team is looking at a revamp of hotkey handling. We can probably tackle this as part of that. dtseng@ I thought there was already a policy to allow disabling of ChromeVox. Is that not the case?
,
Aug 9 2017
I think there's already a policy for that: https://cs.chromium.org/chromium/src/components/policy/resources/policy_templates.json?q=f:.*policy.*%5C.json&dr&l=7224
,
Aug 18 2017
Looks like that policy can't be independently set on its own.
,
Aug 29 2017
Hi, Most of the students take the test without voice feature. If we had to ability to enable/disable the Chrome Vox then we could do testing with impaired students at a different time or day. When the chrome vox is accidently enabled it could invalidate a students test. Derek
,
Oct 10 2017
dkawamura@ there should be a setting in the admin console labeled "Turn off accessibility settings on sign-in screen upon logout." If I'm reading the code correctly that should force ChromeVox to off.
,
Oct 16 2017
Hi, Ok, will try it and let you know. Thanks, Derek
,
Oct 16 2017
Ok. I tried it. On the sign in screen and when your logged into an account you still enable the setting. However, when you launch the Kiosk Air Secure test it is disabled when the app launches and you can't enable it during the test. This is good.
,
Oct 16 2017
,
Oct 16 2017
Can you explain what this feature actually does on the chromebooks?
,
Oct 16 2017
ChromeVox? It allows visually impaired users to use Chrome OS. https://support.google.com/chromebook/answer/7031755?hl=en The option in the admin console does a blanket disable of accessibility features after signing out and in kiosk mode. There is always a difficult balance of making these features easily available to those that need them while at the same time preventing them from getting in the way of users that don't.
,
Oct 16 2017
Thank you! I think this resolves our issue with the students enabling the Chrome Vox keyboard shortcut during SBA testing. Also, other feature that might be accidently enabled too. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by rjahagir@chromium.org
, May 16 2017