Java-based Application Accessibility


Java Access Bridge is the key component of Java-based Accessibility. The instructions for installing the Bridge are located at Installing Java Access Bridge on the Oracle web site.

Java Ferret is one of the utilities in Java Accessibility Utilities API. The Java Ferret example uses the Java Accessibility Utilities API to examine accessible information about the objects in the Java Virtual Machine.

Most known issues with Java-based applications are documented on the Oracle web site. The quickest way to locate these issues is to go to the Oracle Documentation website, then use the sites "Secure Search" function to search using keywords: Jaws, accessibility and ADA (for American's with Disabilities Act). Additional search options are availabe at Oracle9i Database Online Documentation

The highlighted text below is copied from the Oracle web site and presented here for convenience and quick reference. For direct access to the Oracle site for accessibility, use this link: Java (tm) Accessibility.

With the Java Accessibility API, developers can easily create Java applications that are accessible to persons with disabilities. Accessible Java applications are compatible with assistive technologies such as screen readers, speech recognition systems, and refreshable braille displays.

Oracle Forms Accessibility Information Oracle Forms Accessibility Information

Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle Corporation is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site.

To make the best use of our accessibility features, Oracle Corporation recommends the following software configuration: Using a Screen Reader and Java Access Bridge with Oracle Forms

In order for assistive technologies, like screen readers, to work with Java-based applications and applets, the Windows-based computer must also have Sun's Java Access Bridge installed, as described below.

Refer to the Oracle Developer Suite Installation Guide found in the root directory on the Oracle Developer Suite CD, in oracle_home\doc\core904\install\toc.htm for information about installing Oracle Developer Suite. Please refer to the Preface in the documentation found on the Oracle Developer Suite CD, in oracle_home\doc\core904\install\pref.htm for additional information about accessibility.

To set up a screen reader and Java Access Bridge with Oracle Forms:
  1. Install the screen reader, if it is not already installed.
  2. Install Oracle Forms.
  3. Refer to the Oracle Developer Suite Installation Guide for more information.
  4. Download Java Access Bridge 1.0.2. The file you will download is It is available from Refer to the Java Access Bridge documentation available from this web site for more information about installation and the Java Access Bridge.
  5. After downloading the file, extract the contents to a folder; for example, accessbridge_home.
  6. Install Java Access Bridge by running Install.exe from the accessbridge_home\installer folder.
  7. Confirm that you want to install the Java Access Bridge into each of the Java virtual machines displayed in the dialog. Click OK when you see the Installation Completed message.
  8. Confirm that two jar files: access-bridge.jar and jaccess-1_3.jar were added to the folder \oracle_home\jdk\jre\lib\ext during the install. If necessary, copy them from accessbridge_home\installer\installerFiles to oracle_home\jdk\jre\lib\ext.
  9. Confirm that two DLL files: JavaAccessBridge.dll and WindowsAccessBridge.dll were added to the folder oracle_home\jdk\jre\lib\ext. If necessary, copy them from accessbridge_home\installer\installerFiles to oracle_home\jdk\jre\lib\ext.
  10. Add the files listed above, JavaAccessBridge.dll and WindowsAccessBridge.dll, to the Winnt\System32 folder, as they must be in the system path in order to work with Oracle Forms.
  11. Confirm that the PATH environment variable has been updated to include the directory where the DLL files were installed, oracle_home\jdk\jre\lib\ext.
  12. Confirm that the file oracle_home\jdk\jre\lib\ includes the following line:
  13. If necessary, copy the file from accessbridge_home\installer\installerFiles to oracle_home\jdk\jre\lib.
  14. Copy the appropriate accessibility files to your Oracle JInitiator directory:
  15. Copy access-bridge.jar and jaccess-1_3.jar to the folder Program Files\Oracle\Jinitiator1.*\lib\ext.
  16. Copy to Program Files\Oracle\Jinitiator1.*\lib\ext.
  17. Start your screen reader.
  18. Start Oracle Forms by running the ifbld90.exe file from Oracle_Home\bin. The above steps assume you are running Windows and using a Windows-based screen reader. Java Related Dialogs And Windows Are Not Read By Jaws

(3032246) You need to add access-bridge.jar and jaccess-1_3.jar to the CLASSPATH. See Section, "Using a Screen Reader and Java Access Bridge with Oracle Forms" for more information. Workaround for Reading Accessibility PL/SQL Error Messages

Although compilation errors are displayed in the PL/SQL Compilation Message window, keyboard accessibility is limited. If the error message does not fit in the window, the workaround is to save the file and then run the command-line generator. This will generate an error file (.err), which you can then read in a text editor of your choice. To generate and view an error file:

  1. Save the .fmb file in Oracle Forms.
  2. In an MS-DOS prompt, type ifcmp90 and the location of the .fmb file. For example:
    ifcmp90 module=d:temp/module1.fmb


    If there are errors, a .err file containing the error message(s) will be generated. The .err file will be located in the same directory as the .fmb file and will have the same root name as the .fmb file. Open the .err file in your favorite text editor. Location of JAWS Scripts

JAWS scripts are now installed with Forms Developer. The location for these scripts is oracle_home\forms90\ScreenReader\, and are also available at Oracle Technology Network (OTN) at Graphics Fails Against Database (64bit)

(3080826) Due to a limitation in the 8.0.6 RSF, Oracle Graphics 6i on Windows cannot connect to a 64-bit database. Thus, if you are using Forms 9.0.4 to connect to a 64-bit database, and want to integrate with Oracle Graphics, you will need to upgrade your Oracle 6i home (where Graphics is installed) to use the RSF. List of Colors in the Default Color Palette

For a list of default colors available in Oracle Oracle Forms, see "Default Color Palette Colors" in the Online Help. Changing the Look-and-Feel for the Property Inspector and Navigator

You can change the Look-and-Feel for the Property Inspector and Navigator to the Forms 6i look-and-feel to enable color accessibility by setting the registry variable SET FORMS90_CLAF to value 1 under Oracle Home. FRM-18113 Error When Clicking On Design Capture

(3071580) Clicking on Design Capture triggers "FRM-18113: Form Builder failed to Initialize the Oracle Designer as an Automation Server." This error occurs because the appropriate Windows registry settings do not exist. To import the appropriate registry settings, double click ORACLE_HOME\CGENF61\de9i.reg, then exit and restart Oracle Forms.