Oracle Accessibility Conformance Report

The WebUI 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
• Controls have an associated name
• Client-side image maps specify the ALT attribute on each AREA element
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

The documentation was tested for:

• Images that convey information have meaningful alternative text using ALT
• Information shown in complex images such as charts is also available in an alternative textual form
• CAPTCHAs are not used

The WebUI was tested for:

• User interface component labels are associated with the fields they are labeling 
• Headings are encoded with HTML heading tags
• 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:

• 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

The WebUI and documentation were tested for:

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

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

The WebUI and documentation were tested for:

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

The following defect was found:

• Bug 36795048 - Connection and Pipeline attributes in the WebUI are not visible in a Mobile view orientation.

The WebUI and documentation were tested for:

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

The WebUI and documentation were tested for:

• Information conveyed by color is available in alternative formats, such as shape, text, font weight

The WebUI 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 WebUI and documentation were tested for:

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

The WebUI and documentation were 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 WebUI and documentation were 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.

The WebUI and documentation were tested for:

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

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

• There is no additional content that becomes visible and then hidden with a pointer hover or keyboard focus.

The documentation was tested for:

• 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 WebUI and documentation were tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes

The WebUI and documentation were 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 WebUI and documentation were tested for:

• There are no single character keyboard shortcuts.

WebUIs  and documentation were tested for:

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

The WebUI and documentation were tested for:

• There is no moving, blinking or scrolling content

The WebUIs and documentation were tested for:

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

The WebUI was tested for:

• 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 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

The WebUI and documentation were tested for:

• Pages have a meaningful title specified in the TITLE element

The WebUI and documentation were tested for:

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

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

• Pages are fully inter-linked to each other
• Page contains controls that enable reaching all pages

The documentation was tested for:

• Pages are contained in a "site map"
• Pages can be found using the provided "search" function
• Pages are in a site table of contents

The WebUI 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 WebUI and documentation were tested for:

• Visual indication of the location of the focus

The WebUI and documentation were tested for:

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

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

The documentation was tested for:

• There are no single pointer operations

The WebUI and documentation were 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 WebUI and documentation were tested for:

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

The WebUI and documentation were tested for:

• Properly set lang attribute for each page

The WebUI was tested for:

• Not Applicable

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 WebU and documentatin 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 WebUI 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 WebUI 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 WebUI and documentation were tested for:

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

The WebUI 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 WebUI and documentation were tested for:

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

The WebUI was tested for:

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

The documentation was tested for:

• The documentation has no input fields, except for the search field.

The WebUI and documentation were tested for:

• There are no inputs to the WebUI or documentation that cause legal commitments or financial transactions

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

The WebUI 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 appropriate state and property information conveyed using the relevant WAI-ARIA or HTML5 attributes
• Custom controls have a meaningful programmatically exposed name 

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

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

The documentation was tested for:

• There are no status messages.

The CLI was tested for:

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

The CLI was tested for:

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

Not applicable for the WebUIs and documentation, as they only use technologies that run in a browser.

There are no specific Accessibility features that require documentation.

Product documentation is in electronic format.

N/A

N/A