Oracle Accessibility Conformance Report

The documentation was tested for:

• Images that convey information have meaningful alternative text using ALT text
• Non-text content that is time-based media is not used
• Non-text content that is a test or exercise is not used
• Controls have an associated name
• Non-text characters are not used
• CAPTCHAS are not used
• Non-text content that is pure decoration is not used

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

• HTML markup and coding of text provides a correct and logical reading sequence.

The documentation was tested for:

• Instructions provided do not refer to things only based on their sensory characteristics, such as shape, size, visual location, orientation, color, or sound

The documentation was tested for:

• Color is not the only means to convey the information.

The documentation was tested for:

• Large-scale text, and images of large-scale text, have a contrast ratio of 3:1
• 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
• Proper operation of unique keystrokes and access keys, including those listed in the product documentation

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 within the documentation

The documentation was tested for:

• Time limits are not used in the documentation

The documentation was tested for:

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

The documentation was tested for:

• A "Go 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.

The documentation was tested fo:

• Pages have meaningful titles specified with the TITLE element

The documentation was tested for:

• Logical movement through the focusable components can be accomplished using only the keyboard, and 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) are sufficient to describe their content

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
• Pages contain controls that enable reaching other pages

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 the "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 do 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 use that mechanism in the same manner, 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 documentation

The documentation was tested for:

• The documentation does not have input fields, except for the Search field.

The documentation was tested for:

• Content does not require user input

The documentation was tested for:

• Content does not require user input

The documentation was tested for:

• There are no legal commitments or financial transactions required to view documentation.

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.
• 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 a meaningful programmatically exposed name
• Frames have a meaningful title specified in the title attribute

The documentation was tested for:

• Special keystrokes needed to operate controls
• Workarounds
• Descriptions of, and how to use, the hardware and software accessibility features that are part of the product and that provide compatibility with assistive technology
• Accessibility related documentation can be found within the product accessibility guide which you can find at http://docs.oracle.com/cd/E88493_01/index.html

The documentation was tested for:

• Product documentation is in electronic format