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
• Controls have an associated name
• 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 where appropriate
• Layout tables use appropriate markup
• Style sheets are used only to change the layout and presentation on the screen
• info and relationship information is provided via wai-aria attributes in HTML code

The product and documentation were tested for:

• The sequence of html elements in web pages 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.
• A fixed display orientation is required for essential functionality. 

The product and documentation were tested for:

• Input that collects information about the user has the appropriate input purpose

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
• All 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 more than 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:

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

The product and documentation were tested for:

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

The product 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 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:

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

The product and documentation were tested for:

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

The product and documentation were tested for:

• Single character keyboard shortcuts are only active when that component has focus.

The product and documentation were tested for:

• Product provides option to extend the session with following text after a period of application inactivity. “This page will expire unless a response is received within 2 minutes. Click OK to prevent expiration.”
• Adjust and Extend is supported.

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.

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 are meaningful and link context is described in inner text, alt, title and aria-label (wherever applicable)

The product and documentation were tested for:

• Pages are fully inter-linked
• 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 were tested for:

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

The product and documentation were 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 product 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 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 each page.

The product and documentation were tested for:

• All text is in one language so additional language tags are not required.

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:

• In circumstances where changing the value of the components causes a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window, warning is given prior to the user interacting with those user-interface components

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.

The product and documentation were tested for:

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

Exception:

• Since we are gradually transitioning to a newer technology, our application pages are mix of OJFF and OJET technologies, which can result in slight variations in the look and feel of different controls.

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

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 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.
• Essential Exception: ID’s may not be unique in a few cases where it cannot be avoided.
• 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, 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 product and documentation were tested for:

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

The product documentation describes:

• accessibility support for users.
• special keystrokes needed to operate controls

Accessibility related documentation can be found in the topic titled "Accessibility" by either clicking Accessibility link on the product Help's Home Page or by clicking the Introduction link and then clicking the Accessibility link in the product Help menu.

The Product has Electronic Documentation.