Oracle Accessibility Conformance Report

The 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
• 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
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

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

• HTML markup and coding of text that provides a correct and logical reading sequence.

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

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

The documentation was tested for:

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

The documentation was tested for:

• Information is not conveyed using color.

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

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

The documentation was tested for:

• Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential

The documentation was tested for:

• Text information reflows so that only one direction of scrolling is required while at 400% zoom.

The documentation was tested for:

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

The 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 1.5 times the font size
  • Spacing following paragraphs to 2 times the font size
  • Letter spacing (tracking) to at 0.12 times the font size
  • Word spacing to 0.16 times the font size

The documentation was tested for:

• Dismissable: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
• Hoverable: If pointer hover can trigger the additional content, then 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.

The documentation was tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes
• Logical movement of focus through the controls.
• Proper operation of unique keystrokes and access keys.

The documentation was tested for:

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

There are no single character keyboard shortcuts.

Time limits are not used.

There is no moving, blinking or scrolling content.

The documentation was tested for:

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

The 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 are marked up with Header elements outside of repetitive navigation links.

The documentation was tested for:

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

The documentation was tested for:

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

The documentation was tested for:

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

The documentation was tested for:

• Pages are in a site table of contents
• Pages are fully inter-linked
• Page contains navigation controls

The product documentation was tested for:

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

The documentation was tested for:

• Visual indication of the location of the focus.

The documentation was tested for:

There are no multi-point or path-based gesture actions.

The 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

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

There are no functions that require motion of the device.

The documentation was tested for:

• Properly set lang attribute for pages.

The documentation was tested for:

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

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

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

The 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.

The documentation was tested for:

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

The documentation was tested for:

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

The documentation was tested for:

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

The documentation was tested for:

• Content does not require user input

The documentation was tested for:

• Content does not allow for changes to data.

The documentation was tested for:

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

The 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

The documentation was tested for:

There are no status messages.

The documentation was tested for:

• Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts

The documentation was tested for:

• Responds to platform settings for color, contrast, font type, font size, and focus cursor

There is no user interface, therefore there is no documentation about the accessibility features of the product.

The product documentation is available in electronic formats only.