Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Cloud Infrastructure (OCI) Data Labeling April 2022

Product Description:

The OCI Data Labeling service (DLS) is an OCI native service that allows customers to create and browse datasets, view data records (text, images) and apply labels for the purposes of building AI/ML models. The service also provides interactive user interfaces designed to aide in the labeling process. Once records are labeled, the dataset can be exported as line-delimited JSON for use in machine learning model development. The OCI Data Labeling service will provide a platform for customers to assemble data into data sets, grant access to labelers, provide interactive UIs and instructions to labelers, store data labels and collate this labeled data which can then be used to build custom AI/ML models

Date:

29-Jun-2022

Contact Information:

accessible_ww@oracle.com

Notes:

This ACR does not cover APIs nor backend services

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

The following tickets track the identified errors in DLS Jira:

DLS-3282

For different screens and components listed below, there is a missing label for control:

  • Apply tag filter
  • Create dataset - Add files and labels (2 errors) - textbox, choose files
  • Dataset details (Dataset information tab)  - textarea
  • Dataset details (Labels tab) - edit icon
  • Edit dataset - choose files
  • Workrequest details - textarea

DLS-3382

Alternative text for following SVG images is missing:

  • Overview page - Watch Service video icon
  • Dataset details page - Labels tab - Edit icon
  • Dataset details page - Tags tab - Edit icon
  • Labeling screen - zoom in/out icon, redo icon, instructions icon, adjust image icon, move icon, carousel minimize/maximize icon, tools minimize/maximize icon
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 was tested for:

  • User interface component labels are associated with the fields they are labelling
  • Headings are encoded with HTML heading tags
  • List markup is used for marking up lists
  • Groups of components are marked up with their description
  • 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

The following tickets track the identified errors in DLS Jira:

DLS-3280

For different screens listed below, the tables present don't have accessible text:

  • List datasets
  • Dataset details
  • Workrequest list
  • Workrequest details

DLS-3284

On the labeling screen, lists are not structured correctly for carousel.

DLS-3314

On the overview page, the headers are incorrectly used for links like Image Labeling, Document Labeling and Text Labeling.

DLS-3809

With screen readers enabled, whenever the focus comes to rows in tables present on list datasets and dataset details page, screen readers announce row id (which is a hidden field). Row id is the programatic row identifier which has no meaning for the user.

1.3.2 Meaningful Sequence(Level A)Partially Supports

The product was tested for:

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

The following tickets track the identified errors in DLS Jira:

DLS-3268

On the labeling screen, when we try to navigate using tab key, after the toolbar, focus goes to carousel and then comes to Tools, Adjust image, Labels. The order is not maintained as the DOM contains Carousel before the draggable panels.

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 :

  • A fixed display orientation is required for essential functionality.
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 ApplicableThe product has no multimedia.
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
  • Other text and images of text have a contrast ratio of at least 4.5:1

The following tickets track the identified errors in DLS Jira:

DLS-3281

For different screens and components listed below, there is an issue with contrast between foreground and background colors. The contrast ratio should be at least 4.5:1.

  • List datasets - "no tag filters applied"
  • View tags (2 errors) - "Oracle Tags"
  • Create dataset - Add files and labels (2 errors) - "Select a bucket, Select..."
  • Dataset details (Tags tab) (2 errors) - "Oracle Tags"
  • Add labels dialog - "Enter label name"
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
1.4.10 Reflow (Level AA)Partially Supports

The product was tested for :

  • Content that requires two-dimensional layout only presents scroll bars in the component used
    to present the two-dimensional content.

The following tickets track the identified errors in DLS Jira:

DLS-3285

For the labeling screen, functionality becomes unusable if the zoom level is 400%. 

1.4.11 Non-text Contrast (Level AA)Supports

The product was tested for:

  • Non-text items have a contrast ratio of at least 3:1
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.
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
  • The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms)

The following tickets track the identified errors in DLS Jira:

DLS-3266

On the labeling screen, toolbar buttons - Move, zoom in/out, etc don't respond to "Enter" key.

Carousel images don't respond to "Enter" key

Toolbar buttons and Carousel images, receive the focus using tab key but intended operations do not take place once "Enter" key is pressed. 

DLS-3277

For the Labels set field (Step 2 of create dataset flow) and Add labels dialog on dataset details screen and labeling screen, labels can't be deleted with "enter" key when "X" icon is highlighted.

Workaround - Selected values can be cleared by hitting the delete/backspace key. 

DLS-3320

When screen reader is enabled, while creating the dataset, the bucket can't be selected in step no 2 (Add files and labels). Screen reader treats the field as text and list of buckets don't show up.

DLS-3810

While screen reader is enabled, navigation doesn't work for below mentioned links by hitting "Enter" key on keyboard:

  • Left side links (Overview, Datasets, Work requests) on dataset details, overview and workrequest list page
  • Breadcrumbs on Dataset detail, labeling screen and workrequest details
  • Links within tables - Dataset names in list datasets table, record names in data records table on dataset details page and workrequest names in list workrequests table
  • Record names within grid in Gallery view
  • Left side links on dataset details page (Data records and Gallery view)
  • Left side links on work request details page (Error logs and error messages)
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 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

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
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)Partially Supports

