Database Actions Accessibility Information

Keyboard Access

The following menu and toolbar functionality is provided through keyboard access:

Users can navigate to and start 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 called.
Frequently used menu items have unique accelerator keys.

The following functionality is available in 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.
Call 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 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 start a command on the context menu.

The following functionality is available in dialogs and wizards:

Users can navigate to and start 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.

Screen Reader Readability

Here is a summary of screen readability in Database Actions, 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 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.

No Audio-only Feedback

In Database Actions, 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.

No Dependency on Blinking Cursor and Animation

Database Actions makes minimal use of a blinking cursor and animation:

No features use blinking indicators, with the exception of the cursor in the source editor.
No features rely on animated sequences.

Screen Magnifier Usability

The screen magnifier is dependent on the browser used. All features of the product can be magnified by a screen magnifier.

Highly Visual Features of Oracle Database Actions

Oracle Database Actions includes features that are highly visual such as:

Data Modeler diagramming
Widgets on the overview pages
Real Time SQL Monitor
DBA performance monitoring pages