Oracle Accessibility Conformance Report

The product and documentation were tested for:

• Images that convey information have meaningful alternative text using ALT
• Images that are decorative are marked up using ALT=”” or CSS background images
• Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)
• Titles for Objects and Applets are provided
• Controls have an associated name
• Text summary or alternative is provided for time-based media
• Client-side image maps specify the ALT attribute on AREA elements.
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

The product and documentation were tested for:

• User interface component labels are associated with the fields they are labeling
• Headings are encoded with HTML heading tags
• List markup is used for marking up lists
• Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate
• Data tables specify SUMMARY or CAPTION
• Layout tables use appropriate markup
• Groups of components are marked up with their description
• Style sheets are used only to change the layout and presentation on the screen

Exceptions:

• Ports usage table does not have accessible text.This issue is reported in the bug 32098345
• Purge Policies table is empty. This issue is reported in the bug 32098362.
• ESSWork Assignment Details table is empty.This issue is reported in the bug 32098365.

The product and documentation were tested for:

• The sequence of elements in the DOM matches a logical reading sequence

The product and documentation were tested for:

• Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound
• Instructions provided which refer to graphics included a reference to the text alternative of the graphic

The product and documentation were tested for:

• Text is displayed in both device orientations without loss of functionality or visibility of the text.

The product and documentation were tested for:

• No text fields that collect information about the user.

The product and documentation were tested for:

• Information conveyed by color is available in alternative formats, such as shape, text, font weight
• Information conveyed by color has a contrast ratio of at least 3:1

The product and documentation were tested for:

• Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
• Other text and images of text have a contrast ratio of at least 4.5:1

The product and documentation were tested for:

• Text can be resized up to 200% without loss of content or functionality

The product and documentation were tested for:

• Images of text are not used

The product and documentation were tested for:

• Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions

The product and documentation were tested for:

• Non-text Contrast has ratio at least 3:1 against adjacent color

The product and documentation were tested for:

No loss of content or functionality occurs by setting the following text spacing properties and by changing no other style property: 

• Line height (line spacing) to at least 1.5 times the font size;
• Spacing following paragraphs to at least 2 times the font size;
• Letter spacing (tracking) to at least 0.12 times the font size;
• Word spacing to at least 0.16 times the font size.

The product and documentation were tested for:

• Content appears on pointer hover or keyboard focus can be dismissed without moving pointer hover or keyboard focus.
• If the pointer hover can trigger the additional content, the pointer can be moved over the additional content without the additional content disappearing.
• The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.

The product and documentation were tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes
• Proper operation of unique keystrokes and access keys, including those listed in the product documentation
• The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms)

The product and documentation were tested for:

• Movement of focus through controls only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control

The product and documentation were tested for:

• Single keyboard shortcut is not implemented in the product. 

The product and documentation were tested for:

• Time limits are not used

The product and documentation were tested for:

• There is no moving, blinking or scrolling content

The product and documentation were tested for:

• No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz

The product and documentation were tested for:

• A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page.
• Structure and hierarchy is marked up with Header elements outside of repetitive navigation links

The product and documentation were tested for:

• Pages have a meaningful title specified in the TITLE element

The product and documentation were tested for:

• Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence

The product and documentation were tested for:

• The text of links and their surrounding paragraph, list, table cell (with marked up table headers) is sufficient to describe their purpose

Exceptions:

• "Lock Session" button on all pages do not have discernible text. This issue is reported in the bug 32098359

• "Recording" button on all pages do not have discernible text. This issue is reported in the bug 32098360.

The product and documentation were tested for:

• Pages are fully inter-linked to one another
• Page contains controls that enable reaching the pages

The product and documentation were tested for:

• Headers describe the topic or purpose of the content below them
• Labels describe the purpose of the associated field

The product and documentation were tested for:

• Visual indication of the location of the focus

The product and documentation have not yet been evaluated for this criteria.

The product and documentation were tested for:

• When a single pointer is used, pointer completion is done on the up event, and a mechanism is available to abort the function before completion or to undo the function after completion.

The product and documentation were tested for:

• For user interface components with labels that include text or images of text, the name contains the text that is presented visually.

The product and documentation were tested for:

• There are no functions that require motion of the device.

The product and documentation were tested for:

• Properly set lang attribute for pages

The product and documentation were tested for:

• Proper use of lang attribute for text passages that are in a different language than that of the page

The product and documentation were tested for:

• When an element receives focus, it does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window

The product and documentation were tested for:

• Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window

The product and documentation were tested for:

• Pages that are grouped together into sets with a common navigation mechanism utilize that navigation mechanism in the same fashion, with navigation elements appearing in the same relative order each time

The product and documentation were tested for:

• Images and controls are used and identified consistently throughout the product

The product and documentation were tested for:

• When input errors are detected, they are described to the user in text, including identifying the item where the error occurred

The product and documentation were tested for:

• Labels or instructions are provided when the product requires user input

Exception:

• Text field in the Machines Page does not have label.This issue is reported in the bug 32098350.

The product and documentation were tested for:

• Where suggestions for fixing an input error are known, they are provided to the user

The product and documentation were tested for:

• Data is checked for input errors with an opportunity for the user to correct them
• Data can be reviewed, corrected, and confirmed by the user before they are finalized

The product and documentation were tested for:

• Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs
• Pages validate to the HTML specification

The product and documentation were tested for:

• HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
• Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’.
• Custom controls have appropriate roles specified using the role attribute
• Custom controls have appropriate state and property information conveyed using the relevant WAI-ARIA or HTML5 attributes
• Custom controls have a meaningful programatically exposed name
• Frames have a meaningful title specified in the title attribute

The product and documentation were tested for:

• Status Messages are not used

For information on how to enable accessibility mode for Oracle Enterprise Manager Fusion Middleware Control, refer to the section "Accessibility Features and Tips for Fusion Middleware Control" in the Oracle Fusion Middleware Accessibility Guide.

Product documentation is in electronic format