ACR: Oracle JavaScript Extension Toolkit (JET) 21.0.0

Oracle Accessibility Conformance Report

VPAT® Version 2.5

Name of Product:

 Oracle JavaScript Extension Toolkit (JET) 21.0.0

Alternate Titles:

Product Description:

Oracle JET is a JavaScript Extension Toolkit (JET) targeted at intermediate to advanced JavaScript developers working on client-side applications. It's a collection of open-source JavaScript libraries along with a set of Oracle-contributed JavaScript libraries that make it as simple and efficient as possible to build applications that consume and interact with Oracle products and services. Specifically Oracle Cloud Service.

Each component goes through an individual Accessibility review during its development process. 

This document describes what a JET application is capable of rendering when it is used according to the documentation provided by Oracle, and when accessibility requirements in general are followed. For example, JET is capable of rendering the markup of alternative text for an image, but the application developer must supply text that is meaningful.

The responses to many of the technical standards are based on functionality provided by underlying technologies; please see the ACRs listed in the Dependent Products section for more information.

Report Date:

01-SEP-26

Contact Information:

accessible_ww@oracle.com

Notes:

This ACR does not cover the following product areas:

Documentation for accessibility can be found in the Oracle JET Developers Guide under chapter "Developing Accessible Applications"

Dependent Products


This product interacts with or is built with the other Oracle products listed in this section. Click below to view information about the accessibility of these dependent products. Products listed are the versions available at the time of publication of this document; newer documents may be available that supersede these versions.

Evaluation Methods Used:

Oracle's policy is to design, develop and test both products and documentation to be accessible. The recommended styles of testing for accessibility include: (i) algorithmic automated tests, (ii) human judgement tests such as tool-assisted tests, visual inspection and manual operation, and (iii) testing with assistive technology by people with and without disabilities. Additional information about Oracle's accessibility program is available on http://www.oracle.com/corporate/accessibility/

Accessibility Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guideline:

Standard/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.0Level A - Yes
Level AA - Yes
Level AAA - No
Web Content Accessibility Guidelines 2.1Level A - Yes
Level AA - Yes
Level AAA - No
Web Content Accessibility Guidelines 2.2Level A - Yes
Level AA - Yes
Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018Yes

Terms

The terms used in the Conformance Level information are defined as follows:

Supports
The functionality of the product has at least one method that meets the criteria without known defects or meets with equivalent facilitation.
Partially Supports
Some functionality of the product does not meet the criteria.
Does Not Support
Majority of functionality of the product does not meet the criteria.
Not Applicable
The criteria are not relevant to the product.

WCAG 2.2 Report

Table 1 also documents conformance with:

Note: When reporting on conformance with the WCAG 2.2 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria
Conformance Level
Remarks and Explanations
1.1.1 Non-text Content (Level A)Supports

The product and documentation were tested for:

  • 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

The Data Visualization components are SVG base and use the WAI-ARIA application role instead of HTML elements.

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 the HTML code.
  • SVG sub-elements that correspond to navigable data items within a component use of the WAI-ARIA img role.
  • The description of the structure of the component is provided via WAI-ARIA aria-label property in the HTML code.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.4 Captions (Live) (Level AA)Not ApplicableThe product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)Not ApplicableThe product has no multimedia.
1.3.1 Info and Relationships (Level A)Partially Supports

The product and documentation were 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
  • 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, ojTable, and Data Visualization components use the WAI-ARIA application role instead of the HTML table or other HTML elements.

In the case of the ojDataGrid and ojTable components:

The product was tested for:

  • Descriptive text about the content of the data grid is provided via WAI-ARIA aria-label property in the 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 the HTML code.
  • SVG sub-elements that correspond to navigable data items within a component use of the WAI-ARIA img role.
  • The description of the structure of the component is provided via WAI-ARIA aria-label property in the HTML code.

Exceptions:

  1. JET-78726: List View (oj-list-view) lacks programmatic header-to-cell relationships, preventing screen readers from conveying its table structure.
  2. JET-79316: Select Single (oj-select-single) fields in multiple dynamic forms repeat labels on focus.
  3. JET-80499: Input Search (oj-input-search) repeats its label three times before announcing the field role.
  4. JET-80814: Text Area (oj-c-text-area) does not announce maximum-length validation during continuous typing, leaving rejected input unclear.
1.3.2 Meaningful Sequence (Level A)Supports

The product and documentation were tested for:

  • The sequence of elements in the DOM matches a logical reading sequence.
