|Java TM Access Bridge for Microsoft Windows, v1.0.2 FCS
The Java Access Bridge should only be installed by hand as a last resort. The recommended way to install the Java Access Bridge is to use the Java Access Bridge installer, which will locate the Java VMs installed on your system which will support the Java Access Bridge, and then install the Java Access Bridge into those Java VMs which you specifically request the Java Access Bridge to be installed into. The Java Access Bridge installer can be found in the directory
The instructions below describe what the Java Access Bridge installer does, allowing you to make those modifications by hand if need be. Please note, the Java Access Bridge package includes three editions of the Java Accessibility Utilities file ' jaccess.jar', which differs for JDK 1.1, Java 2 SDK 1.2, and Java 2 SDK 1.3 (named jaccess-1_1.jar, jaccess-1_2.jar, and jaccess-1_3.jar).
Using JDK 1.1 EnvironmentsCompatibility Information
The Java VM uses the CLASSPATH variable to specify which classfiles and directories should be searched in order to instantiate a class. Your CLASSPATH should look something like this:
set CLASSPATH=c:\jdk1.1.8\lib\classes.zip;c:\swing-1.1\swingall.jar; \
You will also need to add the AccessBridge-1_0 directory to your path, so that two DLLs which are part of the Java Access Bridge can be found and instantiated.
The Java Virtual Machine consults a number of property files as it starts up. You will need to modify the c:\jdk1.1.x\lib\awt.properties file in order to enable accessibility. The Java Accessibility Utilities examples documentation explain how this all works. The quick and dirty modifications you need to make the Java Access Bridge work are to add the following two lines to the awt.properties file:
The first line tells the Java VM to use an alternate EventQueue. This alternate contains the necessary support that was missing from the stock JDK 1.1. This functionality is built into the Java 2 platform (see below). The second line tells the replacement EventQueue (EventQueueMonitor) to load the AccessBridge assistive technology, which can be found by searching the CLASSPATH.
Using Java 2 Environments (Including SDK v1.2.2, v1.3.x and v1.4.x)
The Java 2 platform doesn't use the CLASSPATH variable. Instead, it searches the standard extensions directory (among others) to build a CLASSPATH. In addition, the Java 2 platform already contains the Java Foundation Classes (the swingall.jar file). Locate your Java 2 platform extensions directory, tyipcally at:
and copy the jaccess-1_2.jar file for Java 2 platform edition 1.2.x, or the jaccess-1_3.jar file for Java 2 platform editions 1.3.x and 1.4.x; and access-bridge.jar files into it. You will also need to add the AccessBridge-1_0 directory to your path, so that two DLLs which are part of the Java Access Bridge can be found and instantiated.
The Java Virtual Machine consults a number of property files as it starts up. You will need to modify the c:\jdk1.3.x\jre\lib\accessibility.properties file in order to enable accessibility. The Java Accessibility Utilities examples documentation explain how this all works. The quick and dirty modifications you need to make the Java Access Bridge work are to add the following line to the accessibility.properties file:
This line tells the Java VM to load the AccessBridge assistive technology, which it finds in the standard extensions directory. In addition, if you are using screen magnification technologies such as ZoomText from Ai Squared, you must also indicate the presence of screen magnification by also adding the following line to the accessibility.properties file:
In the Java Foundation Classes 1.1 with Swing 1.1, the name of the packages containing both the Swing classes and the Java Accessibility API classes changed (from com.sun.java.swing and com.sun.java.accessibility to javax.swing and javax.accessibility respectively). Java applications and applets built with earlier versions of Swing and/or the Java Accessibility API will not work with the Java Accessibility Utilities version 1.1, nor will they work with the Java Access Bridge. The compatibility table details the versions of the Java platform, Java Foundation Classes, Java Accessibility Utilities, Java Plugin, and Java Access Bridge can work with eachother. The basic summary is, the Java Access Bridge requires the latest versions of everything else in order to function..Working from a Browser
The Java Plugin, at here, provides a browser plug-in which contains the Sun Java VM. This VM includes the ability to replace the EventQueue in order to load assistive technologies (or, in the case of the JDK 1.2 version of the Java Plugin; load assistive technologies directly). The Java Plugin (version 1.2.2 and later) includes the Java Foundation Classes (and thereby Swing and the Java Accessibility API). The Java Plugin is typically installed on your c:\ drive within your Program Files directory. It may be a separate, or second Java VM. The Java 2 platform extensions directory is typically at:
which is where you must put the accessbridge.jar and jaccess.jar files. The parent lib directory is where the accessibility.properties file is located, which must be likewise modified as above.