The product was tested for:

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

The following ticket tracks the identified error in DLS Jira:

DLS-3263

For the create dataset flow, while navigating the workflow steps on the left, inactive steps dont' get focus in forward direction.

DLS-3264

On the dataset details screen, while navigating using keyboard, focus gets lost after "More Actions" button. After pressing tab 3 times, it becomes visible

DLS-3267

On the labeling screen, while traversing using tab key, carousel header, "Records (1 of 10 labelled)" also receives focus which is not desirable as this text is not actionable.

DLS-3268

On the labeling screen, when we try to navigate using tab key, after the toolbar, focus goes to carousel and then comes to Tools, Adjust image, Labels.

The order is not maintained as the DOM contains Carousel before the draggable panels.

DLS-3270

On the labeling screen, using tab key if we try to select labels for single/multiple label type datasets, as soon as selection is made, the focus goes to first element on the page.

DLS-3276

On the labeling screen, for Object Detection type datasets, inside the Tools panel, focus is not coming on the actionable items - Bounding box and remove box.

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

The product was tested for:

  • Pages can be found using the provided "search" function
  • Pages are in a site table of contents
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)Partially Supports

The product was tested for:

  • Visual indication of the location of the focus

The following ticket tracks the identified error in DLS Jira:

DLS-3269

On the labeling screen, while trying to navigate the adjust image panel using tab key, the controls receive focus but the border is missing. As a result visual representation is missing. If we press up/down arrow, the value changes indicating the focus.

2.5.1 Pointer Gestures (Level A)Supports

The product was tested for:

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

The product was tested for:

  • There are no single pointer operations
2.5.3 Label in Name (Level A)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.
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)Supports

The product was tested for:

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

The product was tested for:

  • No text passages 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
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)Partially Supports

The product was tested for:

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

The following ticket tracks the identified error in DLS Jira:

DLS-3282

For different screens and components listed below, there is a missing label for the form control:

  • Apply tag filter
  • Create dataset - Add files and labels (2 errors) - textbox, choose files
  • Dataset details (Dataset information tab)  - textarea
  • Dataset details (Labels tab) - edit icon
  • Edit dataset - choose files
  • Workrequest details - textarea
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:

  • Data can be reviewed, corrected, and confirmed by the user before they are finalized
4.1.1 Parsing(Level A)Partially 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

The following tickets track the identified errors in DLS Jira:

DLS-3279

For different screens and components listed below, the landmarks are not unique:

  • Overview screen
  • List datasets (2 errors) - aside, nav
  • Dataset details (Dataset information tab) (2 errors) - aside, nav
  • Dataset details (Labels tab) (2 errors) - aside, ul
  • Workrequest list (2 errors) - aside, nav
  • Workrequest details (2 errors) - aside, nav

DLS-3283

In Create dataset flow Step No 1 --> Add dataset details --> Tags fieldset, the ids for fields are not unique

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.
  • 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 following tickets track the identified errors in DLS Jira:

DLS-3316

For the list datasets, dataset details and work request list screens where we have tables, screen reader is not announcing number of results in table.

DLS-3317

For the following fields, screen reader is not announcing labels:

  • List datasets - Compartment field
  • Create dataset - Add dataset details - Dataset format field and Annotation class
  • Create dataset - Add files and labels - Local upload - Name of the file to be deleted
  • Create dataset - Add files and labels - Selected files field
  • Dataset details - Labels tab - Edit icon

DLS-3369

On the labeling screen, screen reader is not announcing the canvas. For images and documents, the screen reader does not read out the record name for single/multiple label text type datasets.

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

The following tickets track the identified errors in DLS Jira:

DLS-3318

For List datasets screen, screen reader starts announcing the status like active, needs attention, labeled, unlabeled, etc in random. This is not done against a particular table row entry. Only the status names on the page are announced as soon as user lands on the screen.

DLS-3321

The screen reader is not reading the status when the datataset is in "needs attention" state.

DLS-3322

When the records are being generated or the dataset is being exported (Updating state), screen reader doesn't announce the progress of the operation on the dataset details screen. 

DLS-3323

For the operations which take time like Add labels, delete, loading icon is visible on screen for a long time. Screen readers must announce the ongoing operation like "Creating labels", Deleting labels", etc. Below are some of the operations:

  • Add labels
  • Delete labels
  • Delete tags
  • Add tags
  • Delete dataset
  • Edit labels

DLS-3324

On the dataset details screen, once the delete tag operation completes, screen reader is not able to announce the same.

DLS-3808

Screen readers are not announcing toast notifications on the dataset details page.

back to top

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.

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 FeaturesNot ApplicableThe product is designed to be isolated from the underlying platform.
 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 ApplicableThe product is designed to be isolated from the underlying platform.
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 Applicable

There are no accessibility or compatibility features to document. Product uses standard HTML specifications to support accessibility

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.