1.3.3 Sensory Characteristics (Level A)Supports

The product and documentation were 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
1.3.4 Orientation (Level AA)Supports

The product and documentation were tested for

  • Text is displayed in both device orientations without loss of functionality or visibility of the text.
1.3.5 Identify Input Purpose (Level AA)Supports

The product and documentation were tested for

  • Text fields which collect information about the user contain the appropriate autocomplete content attribute.
1.4.1 Use of Color (Level A)Supports

The product and documentation were 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
1.4.2 Audio Control (Level A)Not ApplicableThe product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)Supports

The product and documentation were 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
1.4.4 Resize text (Level AA)Supports

The product and documentation were tested for:

  • Text can be resized up to 200% without loss of content or functionality.
1.4.5 Images of Text (Level AA)Supports

The product and documentation were tested for:

  • Images of text are not used
1.4.10 Reflow (Level AA)Supports

The product and documentation were tested for

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

 

 

1.4.11 Non-text Contrast (Level AA)Supports

The product and documentation were tested for:

  • Non-text items have a contrast ratio of at least 3:1.
1.4.12 Text Spacing (Level AA)Supports

The product and documentation were tested for:

  • When the following attributes and no others are modified there is no loss in functionality or content:
    • 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
1.4.13 Content on Hover or Focus (Level AA)Partially Supports

The product and documentation were 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.

Exceptions:

  1. JET-69059: The data tip implementation needs to meet Content on Hover or Focus (Level AA) in the core pack components.

 

2.1.1 Keyboard (Level A)Partially Supports

The product and documentation were 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)

Exceptions:

  1. JET-80398: Data Grid (oj-data-grid) prevents direct keyboard navigation from the first column header to the next column headers, breaking direct header navigation and forcing users to take a circuitous route through row content.
  2. JET-76443: Menu Button (oj-c-menu-button) cannot reopen a collapsed submenu, blocking access to its commands.
  3. JET-80041: Input Date Time (oj-input-date-time) lacks keyboard access to its calendar trigger.
2.1.2 No Keyboard Trap (Level A)Supports

The product and documentation were 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.
2.1.4 Character Key Shortcuts (Level A)Supports

The product and documentation were tested for

  • There are no single character keyboard shortcuts.
2.2.1 Timing Adjustable (Level A)Supports

The product and documentation were tested for:

  • Time limits are not used
2.2.2 Pause, Stop, Hide (Level A)Supports

The product and documentation were tested for:

  • There is no moving, blinking or scrolling content.
2.3.1 Three Flashes or Below Threshold (Level A)Supports

The product and documentation were tested for:

  • No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz
2.4.1 Bypass Blocks (Level A)Supports

The documentation was tested for:

  • A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page.
  • Structure and hierarchy are marked up with Header elements outside of repetitive navigation links
  • WAI-ARIA Landmark elements are used outside of repetitive navigation links

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

2.4.2 Page Titled (Level A)Supports

The documentation was tested for:

  • Pages have a meaningful title specified in the html "title" tag

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

2.4.3 Focus Order (Level A)Partially Supports

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

The product and documentation were tested for:

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

Exceptions:

  1. JET-55947: The select single dropdown (oj-select-single) does not keep screen reader focus inside the option list.
  2. JET-78458: The single-select (oj-c-select-single) control exposes unrelated content before the option list during screen reader navigation.
  3. JET-80260: List View (oj-list-view) moves focus unpredictably when columns move between Show and Hide sections, causing users to lose their place after each selection change.
  4. JET-80306: Drawer (oj-drawer-*) moves focus to the document body during navigation, causing users to lose their modal context.
2.4.4 Link Purpose (In Context) (Level A)Supports

The product and documentation were tested for:

  • The text of links and their surrounding paragraph, list, table cell (with marked up table headers) is sufficient to describe their purpose
2.4.5 Multiple Ways (Level AA)Supports

The documentation was tested for:

  • Page contains controls that enable reaching other pages of our product
  • Pages can be found using the provided "search" function

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

2.4.6 Headings and Labels (Level AA)Supports

The product and documentation were tested for:

  • Headers describe the topic or purpose of the content below them
  • Labels describe the purpose of the associated field.
2.4.7 Focus Visible (Level AA)Supports

The product and documentation were tested for:

  • Visual indication of the location of the focus.
2.4.11 Focus Not Obscured (Level AA)Supports

