Oracle Accessibility Conformance Report

The product was tested for:

• Non-text content that is presented to the user has a text alternative that serves the equivalent purpose.
• Complex images, such as charts and graphs, are not used.
• Data tables include a summary or caption, programmatically connected with the table using the appropriate platform-specific technique.
• Controls have an associated name.
• Time-based media are not used.
• Non-text characters are not used or have meaningful alternative text.
• CAPTCHAs are not used.

The product documentation was tested for:

• Images that convey information have meaningful alternate text using ALT.
• Images that are decorative are marked up using ALT=”” or CSS background images.
• Controls have an associated name.
• Non-text characters are not used or have meaningful alternative text.
• CAPTCHAs are not used.
• Does not include client-side image maps.
• Does not include time-based media

The product was tested for:

• Information displayed in the user interfaces of this product appears as text.
• User interface component labels are associated with the fields they are labeling using the appropriate platform-specific technique.
• Headings are marked using the appropriate platform-specific technique.
• Lists are marked using the appropriate platform-specific technique.
• Tables are marked including row and column headers and table captions/summaries where appropriate using the appropriate platform-specific technique.
• Groups of components are marked with a description for the group using the appropriate platform-specific technique.
• Results from requests issued using the user interfaces appear as text.

The product documentation was tested for:

• User interface component labels are associated with the fields they label.
• 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 was tested for:

• The platform's built-in assistive technology reading/presentation sequence matches the logical reading sequence.

The product documentation was tested for:

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

The product 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
• Content is not displayed based on shape, size, visual location, or sound.

The product documentation was tested for:

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

The product was tested for:

• Content does not restrict its view and operation to a single display orientation

The product documentation was tested for:

• Content does not restrict its view and operation to a single display orientation

The product was tested for:

• The purpose of input fields is identified using the appropriate platform-specific technique.
• Input fields receive user input as text

The product was tested for:

• Information conveyed by color is available in alternative formats, such as shape, text, and font weight.
• Color coded information is presented in conjunction with text which conveys the meaning independently from the color used.

The product documentation was tested for:

• Information conveyed by color is available in alternative formats, such as shape, text, and font weight.

The product was tested for:

• Does not interfere with or disregard the color and contrast settings of the underlying graphical environment of the operating system.
• 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 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 was tested for:

• Text can be resized up to 200% without loss of content or functionality, using the appropriate mechanism of the platform.

The product documentation was tested for:

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

The product was tested for:

• Text is used to convey information wherever images of text are used.

The product documentation was tested for:

• Images of text are not used.

The product was tested for:

• Text information reflows so that only one direction of scrolling is required while at 400% zoom.

The production documentation was tested for:

• Text information reflows so that only one direction of scrolling is required while at 400% zoom.

The product was tested for:

• Graphical objects have a contrast ratio of at least 3:1.

The product documentation was tested for:

• Graphical objects have a contrast ratio of at least 3:1.

The product was tested for:

• The product does not have content implemented using markup languages that support editing the text style properties in this criteria.

The product documentation was tested for:

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

• Information appears on hover or focus using default browser behavior, such as the title attribute of components.

The product was tested for:

• Ability to perform functions from the keyboard only
• Logical movement of focus through the controls.
• Proper operation of unique keystrokes and access keys, including those listed in the product documentation.

Product exceptions:

• Bug 15437503 - Agents Access Tables get focus when no items in table

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

The product was tested for:

• Movement of focus through control only using the keyboard, with no keyboard trap that prevents focus from moving away from any control using the appropriate platform-specific technique for focus movement, for example, via commands to the built-in assistive technology of touch devices.

The product documentation was tested for:

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

The product was tested for:

• Single character keyboard shortcuts are only active when that component has focus.

The product  production was tested for:

• Single character keyboard shortcuts are only active when that component has focus.

The product was tested for:

• Time limits in the product can be turned off before they are encountered.
• Time limits in the product can be set to be up to 60 minutes.

The product documentation was tested for:

• Time limits are not used.

The product was tested for:

• Does not move, blink, or scroll information.
• Does not periodically refresh content except for in-progress indicators during long-running operations.
• Refreshes displayed content only in response to a request issued by the user.

The product documentation was tested for:

• There is no moving, blinking, or scrolling content.
• There is no auto-updating content.

The product and product documentation was tested for:

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

The product was tested for:

• Does not display blocks of content that is repeated on multiple panels.

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

• Panels have a unique title that describes its topic or purpose.

The product documentation was tested for:

• Pages have meaningful titles specified with the TITLE element.

The product was tested for:

• Visual indication of the position of the cursor
• Current focus location is programmatically exposed
• Logical movement through the focusable components using only the keyboard, in an order that follows a meaning sequence

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

• Links are not used in the product.

The product 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 purpose and content.

The product was tested for:

• Web pages are not used in the product.

The product 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 one another.
• Pages contain controls that enable reaching other pages.

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

• Visual indication of the location of the focus using the appropriate platform-specific technique.

The product documentation was tested for:

• Visual indication of the location of the focus.

The product was tested for:

• There are no multipoint or path-based gesture actions.

The product documentation was tested for:

• There are no multipoint or path-based gesture actions.

The product was tested for:

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

The production documentation was tested for:

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

The product was tested for:

• User interface components with labels that include text have a name that contains the presented text

The product documentation was tested for:

• User interface components with labels that include text have a name that contains the presented text

The product was tested for:

• There are no functions that require motion of the device.

The product documentation was tested for:

• There are no functions that require motion of the device.

The product was tested for:

• The user interfaces of this product have been internationalized.  The language that they display is determined by the locale setting of the operating system on which they run.

The product documentation was tested for:

• Properly set "lang" attribute for pages.

The product was tested for:

• The user interfaces of this product have been internationalized.  The language that they display is determined by the locale setting of the operating system on which they run.

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

• Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline does not apply.

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

The product was tested for:

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

The product documentation was tested for:

• Images and controls are used and identified consistently throughout the documentation.

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

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

The product was tested for:

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

The product documentation was tested for:

• Product documentation does not have input fields

The product was tested for:

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

The product documentation was tested for:

• Product documentation does not require user input.

The product was tested for:

• Data entered by the user is checked for input errors, and the user is provided an opportunity to correct them.

The product documentation was tested for:

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

The product was tested for:

• Markup languages are not used to generate the user interface.

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

• User interface components have a programmatically associated name and role using the appropriate platform-specific techniques for this.
• State information, properties, and values are programmatically exposed for user interface components using the appropriate platform-specific techniques for this.

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

• Markup languages are not used to generate the user interface.

The product documentation was tested for:

• There are no status messages.

The product were tested for:

• Does not disrupt accessibility features, such as Sticky Keys, High Contrast, and Large Font.

The product  was tested for:

• Does not interfere with or disregard the platform settings for color, contrast, font type, font size, and focus cursor.

The product documentation was tested for:

• Describes special keystrokes needed to operate controls.
• Describes 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 documentation.

Accessibility-related documentation can be found in:

• Administrator guide
• Online help

Product documentation is in electronic format.