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
• Controls have an associated name
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

• Descriptive text about the content of the SVG element is provided via WAI-ARIA aria-label property in HTML code
• SVG sub elements that correspond to navigable data items within a component use of the WAI-ARIA img role
• Description of the structure of the component is provided via WAI-ARIA aria-label property in HTML code

• 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
• Layout tables use appropriate markup
• Style sheets are used only to change the layout and presentation on the screen
• info and relationship information is provided via wai-aria attributes in HTML code

The ojDataGrid and Data Visualization components use the WAI-ARIA application role instead of HTML table or other HTML elements.

In the case of the ojDataGrid component:

The product was tested for:

• Descriptive text about the content of the data grid is provided via WAI-ARIA aria-label property in HTML code
• Description of the structure of the data grid is provided via WAI-ARIA aria-describedby property in HTML code
• Row and column headers are identified via WAI-ARIA aria-labelledby property in HTML code
• Data cells are associated with the appropriate headers via WAI-ARIA aria-labelledby property in HTML code
• Description about the action performed on the data grid is provided via WAI-ARIA status role and alert role in the HTML code

In the case of the Data Visualization components:

The product was tested for:

• Descriptive text about the content of the SVG element is provided via WAI-ARIA aria-label property in HTML code
• SVG sub elements that correspond to navigable data items within a component use of the WAI-ARIA img role
• Description of the structure of the component is provided via WAI-ARIA aria-label property in HTML code

The product was tested for:

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

• 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

• 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

• 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

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

• 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
• 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 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 are not used

• There is no moving, blinking or scrolling content

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

This framework does not provide complete web pages, therefore this guideline does not apply.

This framework does not provide complete web pages, therefore this guideline does not apply.

This framework does not provide complete web pages. However for the individual components provided by the framework that have flow,

The product was tested for:

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

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

Framework does not provide complete web pages, therefore this guideline does not apply.

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

• Visual indication of the location of the focus

• Properly set lang attribute for each page

• Proper use of lang attribute for text passages that are in a different language than that of the page

• 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

• 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

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

• When input errors are detected, they are described to the user in text, including identifying the item where the error occurred

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

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

• Data can be reviewed, corrected, and confirmed by the user before they are finalized

• Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs
• HTML code validates to the HTML specification

• 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 programatically exposed name

The product is not a platform or does not have access to platform accessibility features.

The product is not a platform or does not have access to platform accessibility features.

• special keystrokes needed to operate controls
• workarounds

Accessibility-related documentation can be found at: https://docs.oracle.com/en/middleware/developer-tools/jet/7/develop/developing-accessible-applications.html

A reference guide for keystrokes and touch gestures can be found at: http://www.oracle.com/pls/topic/lookup?ctx=jetlatest&id=OJACC

Product documentation is in electronic format.

Oracle JET is an open source product that provides support through community forums only.  There is no phone based support.

Technical Support can be found in the Community Forums at: 

https://community.oracle.com/community/groundbreakers/development_tools/oracle-jet/content

Oracle JET is an open source product that provides support through community forums only.  There is no phone based support.

Technical Support can be found in the Community Forums at: 

https://community.oracle.com/community/groundbreakers/development_tools/oracle-jet/content