Integration with Assistive Technology

This section provides an overview of the embedded and non-embedded assistive technology resources that can be used to help students with accessibility needs complete computer-based tests in the TDS.

Embedded assistive technology resources include the built-in test features in the TDS, such as the TTS and STT resources. These resources can be accessed without third-party software or hardware and do not require permissive mode to be turned on in the TDS. The embedded assistive technology tools in the TDS are available using both desktop and mobile devices.

Non-embedded assistive technology resources are the third-party hardware and accessibility software that students use to help them complete tests in the TDS. These resources require permissive mode to be turned on in the TDS and may require additional configuration steps prior to testing.

Students who use assistive technologies with a standard web browser should be able to use those same technologies with the TDS. The best way to test compatibility with assistive technologies is to take a practice test with those technologies turned on. If they do not work, refer to the additional configuration instructions in this manual as required.

Permissive Mode

Permissive mode, a complementary technical resource, is a setting that allows students to use non-embedded assistive technology to complete tests in the secure browser. When permissive mode is turned on, the secure browser’s security settings will be partially lowered to allow students to use resources that would otherwise be blocked. This setting should only be selected when using an approved, non-embedded accessibility software or device—for example, screen readers, magnifiers, braille screen readers, RBDs, etc.—and is not for stand-alone use.

Permissive mode is assigned in TOMS and activates when the student is approved for testing. The student’s assistive technology should already be set up for use with the TDS when testing with permissive mode begins. A student who has the permissive mode setting enabled should not continue with the sign-in process until the accessibility software is configured correctly.

Permissive mode is available only for computers running supported desktop Windows and macOS operating systems. When using Windows, the taskbar remains on-screen throughout the test after enabling accessibility software. However, forbidden applications are still prohibited.

When permissive mode is turned on, standard keyboard navigation in the secure browser is disabled to accommodate any potential keyboard commands associated with the assistive technology the student may be using. When permissive mode is turned off, the secure browser reoccupies the whole screen, and the student’s ability to use assistive technologies or switch between any other applications and the secure browser is suppressed.

For information about standard keyboard commands in the secure browser, refer to the Keyboard Navigation for Students subsection in the Features of the Student Testing Application section in the CAASPP Online Test Administration Manual.

Testing Using Permissive Mode

Permissive mode is available only for devices running supported desktop Windows and macOS operating systems. For information about supported operating systems, refer to the CAASPP and ELPAC Technical Specifications and Configuration Guide for Online Testing.

Note the following about using permissive mode:

• Accessibility software must be certified for use with the test delivery application.
• Forbidden applications still will not be allowed to run.
• Permissive mode will not allow applications, such as those using cloud-based technologies, to connect to the internet.

Testing in Windows

Students can follow the instructions in this subsection to use assistive technology alongside the secure browser with all supported Windows operating systems. To use accessibility software with the secure browser, complete the following steps:

1. Open the required accessibility software on the student’s testing device.
2. Open the secure browser and begin the standard sign-in process up to the TA or TE approval step.
3. When a student is approved for testing, the secure browser allows the operating system’s menu and taskbar to appear. If the taskbar is not visible, turn off the auto hide feature. The secure browser resizes, and the taskbar remains visible inside the test in its usual position. The student can press [Alt] + [Tab] to switch between the secure browser and accessibility applications that are allowed for use during the test session. The steps to take to ensure the taskbar is visible differ between Windows 10 and Windows 11:
   1. Windows 10:
      1. Right-click the taskbar.
      2. Select Properties.
      3. Toggle Automatically hide the taskbar in tablet mode to “off.”
      4. Close the Taskbar window.
4. Windows 11:
   1. Right-click the taskbar.
   2. Select Taskbar Settings.
   3. Scroll down the list in the right panel to the “Taskbar behaviors” section and then select the down arrow to open the section.
   4. Make sure the Automatically hide the taskbar checkbox is not selected.
   5. Close the Properties window.
