Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Data Integrator 12.2.1.4

Product Description:

Oracle Data Integrator (ODI)

This VPAT covers Oracle Data Integrator (ODI Studio and ODI Console) and includes the following Data Integrator components:

  • Application Adapters for Data Integration. This is a separately licensed option required to use the Applications connectors for E-Business Suite, Siebel, JD Edwards Enterprise One, JD Edwards World, Peoplesoft, SAP Enterprise Resource Planning (ERP) and SAP Business Warehouse (BW)

The following Oracle Data Integrator components have no user interface:

  • Application Adapters for Data Integration

Date:

26-Mar-2019

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:
  • ODI Studio Expression editor - The alternative method to the expression editor is to directly enter expressions in SQL syntax without the use of a graphical editor.

Note: When running the Microsoft Windows Operating System, please enable the Java Access Bridge by following the Java Accessibility Guide: http://docs.oracle.com/javase/7/docs/technotes/guides/access/index.html.

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/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.0, at https://www.w3.org/TR/2008/REC-WCAG20-20081211/Level A - Yes
Level AA - Yes
Level AAA - No
Section 508 as published in 2017, at https://www.Section508.govYes

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.
Supports with Exceptions
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.0 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.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Table 1: WCAG Conformance Criteria

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

Console:

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

Studio:

The product was tested for:

  • Images that convey information are embedded within standard user interface components and have a meaningful AccessibleName and/or AccessibleDescription
  • Images that are decorative are embedded within standard user interface components and have neither an AccessibleName nor an AccessibleDescription
  • Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table), or the containers of the complex images are filled with simple image children whose information is exposed via AccessibleName and/or AccessibleDescription
  • Data tables include a summary or caption, programmatically connected with the table as the AccessibleTable's AccessibleSummary
  • Controls have an AccessibleName, or a label control with an AccessibleName has been programmatically associated with it
  • 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

Studio accessibility bugs:

  • 23106993 - Label of multi line box is not read using screen reader assistive technology in Big Data Configuration wizard. This impacts the Topology Navigator.
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)Supports with Exceptions

Console:

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

Console accessibility bugs:

  • 21175897 - Column Header cell is empty for Scenario list

Studio:

The product was tested for:

  • User interface component labels are associated with the fields they are labeling via the LabelFor and LabeledBy relations
  • Headings are marked as such with a Group relation from the header to the items beneath the header
  • Groups of components are marked as such, with a Group relation from the header of the group to the members of the group
  • Style sheets are used only to change the layout and presentation on the screen
  • Lists are contained within a List component
  • Tables are contained within a Table component, implement the AccessibleTable interface, provide an AccessibleSummary, and contain include row and column headers where appropriate

Studio accessibility bugs:

  • 23068404 - Tables don't have AccessibleSummary set
  • 23106993 - Label of multi line box is not read using screen reader assistive technology in Big Data Configuration wizard. This impacts the Topology Navigator.
1.3.2 Meaningful Sequence(Level A)Supports

Console:

The product was tested for:

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

Studio:

The product was tested for:

  • The accessibility hierarchy is logical
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 included a reference to the text alternative of the graphic
1.4.1 Use of Color(Level A)Supports with Exceptions

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

Studio accessibility bugs:

  • 23068578 - Some uneditable text Contrast smaller than 3:1. This impacts the Dimension, Cube and Load Plan functionality
1.4.2 Audio Control(Level A)Not ApplicableThe product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)Supports with Exceptions

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

Studio accessibility bugs:

  • 23068578 - Some uneditable text Contrast smaller than 3:1. This impacts the Dimension, Cube and Load Plan functionality
1.4.4 Resize text(Level AA)Supports

The product was 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 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
2.1.1 Keyboard(Level A)Supports with Exceptions

Studio:

The product was tested for:

  • ability to perform functions from the keyboard only
  • logical movement of focus through the controls
  • proper operation of unique keystrokes, including those listed in the product documentation

Console:

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)

Studio accessibility bugs:

  • 9390337 - Unable to add or remove steps and define the sequence of Steps within a Package diagram in ODI Studio. This can be achieved using the ODI Java API. 
  • 9407307 - Removing markers on objects from the tree views in ODI Studio. All markers are impacted, this can be achieved using the object editor instead.
  • 16003425 - There is no keyboard only way to create join or lookup inside a dataset. Workaround exists by not using dataset in mappings. 
  • 16015331 - Cannot Find a Way to Edit the View Inside Thumbnail by keyboard
  • 22948710 - Cannot control scrollbar by keyboard in the navigator

