Oracle Accessibility Conformance Report

The product and 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.
• 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.
• Text summary or alternative is provided for time-based media.
• 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 product and documentation have been 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/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 product and documentation was tested for:

• The sequence of elements in the DOM matching a logical reading sequence.

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

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

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

• Resizeable text up to 200% without loss of content or functionality.

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

• Text information reflows so that only one direction of scrolling is required while at 400% zoom.
• An alternative mobile user interface is available and is accessed from the main application.
• Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.

The product and documentation was tested for:

• Non-text item contrast ratio of at least 3:1.

The product and 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 product and documentation has been 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.
• Information appears on hover or focus using default browser behavior, such as the title attribute of components.

The product and documentation was 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.
• Ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms).

The product and documentation have been tested for

• Proper movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control.

This product and documentation have been tested for:

• Single character keyboard shortcuts can be remapped.

The product was tested for :

• Time limits used are part of a real-time event, or an essential activity.

The product and documentation was tested for:

• There is no moving, blinking or scrolling content.

The product and documentation was tested for:

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

The product and docuemntation have been 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 has been tested for:

• Page Titles have descriptive text.
• Title elements

The product and documentation have been tested for:

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

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

• Pages are contained in a "site map."
• Pages can be found using the provided "search" function
• Pages are fully inter-linked to each other.
• Page contains controls that enable reaching all pages.

The product and documentation have been 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 was tested for:

• Visual indication of the location of the focus.

This product and documentation have been evaluated for

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

This product and documentation have been evaluated 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 has been 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 was tested for:

• Functionality that is operated by device motion or user motion can also be operated by user interface components.
• Responding to the motion can be disabled, except when the motion is used to operate functionality through an accessibility supported interface OR the motion is essential for the function.

The product and documentation have been tested for:

• Properly set lang attribute for each page.

The product and documentation have been tested for

• Proper use of lang attribute for text passages that are in a different language than that of the page.

The product and documentation have been 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 have been 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.
• 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 have been 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 have been tested for:

• Consistent use of icons
• Consistent terminology

The product and documentation have been tested for:

• detected input errors are described to the user in text, including identifying the item where the error occurred

The product and documentation have been tested for:

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

The product and documentation have been tested for:

• meaningful corrective actions in error messages.

The product and documentation have been tested for:

•   the ability to reverse, correct, and/or confirm transactions.

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

• Standard controls have a programmatically associated name, derived from the appropriate HTML elements and attributes, including LABEL and TITLE.
• Synthesized controls use WAI-ARIA markup to identify role, state and value information.
• Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’.
• Controls have a meaningful programmatically exposed name
•  Frames have a meaningful title specified in the title attribute

This product and documentation have been evaluated for:

• There are no status messages.

The product and documentation has been tested for:

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

The product and documentation have been tested for:

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

The Accessibility-related documentation can be found in the Fundamentals Guide in the Bookshelf and describes:

• The run time accessibility mode
• special keystrokes needed to operate controls.  

Documentation is provided in electronic format.