Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Integration Cloud 21

Product Description:

Oracle Integration is an enterprise connectivity and automation platform for quickly modernizing applications, business processes, APIs, and data. Developers and cloud architects can connect SaaS and on-premises applications faster with a visual development experience, prebuilt integrations, and embedded best practices. Oracle Integration gives you native access to events in Oracle Cloud ERP, HCM, and CX. Connect app-specific analytic silos to simplify requisition-to-receipt, recruit-to-pay, lead-to-invoice, and other critical processes. Finally, give your IT and business leaders end-to-end visibility.

Product Documentation: https://docs.oracle.com/en/cloud/paas/integration-cloud/index.html

Date:

22-Dec-2021

Contact Information:

accessible_ww@oracle.com

Notes:

This ACR does not cover the following areas:

Visual Builder
Integration Insight
Process
File Server
B2B

Note that the above integration features are not offered today in US Gov cloud regions and as such are limited to commercial regions only.

Dependent Products

This product interacts with or is built with the other Oracle products listedin this section. Click below to view information about the accessibility ofthese dependent products. Products listed are the versions available at thetime of publication of this document; newer documents may be available that supersedethese 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/index.html

Accessibility Standards/Guidelines

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

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

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.1 Report

Table 1 also documents conformance with:

Section 508: Chapter 5 - 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 - 602.3 Electronic Support Documentation

Note: When reporting on conformance with the WCAG 2.1 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 was 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 Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table) Titles for Objects and Applets are provided Controls have an associated name Text summary or alternative is provided for time-based media Client-side image maps specify the ALT attribute on each AREA element. CAPTCHAs are not used
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Not Applicable
1.2.2 Captions (Prerecorded) (Level A)	Not Applicable
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Not Applicable
1.2.4 Captions (Live) (Level AA)	Not Applicable
1.2.5 Audio Description (Prerecorded) (Level AA)	Not Applicable
1.3.1 Info and Relationships (Level A)	Supports	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 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
1.3.2 Meaningful Sequence(Level A)	Supports	The product was tested for: The sequence of elements in the DOM matches a logical reading sequence
1.3.3 Sensory Characteristics(Level A)	Supports	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 include a reference to the text alternative of the graphic
1.3.4 Orientation (Level AA)	Supports	The product was 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 was 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 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
1.4.2 Audio Control(Level A)	Not Applicable
1.4.3 Contrast (Minimum) (Level AA)	Partially Supports	The product 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 Exception - BUG 33681248 - The recipe button in the Accelerators & Recipes screen has a contrast ratio of 3.85:1.
1.4.4 Resize text(Level AA)	Partially Supports	The product was tested for: Text can be resized up to 200% without loss of content or functionality Exception - Bug 33681921 While editing Integrations, when the browser zoom is 200%, action dialogs 'for each' and 'stage file' fields are not fully visible.
1.4.5 Images of Text(Level AA)	Supports	The product was tested for Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential
1.4.10 Reflow (Level AA)	Partially Supports	The product was tested for Text information reflows so that only one direction of scrolling is required while at 400% zoom. Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content. Exception Bug 33681251 - at 400%, the screen does not reflow.
1.4.11 Non-text Contrast (Level AA)	Partially Supports	The product was tested for: Non-text items have a contrast ratio of at least 3:1 Exception BUG 33681248 - The contrast ratio is 1.66:1 for the informational notification and integration-recipe icons in the Home and Integrations screens.
1.4.12 Text Spacing (Level AA)	Supports	The product was 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)	Supports	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. Information appears on hover or focus using default browser behavior, such as the title attribute of components.
2.1.1 Keyboard(Level A)	Partially Supports	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) Exception Bug 33685628 - in designtime popup screens, the default focus is missing. However, with OS keyboard aids, the user can enable the focus to any field. Once the focus has been set, all fields are available via the tab key.
2.1.2 No Keyboard Trap (Level A)	Supports	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
2.1.4 Character Key Shortcuts (Level A)	Supports	The product was tested for There are no single character keyboard shortcuts.
2.2.1 Timing Adjustable(Level A)	Supports	The product was tested for Time limits in the product can be extended with at least 10 seconds warning
2.2.2 Pause, Stop, Hide (Level A)	Supports	The product was tested for There is no moving, blinking or scrolling content
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	The product was 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 product was tested for A ‘HOME’ link is provided to skip repetitive navigation links at the top of the page. The shortcut "Go to Integrations" link can be accessed by the OS keyboard aids.
2.4.2 Page Titled(Level A)	Supports	The product was tested for: Pages have a meaningful title specified in the TITLE element
2.4.3 Focus Order(Level A)	Supports	The product was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence
2.4.4 Link Purpose (In Context)(Level A)	Partially Supports	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 Exception - Bug 33681884 - the navigation pane arrow icon does not have link text. However, the user can navigate to the Home screen icon which has link text and navigate to the appropriate screen.
2.4.5 Multiple Ways(Level AA)	Supports	The product was tested for Pages are contained in a "site map" 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 Page contains controls that enable reaching all pages
2.4.6 Headings and Labels(Level AA)	Supports	The product was 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 was tested for: Visual indication of the location of the focus
2.5.1 Pointer Gestures (Level A)	Supports	The product was tested for Multipoint or path-based gesture actions can be completed using a different input modality. In the Integration > Edit screen, multipoint gestures can be completed with mouse, keyboard, or touchscreen. The source/target can be selected with keyboard, and the shuttle button will allow the user to move the element.
2.5.2 Pointer Cancellation (Level A)	Supports	The product was 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 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 When an operation uses a single pointer, the up-event reverses any outcome of the preceding down-event
2.5.3 Label in Name (Level A)	Partially Supports	The product has been 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. Exception - Bug 33681905 In some screens, table rows have a hidden checkbox with no label that should be ignored. In the Monitoring > Errors screen, the checkboxes are visible with no label, and the user can use the parent element to identify the row.
2.5.4 Motion Actuation (Level A)	Supports	The product was tested for There are no functions that require motion of the device.
3.1.1 Language of Page(Level A)	Partially Supports	The product was tested for: Properly set lang attribute for each page Exception Bug 33681908 - lang attribute is not set in the Home, Integrations, and Accelerators & Recipes screens.
3.1.2 Language of Parts(Level AA)	Supports	The product was 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 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
3.2.2 On Input(Level A)	Supports	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 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 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
3.2.4 Consistent Identification(Level AA)	Supports	The product was tested for: Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification(Level A)	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
3.3.2 Labels or Instructions (Level A)	Supports	The product was tested for: Labels or instructions are provided when the product requires user input
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
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)	Supports	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
4.1.1 Parsing(Level A)	Supports	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
4.1.2 Name, Role, Value (Level A)	Partially Supports	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 Frames have a meaningful title specified in the title attribute Exceptions Bug 33681916 - The following controls do not have a programmatically associated name HOME > INTEGRATIONS > Integrations > Create integration (Description textbox), Edit (Sources and Target sections), Add schedule (Frequency and Time Zone fields), and Schedule and future runs (Future Runs table) HOME > INTEGRATIONS > Connections > Details (Description textbox) HOME > INTEGRATIONS > Lookups > Create lookup (Description textbox) and Lookup configuration (Lookups table) HOME > INTEGRATIONS > Packages > Configuration editor (Resources table) HOME > INTEGRATIONS > Agents > Create agent group (Description textbox) HOME > INTEGRATIONS > Libraries > Create Library (Description textbox)
4.1.3 Status Messages (Level AA)	Partially Supports	The product was tested for Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus. Exception - Bug 33681919 Banner messages are not announced by screen readers. However, the screen reader will report that the action has been completed.

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria	Conformance Level	Remarks and Explanations
302.1 Without Vision	Not Applicable
302.2 With Limited Vision	Not Applicable
302.3 Without Perception of Color	Not Applicable
302.4 Without Hearing	Not Applicable
302.5 With Limited Hearing	Not Applicable
302.6 Without Speech	Not Applicable
302.7 With Limited Manipulation	Not Applicable
302.8 With Limited Reach and Strength	Not Applicable
302.9 With Limited Language, Cognitive, and Learning Abilities	Not Applicable

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 AA	Supports	See the responses in the WCAG 2.0 section of this report.
502 Interoperability with Assistive Technology	Heading cell - no response required	Heading cell - no response required
502.2.1 User Control of Accessibility Features	Not Applicable
502.2.2 No Disruption of Accessibility Features	Not Applicable
502.3 Accessibility Services	Heading cell - no response required	Heading cell - no response required
502.3.1 Object Information	Not Applicable
502.3.2 Modification of Object Information	Not Applicable
502.3.3 Row, Column, and Headers	Not Applicable
502.3.4 Values	Not Applicable
502.3.5 Modification of Values	Not Applicable
502.3.6 Label Relationships	Not Applicable
502.3.7 Hierarchical Relationships	Not Applicable
502.3.8 Text	Not Applicable
502.3.9 Modification of Text	Not Applicable
502.3.10 List of Actions	Not Applicable
502.3.11 Actions on Objects	Not Applicable
502.3.12 Focus Cursor	Not Applicable
502.3.13 Modification of Focus Cursor	Not Applicable
502.3.14 Event Notification	Not Applicable
502.4 Platform Accessibility Features	Not Applicable
503 Applications	Heading cell - no response required	Heading cell - no response required
503.2 User Preferences	Not Applicable
503.3 Alternative User Interfaces	Not Applicable
503.4 User Controls for Captions and Audio Description	Heading cell - no response required	Heading cell - no response required
503.4.1 Caption Controls	Not Applicable
503.4.2 Audio Description Controls	Not Applicable
504 Authoring Tools	Heading cell - no response required	Heading cell - no response required
504.2 Content Creation or Editing	Not Applicable
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable
504.2.2 PDF Export	Not Applicable
504.3 Prompts	Not Applicable
504.4 Templates	Not Applicable

