Assistive Technology not found: com.sun.java.accessibility.AccessBridge

Assistive Technology Not Found Error Notification


Customers running any program that has the Java Access Bridge feature enabled may see this error when attempting to run the PaperCut User Client software. We’ve seen this issue with ImageNow from Perceptive Content solutions, but this is not the only app that might cause this. This error may also be caused by other ‘screen reading’ applications.

The Cause

Since PaperCut changed Java Runtime Environments (JRE) for version 19.0, the instance of Java that powers the User Client Software has been incompatible with the Java Access Bridge accessibility features. When the Access Bridge is installed on the same machine as the User Client Software, it changes a config file and causes an error when our JRE attempts to read it.

Note 💡 In older versions of PaperCut (early releases of 15.x), you might see this issue when using mismatched versions of the Java Runtime Environment. If you are running an older version of PaperCut and you think this applies to you, skip to the “Solution for Older Versions of PaperCut” section below.

The Solution

The best fix for this problem is to disable the Access Bridge technology in the Java configuration files. To do this, follow these steps:

  1. Navigate to C:\Users\<username>
  2. Open the file called .accessibility.properties using a standard text editor (Notepad is fine)
  3. Find the following lines in the config:
    1. assistive_technologies=com.sun.java.accessibility.AccessBridge
    2. screen_magnifier_present=true
  4. Add a hashmark (#) in front of theses lines
  5. Save your changes to the file, restart the User Client Software

Solution for Older Versions of PaperCut

We generally suggest running pc-client-local-cache.exe in a login script or installing the client locally and running pc-client.exe. However, in this situation you may need to run pc-client-java.exe as this version of the PaperCut User Client will use the system installed Java Runtime Environment rather than the one we bundle.


Categories: Troubleshooting Articles, Administration


Keywords: jaws

Comments