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

Issue 704239 link

Starred by 6 users

Issue metadata

Status: WontFix
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

Enterprise support feature request - Crome Vox - Ctrl + Alt + Z - TestNav app loading in KIOSK mode

Reported by kmcc...@paramusschools.org, Mar 22 2017

Issue description

Chrome Version  56.0.2924     : <Copy from: 'about:version'>
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox:
         IE:

What steps will reproduce the problem?
(1)  Ctrl + Alt + Z turns on Chrome Vox
(2)  Unfortunately, this also works under our TestNav application loading in KIOSK mode which is to be a secure test site for PARCC testing.  
(3) From the management console, we need to be able to turn this accessibility feature "off" entirely in KIOSK mode so students cannot accidently turn it on with Ctrl + Alt + Z

What is the expected result?
TestNav application loading in KIOSK mode should not allow for Ctrl + Alt + Z to work; that is, turn on the narration feature.

What happens instead?
Upon Start-up or under the TestNav "change customer", the Ctrl + Alt + Z turns on the narration.  

Please provide any additional information below. Attach a screenshot if
possible.

 
Components: Enterprise UI>Shell>Kiosk
Labels: -Type-Bug Type-Feature

Comment 2 by pmarko@chromium.org, Mar 24 2017

Owner: sduraisamy@chromium.org
@sduraisamy: Raj, this seems to be a kiosk related issue which might require triage. Would you please take a look? Thanks.
Labels: OS-Chrome
Cc: sduraisamy@chromium.org
Owner: r...@chromium.org
Status: Assigned (was: Unconfirmed)
@rkc do you know if there's already a way for kiosk admins to disable ChromeVox?

Comment 5 by acro...@sdale.org, May 3 2017

The initial bug report isn't from a TestNav developer.  Nor am I.  We're both "end users" at school districts trying to ensure that we have a secure testing environment.

Here's a better understanding of what seems to be happening.

This is a combination of issues.

TestNav is a platform for delivering standardized tests in an educational setting.  As such, it has to try to completely control the delivery of accommodations.  TestNav is a Pearson product used for delivering a number of tests, including the ACT, Aspire, PARCC, GMade, some College Board tests, etc.

Without seeing their source code, I believe TestNav is *usually* supressing the Ctrl+Alt+Z keystroke that toggles Chromevox via javascript.

Their expectation is that Chromevox is disabled at the login screen (as our domain does, via the domain device setting to turn off accessibility settings upon logout).

The TestNav app doesn't *force* Chromevox to be turned off -- if this is even possible in ChromiumOS for Kiosk mode apps. 

Inside TestNav, one of the web pages loaded by the app doesn't include the code to suppress toggling Chromevox -- this is the screen referred to by the TestNav developers as the "home.testnav.com" screen.  Users reach this screen using the instructions supplied by Maryland on their state testing site and referenced in a comment to a closed bug report from 2015.

Because of this hole, it's possible for users to maliciously turn on Chromevox support and compromise the integrity of the secure testing environment.

The proper solution would be for TestNav and other kiosk mode secure testing apps to completely disable builtin accessibility settings and applications, replacing them with their own.  

If this functionality doesn't already exist for ChromiumOS kiosk mode apps, it needs to be added for proper use as a secure educational testing platform.  The expectation for a secure testing environment is that accommodations are managed via a plan and their usage is documented and controlled external to the users action.
Cc: r...@chromium.org
Owner: maxkirsch@chromium.org
Max, can you drive this?
There's a Chrome API for disabling ChromeVox, so I don't think we need an admin policy as well. I'll send this to TestNav to make sure they're using it.
Status: WontFix (was: Assigned)
Is the status of this bug "Won't Fix" because the only workaround for this is through Google API? Nothing else?

Sign in to add a comment