Chapter 6: Support Documentation and Services

Criteria	Conformance Level	Remarks and Explanations
602 Support Documentation	Heading cell - no response required	Heading cell - no response required
602.2 Accessibility and Compatibility Features	Supports	The product documentation describes: Setting accessibility preferences Accessibility-related documentation to set accessibility preferences can be found at: https://docs.oracle.com/en/cloud/accessibility/oracle-integration-cloud-service-accessibility.html#GUID-33CB85A8-B690-4333-AB1C-84B02FB1E8E6
602.3 Scope - Incorporation of WCAG 2.0 AA	Supports	See the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support Documentation	Supports	Product documentation is in electronic format.
603 Support Services	Heading cell - no response required	Heading cell - no response required
603.2 Information on Accessibility and Compatibility Features	Supports	Oracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication Needs	Supports	Oracle customers have access to electronic support through My Oracle Support or by calling Oracle Support at 1.800.223.1711. Hearing-impaired customers in the U.S. who wish to speak to an Oracle Support representative may use a telecommunications relay service (TRS). Information about the TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of telephone numbers is available at https://www.fcc.gov/general/telecommunications-relay-services-directory. International hearing-impaired customers should use the TRS at +1.605.224.1837. An Oracle Support engineer will respond to technical issues according to the standard service request process.

Oracle Legal Disclaimer

The information above describes this product's ability to support the applicableStandards/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.