Oracle Accessibility Conformance Report

The Product was tested for:

• Images that convey information have descriptive alternative text
• Images that are decorative are marked up using ALT=”” or CSS background images
• Controls have an associated name 
• Time-based media is not used
• Client-side image maps are not used
• Non-text characters are not used
• CAPTCHAs are not used

The Product 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 at the discretion of the application author
• 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 was tested for:

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

Application authors can control the presentation order of UI elements on the screen, and when they do, that is reflected in the DOM and in the navigation sequence. The generated application pages are properly linearized without loss of meaning or context.

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

This product was tested for:

• Text is displayed in both device orientations without loss of functionality or visibility of the text.

This product was tested for:

• The expected meaning for form Input fields is programmatically determinable.

The product 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 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 in the browser up to 200% without loss of functionality

Images of text are not used.

This product was tested for:

• Vertical and Horizontal scrolling with 400% zoom. With this, there is no loss of information or content overlapping, with the exception noted below.

The product was tested for:

• Minimum non-text Contrast of at least 3:1 against adjacent colors.  The presence of visual information for identifying user interface components and states where applicable. Use of graphics required to understand content.

The product was tested for:

•  For content implemented using markup languages there is no loss of content or functionality when setting the designated style properties.

There is no content that appears on hover or focus.

The product 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
• 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 each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control

There are no single character keyboard shortcuts.

Time limits are not used by default in a generated application.

However, there is a session timeout of 4 hours for inactive sessions set by the server for security reasons, which is not configurable by the user. In case of an invalidated session, the user would need to log in again.

As generated the default application contains no moving blinking or flashing content.

The product was tested for:

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

As generated the default application does not contain repeated page content accross pages therefore there is no need for a means to skip it.

The product 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 order of navigation is determined by the application author and follows the sequence of components as they occur in the DOM which is also the order in which they are displayed on the page. 

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

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

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

• Visual indication of the location of the focus

There are no multipoint or path-based gesture actions.

There are no single pointer operations.

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

There are no functions that require motion of the device.

The product was tested for:

• Properly set lang attribute for each page.

By default, there are no passages in a language different from that of the page. If an application author were to include such content, they would need to mark that content with the lang attribute.

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 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 navigation component in the page header shell is not repeated on each page.

The product was tested for:

• Images and controls are used and identified consistently throughout the product. Where the author introduces their own icons and components into the app, they should take care to use them consistently.

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

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

The product was tested for:

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

The product was tested for:

• 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

Application authors can include mechanisms to allow the user to review and correct data before submission, or add custom validations that flag errors and give the user the opportunity to correct them.

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

• 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 appropriate state and property information conveyed using the relevant WAI-ARIA or HTML5 attributes
• Custom controls have a meaningful programmatically exposed name

The Product uses standard HTML5 components and Oracle JET components which properly expose name (label) and role. In cases where the author chooses to write a custom UI component, they would need to use the appropriate APIs to expose the name, role, and other relevant attributes.

The product was tested for:

• Status messages have role or properties set so that information is conveyed to assistive technology without the component receiving focus.

Documentation of Visual Builder runtime apps is not provided. Such documentation is the responsibility of the application author.

Visual Builder runtime applications do not provide any documentation. Any such documentation is the responsibility of the application author.