Home > SQL Developer Accessibility... > Oracle SQL Developer Featur...
Oracle SQL Developer provides features that are designed to support accessibility.
Oracle SQL Developer features support keyboard access to SQL Developer 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 SQL Developer 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 SQL Developer window.
Tips:
|
The following functionality is available in Oracle SQL Developer 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.
Here is a summary of screen readability in SQL Developer, 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 SQL Developer 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.
The user interface in SQL Developer 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.
In SQL Developer, 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.
SQL Developer makes minimal use of a blinking cursor and animation:
No features in SQL Developer use blinking indicators, with the exception of the cursor in the source editor.
No features rely on animated sequences.
The SQL Developer user interface works well with screen magnifiers. All features of the product can be magnified by a screen magnifier.
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.
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.
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.
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.