A Accessibility Features in ODI
The accessibility features in Oracle Data Integrator aim to make aspects of navigating and using the product easier for persons with disabilities and for the aging population. The accessibility features support the use of standards-based assistive technology hardware and software (such as Freedom Scientific JAWS).
This appendix provides information about how to configure and use accessibility features for ODI. It helps you to understand certain keyboard shortcuts and steps to create mappings using keyboard.
This appendix includes the following sections:
Working with Java Access Bridge
Java Access Bridge (JAB) is a technology that exposes the Java Accessibility API in a Microsoft Windows DLL, enabling Java applications and applets that implement the Java Accessibility API to be visible to assistive technologies on Microsoft Windows systems. Java Accessibility API is part of Java Accessibility Utilities, which is a set of utility classes that help assistive technologies provide access to GUI toolkits that implement the Java Accessibility API.
In order for existing assistive technologies available on Microsoft Windows systems to provide access to Java applications, they need some way to communicate with Java Accessibility Utilities. Java Access Bridge supports this communication.
An assistive technology application running on Microsoft Windows (for example a screen reader) communicates with Java Access Bridge DLLs, which in turn communicates with the Java Virtual Machine through Java Access Bridge Java libraries. These Java libraries communicate with Java Accessibility Utilities. Java Accessibility Utilities collects information about what is happening in the Java application, which it forwards to the screen reader through Java Access Bridge.
For more details on JAB, refer to Java Access Bridge Documentation.
This topic has the following sections:
Installing Java Access Bridge (Windows Only)
- Download Java Access Bridge from the URL: http://www.oracle.com/technetwork/java/javase/tech/index-jsp-136191.html
- Install Java Access Bridge.
- Copy the
access-bridge.jar
andjaccess-1_4.jar
files from your installation location to thejre/lib/ext
directory. - Copy the
WindowsAccessBridge.dll, JavaAccessBridge.dll, and JAWTAccessBridge.dll
files from your installation location to thejre/bin
directory. - Copy the
accessibility.properties
file to thejre/lib
directory.
Note:
Refer to Java Access Bridge Documentation for more information on Java Access Bridge.Configuring Java Access Bridge
- Start or enable Java Access Bridge application from the location -
% JDK_HOME% \bin\jabswitch –enable
. Enable the JAB from the SAME JDK that you will use to start ODI Studio. Here,JDK_HOME
means java.home used by ODI, to know this start ODI and navigate toHelp -> About -> Properties
tab, search forjava.home
. It points to the default location -\Program Files\java\jdk..\jre
, so make sure enablingjabswitch
under\Program Files\java\jdk..\jre\bin dir
. - To launch the JAWS (Job Access With Speech) software, double-click the desktop icon or select the JAWS entry from the Start Menu.
- Start ODI Studio.
Note:
Refer to JAWS online help for special keyboard commands to make the software read the text on the screen. In the JAWS application, navigate to selectHelp->Keyboard
commands to know more about them.
Common Keyboard Commands
Some of the commonly used keyboard commands in Java Access Bridge are:
Key Combination | Usage |
---|---|
|
Toggle speech on/off Note: When using this keystroke, press and releaseINSERT + SPACEBAR , and then press S to mute the speech.
|
|
To read the next line |
|
To read the current line |
|
To read the current Window |
|
To read the selected text |
Troubleshooting
-
If JAWS reads only the dialog/window titles and if it does not read any of the text inside the dialog/window then it means you have not started Java Access Bridge or it is not working properly.
-
You need to start JAWS before starting ODI Studio. JAWS should be up and running when you are accessing ODI Studio. If not JAWS does not read all the text in ODI Studio.
-
Double check that your studio is being started by the JDK you enable.
-
If JAWS is not working properly, make sure you remove all the previous versions of java and all its related files along with registry entries from your system and then install the JDK clean (with all default values).
-
In order to have JAWS read tool tip text for a button you have to enable the option - read tool tip text from Settings -> verbosity preferences. By default, it is disabled. Search for verbosity option in the Settings menu and enable it to make JAWS read a tool tip.
-
Jaws can only read the User Interface (UI) components that you access by placing the cursor on them otherwise it cannot recognize the components and cannot read them for you.
Keyboard Navigation in ODI Studio
This section is a collection of keyboard actions that allow you to navigate through ODI Studio UI using the Keyboard (without Mouse). They are:
-
Shift + F10
– Functions like a right-click button on mouse. It opens the context menu on whatever component that has the focus/cursor on. Navigate to an item in the tree and press Shift-F10 - The context menu opens. -
Alt + F6
– Shift between dialogs. Alt +F6 has a focus cycle. If there are only two windows open at a time, focus will keep cycling between these two (for example, smart export dialog + main window). -
Menu Windows->Documents
– displays a list of multiple objects of same type. (i.e., opens the two mappings MAP1, MAP2. This list would represent both the mappings) -
Ctrl + Shift + Tab
- Displays a dialog of all open frames and any tabs of those frames (i.e.MAP1->Overview -> Logical -> Physical
) -
Shift + Arrow Keys
- moves objects around the mapping logical/physical diagram -
Alt + PGDN / PGUP
- Switches to the next / previous tab within a map (i.e.MAP1->Overview -> Logical -> Physical
) -
Ctrl + PGDN / PGUP
- Switches to the next / previous sub-tab on the main tab - Overview (i.e. Overview->Definition -> Execution -> Scenarios, and so on) -
TAB key
- tabs to the required editor (this is the standard FCP support) -
Arrow keys
- traverses the nodes and links on the Editor itself. -
Windows Context Menu key
- brings up the context menu (Shift + F10
also performs the same action)