Oracle Accessibility Conformance Report

The product and documentation was 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.
• Titles for Objects and Applets are provided.
• Controls have an associated name.
• Non-text characters have meaningful alternative text.
• CAPTCHAs are not used.

The product and documentation was 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.

The product and documentation was tested for:

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

The product and documentation was 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.

The product and documentation was tested for:

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

The product and documentation was tested for:

• There are no text fields that collect information about the user.

The product and documentation was 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 was 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 was tested for:

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

Exception:
BugDB #36333393 - Horizontal and vertical scroll bars are not visible in scope selector, unable to select hierarchy scopes.

The product and documentation was tested for:

• Images of text are not used.

The product and documentation was tested for:

• Text information reflows so that only one direction of scrolling is required while at 400% zoom.
• Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.

Exceptions:
BugDB #36333418 - Scope Selector hierarchy levels are not completely visible.
BugDB #36319590 - Menu items are not completely visible when selecting items by group.
BugDB #36324684 - Menu Drawer tabs are not completely visible.

The product and documentation was tested for:

• Non-text items have a contrast ratio of at least 3:1.

The product and documentation was tested for:

• When the following attributes and no others are modified there is no loss in functionality or content:
  • 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 was tested for:

• Dismissable -The content can be dismissed without moving the pointer or keyboard focus.
• Hoverable - When pointer hover triggers additional content, the pointer can be moved over the additional content without the additional content disappearing.
• Persistent - The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
• Information appears on hover or focus using default browser behavior, such as the title attribute of components.

The product and documentation was tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes.
• 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 was tested for:

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

The product and documentation was tested for:

• There are no single character keyboard shortcuts.

The product and documentation was tested for:

• Time limits in the product can be extended with at least 20 seconds warning up to 10 times.

The product and documentation was tested for:

• There is no moving, blinking or scrolling content.

The product and documentation was tested for:

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

The product and documentation was 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.
• WAI-ARIA Landmark elements are used outside of repetitive navigation links.

The product and documentation was tested for:

• Pages have a meaningful title specified in the TITLE element.

The product and documentation was tested for:

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

The product and documentation was tested for:

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

The product and documentation was tested for:

• Pages are in a site table of contents.
• Pages are fully inter-linked to each other.
• Page contains controls that enable reaching all pages.

The product and documentation was 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 was tested for:

• Visual indication of the location of the focus.

The product and documentation was tested for:

• There are no multipoint or path-based gesture actions.

The product and documentation was tested for:

• When an operation uses a single pointer, the down-event of the pointer is not used to execute any part of the function.
• When an operation uses a single pointer, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion.
• When an operation uses a single pointer, the up-event reverses any outcome of the preceding down-event.

The product and documentation was tested for:

• User interface components that include text or images of text and have a label, have a name that contains the text that is presented visually.

The product and documentation was tested for:

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

The product and documentation was tested for:

• Properly set lang attribute for each page.

The product and documentation was 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 was 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 was 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 was 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 was tested for:

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

The product was tested for:

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

The documentation was tested for:

• The documentation does not have input fields, except for the Search field.

The product and documentation was tested for:

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

The product was tested for:

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

The documentation was tested for:

• Content does not require user input

The product was tested for:

• Submissions can be reversed by the user.
• 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 documentation was tested for:

• The documentation does not require user input that modifies user controllable data.

This criterion is always satisfied for any content using HTML or XML.

The product and documentation was 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’.
• Frames have a meaningful title specified in the title attribute.

The product and documentation was tested for:

• Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus.

There are no accessibility or compatibility features to document. Product uses standard HTML specifications to support accessibility.

Product documentation is in electronic format.