Oracle Accessibility Conformance Report

The 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)
• Text summary or alternative is provided for time-based media

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

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

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
• Instructions provided which refer to graphics include a reference to the text alternative of the graphic

The documentation was tested for:

• Information is not conveyed using color

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

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

The documentation was tested for:

• Images of text are not used

The documentation was tested for:

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

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

• Time limits are not used

The documentation was tested for:

• There is no moving, blinking or scrolling content

The documentation was tested for:

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

The documentation was tested for:

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

The documentation was tested for:

• Pages have a meaningful title specified in the TITLE element

The documentation was tested for:

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

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

• Pages can be found using the provided "search" function
• Pages are in a site table of contents
• Pages are fully inter-linked to each other

The documentation was tested for:

• Headers describe the topic or purpose of the content below them
• Labels describe the purpose of the associated field

The documentation was tested for:

• Visual indication of the location of the focus

The documentation was tested for:

• Properly set lang attribute for each page

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

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

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

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

The documentation was tested for:

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

The documentation does not allow for changes to data.

The documentation was 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 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.
• Frames have a meaningful title specified in the title attribute

The product documentation describes:

• accessibility modes, either at installation or runtime
• special keystrokes needed to operate controls
• workarounds

Product documentation is in electronic format.