Oracle Accessibility Conformance Report

The product and documentation were tested for:

• 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, such as whether a field is ‘required’.
• Images that convey information have meaningful alternative text.
• The product does not use image maps or CAPTCHAs.

The product and documentation were tested for:

• Structure and hierarchy is marked up with Header elements.
• Meaningful labels programmatically associated with form elements.
• Style sheets are used only to change the layout and presentation of the screen
• 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

Exceptions :

• Bug 31466548 : Missing row headers and summaries on the Landing page

The product and documentation were tested for:

• The sequence of elements in the DOM 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 which refer to graphics reference 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.

The product and documentation were tested for :

• Text fields which collect information about the user contain the appropriate autocomplete content attribute.

The product and documentation were tested for:

• Information conveyed by color or font styles is available in alternative formats, such as shape and text.
• Information conveyed  has a contrast ratio of at least 3:1

The product and documentation were tested for:

• Text and images of text in non-disabled controls have a luminosity contrast ratio of at least 4.5:1.
• Large scale text has a minimum ratio of at least 3:1

Exceptions:

• Bug 21309912  Color contrast. Instructional text on one form has 2:80:1 contrast, not the required 4.5:1.

The product and documentation were tested for:

• Response to the operating system Large Fonts mode
• Text can be resized up to 200% without loss of content or functionality

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

Exceptions :

• Bug 31465045 : Scroll bars are missing on the Administration and Evidence search pages.

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

Exceptions :

• Bug 31465151 : Text is truncated in fields on the Landing Page.

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:

• Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence
• StickyKeys, FilterKeys and Toggle Keys usage.

The product and documentation were tested for:

• Movement of focus through various components, using only keyboard, has no "keyboard trap" that prevents focus from moving away from any component

The product and documentation were tested for  :

• Single character keyboard shortcuts can be turned off.
• Single character keyboard shortcuts can be remapped.
• Single character keyboard shortcuts are only active when that component has focus

The product was tested for:

• Content that has time limits can be adjusted by the user.
• Users are warned before time expires and can extend the time limit.

The documentation was tested for:

• There are no time limits

The product and documentation were tested for:

• Content that automatically updates, or time limits, can be adjusted by the user.
• Moving, blinking, or scrolling information that is designed to last for more than three seconds can be paused.
• Moving, blinking, or scrolling content that is pure decoration can be stopped or hidden.

The product and documentation were been tested for:

• No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz.
• No portion of the screen flashes more than three times in any one second period.

The product and documentation were tested for:

• Structure and hierarchy is marked up with Header elements outside of repetitive navigation links

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 and their surrounding paragraph, list, table cell (with marked up table headers) is sufficient to describe their purpose

The product and documentation were tested for:

• Pages are inter-linked
• Page contains controls that enable reaching related 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 cursor position

The product and documentation were tested for  :

• Multipoint or path-based gesture actions can be completed using a different input modality.
• The multipoint or path-based gesture actions are essential

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

• Pages have lang attribute properly set

The product and documentation were tested for:

• There are no passages of text in a language other than the main language of the page.

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:

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

• Pages that are grouped together into sets with a common navigation mechanism use the navigation in the same way and the elements appear in the same order

The product and documentation were 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, and the item where the error occurred is identified.

Documentation does not require any user input.

The product was tested for:

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

Documentation does not require any user input.

The product was tested for:

• Error messages offer suggestions to the user for fixing the error, when the system has simple suggestions.

The documentation was tested for:

• Documentation does not require user input.

The product was tested for :

• Data can be reviewed, corrected, and confirmed by the user before it is finalized.

The documentation was tested for:

• The documentation does not collect data, and only has a search field.

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

The product and documentation were tested for:

• FRAMES and iFRAMES are titled with meaningful text
• 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, such as whether a field is ‘required’.

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

• The documentation does not generate status messages.

Details are available in the Accessibility Features and Tips for Oracle Business Process Management  chapter of the Oracle Fusion Middleware Accessibility Guide

Product documentation is in electronic format.