5. The student must immediately switch to the accessibility software that is already open on the device so that it appears over the secure browser. The student cannot select (click) within the secure browser until the accessibility software is configured. To switch to the accessibility software application, select the application in the taskbar.
6. The student configures the accessibility software settings as needed. If the student needs to test with multiple accessibility applications simultaneously, they should configure all of them during this step.
7. After configuring all the necessary accessibility software settings, the student returns to the secure browser. At this point, the student can no longer switch back to the accessibility software. If changes need to be made, the student must sign out, make the changes, and then sign in again.
8. The student continues with the sign-in process.

Once permissive mode is turned off, the secure browser reoccupies the whole screen, and the student’s ability to use assistive technologies or switch between any other applications and the secure browser is suppressed.

How to Use Assistive Technology with Permissive Mode on macOS

The secure browser 17.0 for macOS requires the student to launch approved accessibility software after logging on to an assessment. The student should take these steps after logging on:

1. Open the required accessibility software on the student’s testing device and configure the accessibility software settings as needed.
2. Open the secure browser and follow the standard sign-in process.
3. On the first page of the assessment, select Applications in the global menu. When the App Launcher window opens, select the appropriate assistive technology software and then select [OK].
4. Return to the secure browser and continue testing.

ACI Technology

ACI assistive tools allow students with various impairments (such as physical and visual impairments) to interact with a computer without using a traditional mouse and keyboard setup. For instance, ACI technology such as Dwell Clicker 2 allows students to use a mouse without having to press the left or right mouse buttons.

The TDS does not include any embedded ACI tools, but it does support several third-party ACI technologies. Refer to a product’s user manual or web page for detailed instructions on configuration and use.

After configuration of an ACI device, the student may test it on a practice test administered through a supported secure browser prior to using it for operational testing.

Table 1 provides a list of third-party ACI devices that can be used in the TDS. While this list includes only the devices that CAI has tested thoroughly with the secure browser, there may be additional supported ACI devices that have not yet been tested. If a student needs to use an ACI device that has been discontinued or is not listed here, please test it in a practice test first to ensure there are no issues with it.

Configuring PCEye Mini with Windows Control on Student Devices

To configure the PCEye Mini, it should be plugged in to a computer that uses Windows Control software and installed by following the product’s installation instructions manually.

For students using PCEye Mini with Windows Control Software, the Word Prediction feature should be disabled by opening the application and navigating to Settings ➔ Keyboard.

Configuring Dwell Clicker 2

Take the following steps to configure Dwell Clicker 2 settings:

1. Open the application.
2. Select the [On-screen keyboard] icon.
3. Select the [Options] key.
4. In the window that pops up, make sure the Use Text Prediction checkbox is not checked.

Configuring HeadMouse Nano

With a SofType Keyboard

Take the following steps to configure HeadMouse Nano when using the SofType keyboard:

1. Open the SofType application.
2. Select View ➔ Word Bar from the menu.
3. Make sure the Prediction radio button is not selected.

For macOS

The HeadMouse Nano on macOS can be used to mimic mouse-clicking movements only in conjunction with an Access Switch device (such as an AbleNet Switch) and the regular Apple on-screen keyboard. When completing a test with a Switch, students can left-click, drag-and-drop, double-click, and right-click (right-clicking would require an additional Switch).

To configure HeadMouse Nano when using the Apple on-screen keyboard, open System Preferences ➔ Keyboard ➔ Text. Then, make sure the following checkboxes are not marked:

• Add period with double-space
• Capitalize words automatically
• Correct spelling automatically

Configuring Swifty: SW2

To configure Swifty Switch Access according to the student’s needs, the DIP switches listed in table 2 should be set when using Switch. After modifying DIP switch settings, unplug and replug Swifty to activate the settings.

Assistive Keyboard and Mouse Input Technology

Assistive keyboard and mouse input resources provide additional support to students with physical impairments who need to use a keyboard and mouse to respond to test items. These include keyboards with larger keys, computer mice with trackballs, and other tools that facilitate access for students with limited movement abilities.

The TDS does not include any embedded assistive keyboard and mouse input resources, as these typically involve the use of special hardware. However, the TDS does support several third-party assistive keyboard and mouse input tools.

Table 3 provides a list of third-party assistive keyboard and mouse input tools that can be used to test. If a student needs to use a device not listed here, the student may test it with a practice test prior to using it for operational testing to ensure there are no issues.