The product and documentation were tested for:

  • The initial position of user interface components receiving keyboard focus are not hidden entirely by author-created content.

 

2.5.1 Pointer Gestures (Level A)Supports

The product and documentation were tested for

  • There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)Supports

The product and documentation were tested for

  • When an operation uses a single pointer, the down-event of the pointer is not used to execute any part of the function.
2.5.3 Label in Name (Level A)Partially Supports

The product and documentation were 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.

Exceptions:

  1. JET-76456: N Box (oj-n-box) gives minimized cell buttons accessible names, causing the programmatic label to differ from the visible button text.
2.5.4 Motion Actuation (Level A)Supports

The product and documentation were tested for

  • There are no functions that require motion of the device.
2.5.7 Dragging Movements (Level AA)Supports

The product and documentation were tested for:

  • All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging.
2.5.8 Target Size (Minimum) (Level AA)Partially Supports

The product and documentation were tested for:

  • Interactive targets take up at least 24×24 CSS pixels of space, including white space around the target, and the space is not shared with another target.
  • The function can be achieved through a different control in the same software that meets this criterion.
  • The target is in a sentence, or its size is otherwise constrained by the line-height of non-target text.

Exceptions:

  1. JET-78550: The text-tag outline overlaps its label in a small scale and compact density in the select multiple (oj-c-select-multiple).
  2. JET-78868: Read-only form fields can report insufficient touch target size and spacing in the form layout (oj-form-layout).
  3. JET-79150: Input Text (oj-input-text) has undersized or closely spaced touch targets, making accurate activation difficult.
3.1.1 Language of Page (Level A)Supports

Framework does not provide complete web pages, however the individual components provided by the framework were tested to meet this guideline.

The product and documentation were tested for:

  • Properly set lang attribute for each page
3.1.2 Language of Parts (Level AA)Supports

The product and documentation were tested for:

  • Proper use of lang attribute for text passages that are in a different language than that of the page
3.2.1 On Focus (Level A)Supports

The product and documentation were 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.
3.2.2 On Input (Level A)Supports

The product and documentation were 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
3.2.3 Consistent Navigation (Level AA)Supports

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

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

3.2.4 Consistent Identification (Level AA)Supports

The product and documentation were tested for:

  • Images and controls are used and identified consistently throughout the product.
3.2.6 Consistent Help (Level A)Supports

The product and documentation were tested for: 

  • Help mechanisms (or a link to different software containing help mechanisms) occur in the same order relative to other software content.
3.3.1 Error Identification (Level A)Partially Supports

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

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

Exxceptions:

  1. JET-78652: Compact user-assistance popups are not visible on mobile devices in general for all form controls.
3.3.2 Labels or Instructions (Level A)Partially Supports

The product and documentation were tested for:

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

Exceptions:

  1. JET-78520: Table (oj-table) does not announce that rows are selectable and does not communicate the selected or unselected state after row activation, preventing screen-reader users from discovering the available action or confirming the result.
  2. JET-80041: Input Date Time (oj-input-date-time) does not provide visible or programmatic input instructions.
3.3.3 Error Suggestion (Level AA)Supports

The product was tested for:

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

The documentation was tested for:

  • The documentation does not have input fields, except for the Search field.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)Supports

The product was tested for:

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

The documentation was tested for:

  • The documentation does not require user input that modifies user controllable data.
3.3.7 Redundant Entry (Level A)Not Applicable

The product and documentation were tested for:

  • There are no occurrences of information that the user needs to enter which has been previously entered.
3.3.8 Accessible Authentication (Minimum) (Level AA)Not Applicable

The product and documentation were tested for:

  • Authentication is not required.
4.1.1 Parsing (Level A)Not ApplicableThis criterion is considered as always satisfied for any content using HTML or XML.
4.1.2 Name, Role, Value (Level A)Partially Supports

The product and documentation were 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

Exception:

  1. JET-75163: Table should have a role='grid' instead of role='application', which could help assistive technologies to recognize it as a table.
  2. JET-78286: A chart (oj-chart) exposes an undefined accessible label after re-rendering with more data.
  3. JET-78451: The sort icon is announced as an image rather than its intended control meaning in the table (oj-table).
  4. JET-78455: A screen reader can navigate to hidden live-region text in a single-select (oj-c-select-single) control.
  5. JET-78459: The multi-select combobox (oj-c-combobox-many) has screen reader interaction issues on a tablet.
  6. JET-78519: Screen reader focus moves to hidden content and repeats the number of matches found in the select single (oj-c-select-single).
  7. JET-80255: Select Multiple (oj-c-select-multiple) renders checkboxes as non-semantic spans, preventing assistive technologies from identifying or operating them.
