Permissive Mode is a Online Testing System accessibility support that allows students to use non-embedded assistive technology to complete tests in the Secure Browser. It must be turned on for any students testing with third-party assistive technology tools. When Permissive Mode is turned on, the Secure Browser's security settings will be partially lowered to allow students to use tools that would otherwise be blocked. This accommodation should be assigned to students in TIDE before they begin testing.

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

When Permissive Mode is turned on, standard keyboard commands in the Secure Browser will be disabled in order to accommodate any potential keyboard commands associated with the assistive technology the student may be using.

Please note that accessibility software must be certified for use with the Online Testing System and forbidden applications will still not be allowed to run. For information about supported software and operating systems, see the Assistive Technology Manual.

Permissive Mode activates when the student is approved for testing. Students who have the Permissive Mode setting enabled should not continue with the sign-in process until their accessibility software is correctly configured.

To use accessibility software with the Secure Browser for Windows:

1. Open the required accessibility software on the student's testing device.
2. Open the Secure Browser. Begin the normal sign-in process up to the TA approval step.
3. When a student is approved for testing, the Secure Browser allows the operating system’s menu and task bar to appear.
   • The Secure Browser resizes, and the task bar remains visible inside the test in its usual position. Students can execute the keyboard shortcut Alt+Tab to switch between the Secure Browser and accessibility applications, such as JAWS and NVDA, that they are permitted to use in their test session. The task bar remains on-screen throughout the test after enabling accessibility software. However, forbidden applications are still prohibited.
4. The student must click the accessibility software application in the task bar immediately to switch to the accessibility software that is already open on the computer so that it appears over the Secure Browser. The student cannot click within the Secure Browser until the accessibility software is configured.

5. 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.
6. After configuring all the necessary accessibility software settings, the student returns to the Secure Browser and continues the sign-in process. 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 and then sign in again.

To use accessibility software with the Secure Browser for macOS 13.3+:

The Secure Browser for macOS 13.3+ requires students to launch approved accessibility software after logging in to the test.

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 test, click Applications in the global menu. From the App Launcher window that pops up, select the appropriate assistive technology software and click OK.
4. Return to the Secure Browser and continue testing.
   • Note: Students should not close the assistive technology application while the Secure Browser is still open, as they may not be able to relaunch it. If the student accidentally closes the assistive technology application, they must sign out and then sign in again.