Oracle Accessibility Conformance Report

• Images that convey information have meaningful alternative text using ALT
• Images that are decorative are marked up using ALT=”” or CSS background images
• Titles for Objects and Applets are provided
• Controls have an associated name
• Text summary or alternative is provided for time-based media
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

• Images that convey information have meaningful alternative text using ALT
• Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)

• 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

In many places we are using OJET data-grid to display the table content. Since  OJET version 6.1 has some issue with the use of aria-label, we are getting accessibility errors for data-grid as there is no aria-label field for inner HTML table generated from oj-table. This issue is being tracked by BugDB 29911559. 

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 table captions/summaries where appropriate
• Style sheets are used only to change the layout and presentation on the screen

The product was tested for:

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

The documentation was tested for:

• The sequence of elements in the DOM matches 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

The product and documentation were tested for:

• Information is not conveyed using color.

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

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

The product was tested for:

• Images of text are not used

The documentation was tested for:

• Images of text are not used

The product was tested for:

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

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

• Time limits in the product can be turned off before they are encountered
• Time limits in the product can be adjusted to at least 10 times longer before encountered
• Time limits used are part of a real-time event, or an essential activity

The documentation was tested for:

• Time limits are not used

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

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

The documentation was tested for:

• A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page.

The product was tested for:

• Pages have a meaningful title specified in the TITLE element

The documentation was tested for:

• Pages have a meaningful title specified in the TITLE element

The product was tested for:

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

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

• The text of links and their surrounding paragraph, list, or table cell (with marked up table headers) is sufficient to describe their purpose.

The product was tested for:

• Pages are fully inter-linked to each other
• Page contains controls that enable reaching all pages

Multiple ways to locate a web page within a set of Web pages is not available for Web Pages that are the result of, or a step in, a process (Level AA).    This issue is tracked with BugDB 29911590.

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

• Headers describe the topic or purpose of the content below them

The product was tested for:

• Visual indication of the location of the focus

The documentation was tested for:

• Visual indication of the location of the focus

The product was tested for:

• Properly set lang attribute for each page

The documentation was tested for:

• Properly set lang attribute for each page

The product was tested for:

• Content is only provided in a single language (English)

The documentation was tested for:

• Content is only provided in a single language (English)

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

• 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

In the WEB documentation when using the search, a new window is created without warning and takes focus after the user invokes the submit button. This is tracked in bugdb ID: 30015456.

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

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

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

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

ISR is not able to identify the error field, however, it is displaying a valid error message. At this time we cannot identify the fields in the front end when ever we get an error message.

BugDB 29913181 has been raised to track this issue. 

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

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

The documentation does not support user input.

The product was tested for:

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

Not Applicable for the documentation since it does not have any provisions for user input.

The product was tested for:

• Submissions can be reversed by the user
• Data is checked for input errors with an opportunity for the user to correct them
• Data can be reviewed, corrected, and confirmed by the user before they are finalized

Not Applicable for the documentation since it does not allow for changes to data.

• 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

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

• 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 a meaningful programmatically exposed name

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.

Documentation has not documented accessibility features.  The following defect has been raised to track this issue:

bugdb ID: 28578685

Product documentation is in electronic format.