This topic provides information on the accessibility features for Oracle SQL Developer Data Modeler. It includes the following:
1.1 About Oracle SQL Developer Data Modeler Accessibility
It is our goal to make Oracle Products, Services, and supporting documentation accessible to the disabled community. Oracle SQL Developer Data Modeler supports accessibility features. For additional accessibility information for Oracle products, see the Oracle Accessibility Program page at:
1.2 Using a Screen Reader and Java Access Bridge with Oracle SQL Developer Data Modeler
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. See Oracle SQL Developer Installation Guide for the screen reader setup procedure, and for the recommended minimum technology stack.
1.3 Oracle SQL Developer Data Modeler Features that Support Accessibility
Oracle SQL Developer Data Modeler provides features that are designed to support accessibility.
1.3.1 Keyboard Access
Oracle SQL Developer Data Modeler features support keyboard access to Data Modeler functionality; a summary is provided in this section. The following menu and toolbar functionality is provided through keyboard access:
Users can navigate to and invoke all menu items.
All toolbar functions are accessible through menu items.
All menus and menu items have unique and functioning mnemonic keys.
All context menus within the navigators and source editor can be invoked.
Frequently used menu items have unique accelerator keys.
The following functionality is available in Data Modeler windows:
Navigate between all open windows, to all nodes within a window or pane, and between tabs in a window.
Set focus in a window or pane.
Invoke all controls within a window or pane, and perform basic operations.
Navigate and update properties in the Property Inspector.
Use Completion Insight and Code Templates in the source editor.
Invoke context sensitive help topics, navigate to and open all help topics, and navigate between the navigation and viewer tabs.
Open, close, dock, undock, minimize, restore, and maximize the applicable Data Modeler window.
You can press Escape to move the focus from the current dockable window to the last active editor. Press Shift+Escape to move the focus and also close the current window.
You can press Shift+F10 to open the context menu for any window. Use the Down Arrow and Up arrow keys to select a command and press Enter, or use the accelerators to invoke a command on the context menu.
The following functionality is available in Data Modeler dialogs and wizards:
Users can navigate to and invoke all controls within all wizards and dialogs.
The order in which the Tab key causes focus to flow is consistent and logical.
Mnemonic keys are provided for controls where appropriate.
1.3.2 Screen Reader Readability
Here is a summary of screen readability in Data Modeler, when it is used with a screen reader.
When used with menus and toolbars:
All menus and menu items are read.
All toolbar items, including the Navigator toolbar items, are read.
The hint text on all toolbar items is read.
When used with Data Modeler windows:
All open windows are read.
All components within each window, including tabs, are read.
Status text at the bottom of the IDE, and within the source editor, is read.
When used with dialogs and wizards:
All controls within all wizards and dialogs are read.
Hint text is read.
1.3.3 Flexibility in Font and Color Choices
The user interface in Data Modeler improves usability for people who are visually impaired by offering flexibility in color and font choices. The following font and color features are included:
Users can specify both the font and the size in which the font displays for code editors.
All features of the product have black text on a white or gray background.
Colored text, underlining, or images are never used as the only method of conveying information.
1.3.4 No Audio-only Feedback
In Data Modeler, there is no situation in which the only feedback a user receives is audible feedback. All audible feedback is accompanied by a visual indicator. For example, a prompt accompanies the bell sound that occurs when an error or illegal action has taken place.
1.3.5 No Dependency on Blinking Cursor and Animation
Data Modeler makes minimal use of a blinking cursor and animation:
No features in Data Modeler use blinking indicators, with the exception of the cursor in the source editor.
No features rely on animated sequences.
1.3.6 Screen Magnifier Usability
The Data Modeler user interface works well with screen magnifiers. All features of the product can be magnified by a screen magnifier.
1.3.7 How to Change the Editor or Tabbed View of a File
When you press Enter on a node in the Connections Navigator, you open the default editor for that file. To switch to the different editors and views available for a document; you can use the Alt+Page Up and Alt+Page Down accelerators to invoke the Navigate > Go to Window > Right Editor and Navigate > Go to Window > Left Editor menu commands, respectively.
1.3.8 How to Read Text in a Multiline Edit Field
To have the text in a multiline edit field read by a screen reader, you can select text by holding down the Shift key while moving the cursor either up or down with the Arrow keys, depending on the initial cursor position.
1.3.9 How to Read the Line Number in the Source Editor
To have the line number read by a screen reader while you are editing a file in the source editor, you can press Ctrl+G.
1.3.10 How to Access Exception Stack HTML Links and Generated Javadoc Links in the Log Window
After generating exception stack HTML links or Javadoc links in the Log window, they will not be recognized as links, but read as plain text by a screen reader. To access the links, set the cursor focus to the Log window. Right-click or press Shift+F1 and select Save As from the context menu. Save the contents of the Log window as an HTML file. Add the saved HTML file to a project or application workspace as a resource.
1.4 Recommendations for Customizing Oracle SQL Developer Data Modeler
Data Modeler provides a number of customization features that enable users to specify their requirements for keyboard usage, display attributes of Data Modeler, and timing where appropriate. All customization features are organized within the Preferences dialog. For maximum usability and to accommodate your needs, you should consider changing any of the following from the defaults to a more usable customized setting.
1.4.1 How to Customize the Accelerators Keys
You can add and change the default accelerator keys for Data Modeler in the Tools > Preferences > Shortcut Keys page. You can also load preset keymaps that you are accustomed to using.
1.4.2 How to Pass a Conflicting Accelerator Key to Oracle SQL Developer Data Modeler
In addition to changing the mapped accelerator keys, you can pass a conflicting accelerator key to JAWS by preceding the accelerator key combination with Insert+F3.
1.4.3 How to Change the Look and Feel of Data Modeler
You can change the default look and feel for Data Modeler in the Tools > Preferences > Environment page. The look and feel determines the display colors and shapes of objects like menus and buttons.
1.4.4 How to Customize the Fonts in Code Editors
You can change the font and font size that display in editors in the Tools > Preferences > Code Editor > Fonts page.
1.4.5 How to Customize Syntax Highlighting
You can change the font style, as well as the foreground and background colors used in syntax highlighting within the source editor in the Tools > Preferences > Code Editor > PL/SQL Syntax Colors page.
1.4.6 How to Display Line Numbers in Code Editors
You can display or hide line numbers in the source editor in the Tools > Preferences > Code Editor > Line Gutter page.
1.4.7 How to Change the Timing for Completion Insight
You can specify the number of seconds that Completion Insight is delayed, or disable Completion Insight, in the Tools > Preferences > Code Editor > Completion Insight page.
1.5 Highly Visual Features of Oracle SQL Developer Data Modeler
Data Modeler includes features that are highly visual, and these features have equivalent functionality that is available to people who are blind or visually impaired:
The UI and visual editors. The source editor provides equivalent functionality, as pages and UI elements can be completely designed and coded in the source editor.
The Component Palette. The source editor provides equivalent functionality, as elements and tags that can be selected from the Component Palette can also be entered in the source editor.
You can add a component from the Component Palette to the UI or visual editor using keystrokes.
In Data Modeler, it is possible to create, edit, and move elements on a diagram using only keystrokes.