Oracle Accessibility Conformance Report

The product and documentation were tested for:

• Images that convey information have meaningful alternative text using ALT
• There are no client-side image maps.
• Images that are decorative are marked up using ALT=”” or CSS background images
• Controls have an associated name

The product and documentation were tested for:

• User interface component labels are associated with the fields they are labeling
• Data tables specify SUMMARY or CAPTION
• Style sheets are used only to change the layout and presentation on the screen
• Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate 
• Layout tables use appropriate markup
• Headings are encoded with HTML heading tags
• List markup is used for marking up lists

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

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:

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

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
• 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 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.
• Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.

The product and documentation were tested for:

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

Exceptions

• Bug 31434984 - Contrast ratio for UAP help, Refresh & View Log/Output icons in SearchResultsTF UI does not meet 3:1 standard
• Bug 31434970 - Contrast ratio for images on SRS and Jobset pages does not meet 3:1 standard  

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 31435009 - Text Spacing in some elements of the Monitor UI do not meet this criteria
• Bug 31435023 - Text Spacing in some elements of the SRS & Jobset UI do not meet this criteria

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 (feature names may be different on different platforms)

Exceptions:

Bug 33534155 - Tab is not working for 'SIGN IN' button in SAFARI browser.

Bug 33534592 - After opening the request details,we can not select the Parent ID or Request ID

Bug 33534582 - After opening the request details, we can not select the action drop down and other options, except parameters sections. 

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

• There are no single character keyboard shortcuts.

The product and documentation were tested for:

• Time limits used are part of a real-time event, or an essential activity
• Application timeout options to continue or exit are provided after a period of application inactivity.

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.

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

• Page contains controls that enable reaching all pages
• Pages are contained in a "site map"
• Pages are in a site table of contents 
• Pages are fully inter-linked to each other

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

• Properly set lang attribute for each page

The product and documentation were tested for:

• All text passages are in the same language as 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 utilize that navigation mechanism in the same fashion, with navigation elements appearing in the same relative order each time

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, including identifying the item where the error occurred

The documentation was tested for:

• Content does not require user input

The product was tested for:

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

The documentation was tested for:

• Content does not require user input

The product was tested for:

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

The documentation was tested for:

• Content does not require user input

The product was tested for:

• Data can be reviewed, corrected, and confirmed by the user before they are finalized

The documentation was tested for:

• The documentation does not require user input that modifies user controllable data

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

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, SUMMARY, CAPTION, etc.

• Frames have a meaningful title specified in the title attribute

• Additional state information is programmatically exposed for HTML controls, 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:

• There are no status messages.

Exceptions :

• Bug 31439291 - Search Messages in the Results Table in the Monitor/ Searchresults TaskFlow UI cannot be programmatically determined
• Bug 31435064 - Search Messages in the Results Table in the SRS/Jobset UI cannot be programmatically determined

Details in the  Accessibility Features and Tips for Oracle Enterprise Scheduler   chapter of the Oracle Fusion Middleware Accessibility Guide.

Product documentation is in electronic format.