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
• Titles for Objects and Applets are provided
• Controls have an associated name
• Time-based media is not used
• Image maps are not used
• Non-text characters 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
• Style sheets are used only to change the layout and presentation on the screen

The documentation was tested for 

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

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
• Instructions provided which refer to graphics included a reference to the text alternative of the graphic

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
• Instructions provided which refer to graphics included a reference to the text alternative of the graphic

The documentation was tested for

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

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

• Contrast setting is consistent through the user session
• Windows or other OS-level color settings are not over-ruled by product
• Large-scale text, and images of large-scale text, have a contrast ratio of at least 3: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:

• Content is presented without loss of information or functionality, and without requiring scrolling in two dimensions except for parts of the content which require two-dimensional layout for usage or meaning.
• 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 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 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.

The documentation was tested for

• The logical tab order through the product controls and selectable elements
• Ability to access page elements (links, buttons, pop-up close window buttons, selectable rows) and form element fields via key board
• Ability to perform functions from the keyboard only
• Logical movement of focus through the controls

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

• There is no single character keyboard shortcut in content

The documentation was tested for

• Time limits are not used within the documentation

The documentation was tested for

• 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 "Go 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 documentation was tested for

• Pages have meaningful titles specified with the TITLE element

The documentation was tested for

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

The documentation was tested for

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

The documentation was tested for

• Pages can be found using the provided "Search" function
• Pages are in a site table of contents
• Pages are fully inter-linked to each other
• Pages contain controls that enable reaching other pages

The 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 multipoint or path-based gesture actions

The documentation was tested for:

• 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

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 each page

The documentation was tested for

• Proper use of the "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 use that mechanism in the same manner, with navigation elements appearing in the same relative order each time

The documentation was tested for

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

The documentation was tested for

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

The documentation was tested for

• Content does not require user input

The documentation was tested for

• Content does not require user input

The documentation was tested for:

• The documentation does not require user input that modifies user controllable 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
• Pages validate to the HTML specification

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.
• 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 a meaningful programmatically exposed name
• Frames have a meaningful title specified in the title attribute

The documentation was tested for:

• There are no status messages

The product doesn't have user interface and that's why no accessibility or compatibility features to be documented.

Product documentation is in electronic format