Accessibility Features in Chromebook Kiosk Mode

Students with approved accommodations need the Chromebook floating accessibility menu to use the built-in screen reader, text-to-speech, and other accessibility features. Because Bluebook runs in kiosk mode, the menu is not available by default and a student’s custom Chromebook settings won’t be applied. Use your Admin console to change this device setting. 

Important: Make sure accessibility features are available only to students approved to use them. Misuse can disrupt testing and lead to retests, makeups, or score cancellations.

How to Enable Accessibility Features

  1. Select the appropriate organizational unit, remembering to limit availability. Scroll down to learn more about using organizational units. 

  2. Go to Devices > Chrome > Settings > Device  Settings.  

  3. Change the Kiosk floating accessibility menu setting to show the menu in kiosk mode and click Save. 

  4. Change the Kiosk accessibility shortcuts setting to enable keyboard shortcuts and click Save. 

Learn about screen readers and text-to-speech on Chromebooks. 

How Students Use Accessibility Features

If your students don’t often test in kiosk mode on a Chromebook, they probably won’t know the essentials. For instance, they need to customize their accessibility settings every time they open Bluebook. Make sure they know how to access, customize, and use accessibility features when they use Bluebook to take a test on a Chromebook. Go to Using Bluebook on Chromebooks. 

Recommended Deployment Strategy  

You should always follow school or district polices for using organizational units (OUs) in the Admin console, but if your school or district does not provide guidance, we recommend using OUs to: 

  • Limit the availability of the floating accessibility menu and accessibility shortcuts.

  • Isolate applications that require conflicting device settings.

For example, the images below show how High School A used OUs to make sure that only some devices can use accessibility features in kiosk mode, and only on Bluebook. They took these steps: 

  1. They limited the availability of Bluebook by creating a Bluebook OU and deploying the app only to devices within that OU (figure 1).  

  2. Then they added an accessibility OU within the Bluebook OU, enabling the floating accessibility menu and accessibility shortcuts for devices assigned to the accessibility subgroup only (figure 2).  

  3. Finally, they uninstalled the Other Testing App from those devices (figure 3). Note that they used a separate OU for the Other Test so they can uninstall Bluebook from those devices if necessary. 

Figure 1

Figure 1 is a screenshot showing the Google admin console for High School A. Two organizational units are shown, Bluebook and Other Test. The Bluebook organizational unit is configured to hide the floating accessibility menu in kiosk mode and disable accessibility shortcuts.

Figure 2 

Figure 2 is a screenshot showing the Google admin console for High School A. The Bluebook organizational unit is expanded to show a child organizational unit called Accessibility. This organizational unit is configured to show the floating accessibility menu and enable accessibility shortcuts.

Figure 3

Figure 3 is a screenshot showing the Google admin console for High School A. The Other Testing App has been uninstalled from devices in the Bluebook organizational unit.

Related Topics