4.1.3 Status Messages (Level AA)Partially Supports

The product and documentation were tested for:

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

Exceptions:

  1. JET-76518: The empty state announces "loaded" when no meaningful status update is needed in the list view (oj-c-list-view).
  2. JET-78453: The combobox components (oj-combobox-*) announce filter and item-count information even when no list of values is provided.
  3. JET-80861: List View (oj-list-view) repeats a previously announced empty-state message after focus has left the empty list and moved to later controls or sections, causing stale status information to interrupt and obscure the announcement of the user's current context.

 

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria
Conformance Level
Remarks and Explanations
302.1 Without VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of ColorNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without SpeechNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited ManipulationNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and StrengthNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning AbilitiesNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

Chapter 4: Hardware

These criteria are all Not Applicable because the product is not Hardware

Chapter 5: Software

Criteria
Conformance Level
Remarks and Explanations
501.1 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
502 Interoperability with Assistive TechnologyHeading cell - no response requiredHeading cell - no response required
502.2.1 User Control of Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility FeaturesPartially Supports

The product was tested for:

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

Exceptions:

  1. JET-78674: After selecting a menu button (oj-menu-button) item and navigating away, focus returns to the old menu button.
  2. JET-78292: Buttonset (oj-c-buttonset-*) does not allow voice-assistant users to activate its single-select buttons by name even when focus is on the intended option, blocking hands-free selection of the available choices.
  3. JET-81028: Menu Button (oj-c-menu-button) does not expose submenu items to screen-reader swipe navigation, leaving submenu commands inaccessible.
502.3 Accessibility ServicesHeading cell - no response requiredHeading cell - no response required
502.3.1 Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and HeadersNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.4 ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.6 Label RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.8 TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.10 List of ActionsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on ObjectsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.14 Event NotificationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
503 ApplicationsHeading cell - no response requiredHeading cell - no response required
503.2 User PreferencesSupports

The  product was tested for:

  • Responds to platform settings for color, contrast, font type, font size, and focus cursor
503.3 Alternative User InterfacesNot ApplicableThe product does not have assistive technology features.
503.4 User Controls for Captions and Audio DescriptionHeading cell - no response requiredHeading cell - no response required
503.4.1 Caption ControlsNot ApplicableThe product has no multimedia.
503.4.2 Audio Description ControlsNot ApplicableThe product has no multimedia.
504 Authoring ToolsHeading cell - no response requiredHeading cell - no response required
504.2 Content Creation or EditingNot ApplicableThe product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot ApplicableThe product is not an authoring tool.
504.2.2 PDF ExportNot ApplicableThe product is not an authoring tool.
504.3 PromptsNot ApplicableThe product is not an authoring tool.
504.4 TemplatesNot ApplicableThe product is not an authoring tool.

Chapter 6: Support Documentation and Services

Criteria
Conformance Level
Remarks and Explanations
602 Support DocumentationHeading cell - no response requiredHeading cell - no response required
602.2 Accessibility and Compatibility FeaturesSupports

The product documentation describes:

  • special keystrokes needed to operate controls
  • workarounds

Accessibility-related documentation can be found at: Develop Accessible Oracle JET Apps.

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

602.3 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support DocumentationNot Applicable

Product documentation is in electronic format.

603 Support ServicesHeading cell - no response requiredHeading cell - no response required
603.2 Information on Accessibility and Compatibility FeaturesSupports

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/tech/developers/categories/16409-oracle-jet

603.3 Accommodation of Communication NeedsSupports

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/tech/developers/categories/16409-oracle-jet

Oracle Legal Disclaimer

The information above describes this product's ability to support the applicable Standards/Guidelines, subject to Oracle's interpretation of those standards (available at https://www.oracle.com/corporate/accessibility/policy.html#standards-tab) and the remarks in this document. For more information regarding the accessibility status of this product or other Oracle products, see http://www.oracle.com/corporate/accessibility or contact: accessible_ww@oracle.com.

This document is provided for information purposes only and the contents hereof are subject to change without notice. Oracle Corporation does not warrant that this document is error free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Oracle Corporation specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Oracle further makes no representation concerning the ability of assistive technologies or other products to interoperate with Oracle products. This document addresses the named product(s) only and not prerequisite products for which Oracle supplies restricted use licenses.