Console accessibility bugs:

  • 21324735 - ODI User Page shows hidden information while using screen reader assistive technology.
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.2.1 Timing Adjustable(Level A)Supports

The product was tested for :

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

Console:

The product 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 is marked up with Header elements outside of repetitive navigation links
  • WAI-ARIA Landmark elements are used outside of repetitive navigation links
Studio:   The product was tested for :
  • Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline does not apply.
2.4.2 Page Titled(Level A)Supports

Console:

The product was tested for:

  • Pages have a meaningful title specified in the TITLE element

Studio:

The product was tested for:

  • The name of the software application is meaningful.
2.4.3 Focus Order(Level A)Supports

Console:

The product was tested for:

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

Studio:

The product was tested for:

2.4.4 Link Purpose (In Context)(Level A)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
2.4.5 Multiple Ways(Level AA)Supports

Console:

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
Studio:   The product was tested for :
  • Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline does not apply.
2.4.6 Headings and Labels(Level AA)Supports with Exceptions

The product was tested for:

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

Console accessibility bugs:

  • 23106993 - Label of multi line box is not read using screen reader assistive technology in Big Data Configuration wizard. This impacts the Topology Navigator.
2.4.7 Focus Visible(Level AA)Supports

The product was tested for:

  • Visual indication of the location of the focus
3.1.1 Language of Page(Level A)Supports

Console:

The product was tested for:

  • Properly set lang attribute for each page

Studio:

The product was tested for:

  • Properly set locale/language
3.1.2 Language of Parts(Level AA)Supports

Console:

The product was tested for:

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

Studio:

The product was tested for:

  • Properly set locale/language for text passages that are in a different language than that of the software
3.2.1 On Focus(Level A)Supports

Console:

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

Studio:

The product was tested for:

  • When an element receives focus, it does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window
3.2.2 On Input(Level A)Supports

Console:

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

Studio:

The product was tested for:

  • Changes in the value of user interface components does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window
3.2.3 Consistent Navigation(Level AA)Supports with Exceptions

Console:

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
  • There are no navigational mechanisms that are repeated

Console accessibility bugs:

  • 23081259 - No keyboard option for Expand and collapse of Nodes

Studio:

The product was tested for:

  • Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline does not apply.
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 with Exceptions

The product was tested for:

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

Studio accessibility bugs:

  • 23106993 - Label of multi line box is not read using screen reader assistive technology in Big Data Configuration wizard. This impacts the Topology Navigator.
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

Console:

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

Studio:

The product was tested for:

  • Markup elements have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique Ids
  • Markup content validate to the appropriate markup specification(s)
4.1.2 Name, Role, Value (Level A)Supports with Exceptions

Console:

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 programatically exposed name
  • Frames have a meaningful title specified in the title attribute

Studio:

The product was tested for:
  • User interface components have a programmatically associated AccessibleName and AccessibleRole as defined by the Java Accessibility API
  • State information, properties, and values are programmatically exposed for user interface components
  • Event notification of changes to names, states, properties, and values is available to assistive technologies

Studio accessibility bugs:

  • 23068237 - Some Objects don't have Accessible Name. This impacts the following areas: combo box in datastore component, combo box in dimension component, Memo text in dimension, Memo text in Project, push button for JDBC driver selection, push button in dimension datastore selection, search box in dimension datastore selection, search box in Load Plan Scenario selection, sort button in dimension datastore selection, sort button in Load Plan Scenario selection, Attributes table in datastore component, Attributes table in dimension component, search box in dimension levels table, search box in Load Plan Steps table, textual fields in datastore component, textual fields in dimension component.
  • 23106993 - Label of multi line box is not read using screen reader assistive technology in Big Data Configuration wizard. This impacts the Topology Navigator.

back to top

2017 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.

back to top

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 FeaturesSupports

Product was tested for:

  • Software does not disrupt platform features that are defined in the platform documentation as accessibility features.
 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 PreferencesNot Supported

Bug 28679580 - Product does not permit user preferences.

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.

back to top

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 FeaturesNot Supported

Bug# 28282871 - Product does not have Accessibility Features documentation.

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 FeaturesSupportsOracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication NeedsSupportsOracle 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.

back to top

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.