Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Endeca Commerce 11.3.2 (Updated)

Product Description:

Oracle Endeca Commerce is a collection of applications for managing websites and the experiences of website visitors. The product provides capabilities for faceted search, guided navigation, merchandising, and content spotlighting. It includes a tool that enables the rapid creation of dynamic data-driven web pages. Customers can use Oracle Endeca Commerce to create landing pages for a particular search term or navigation state. Custom templates allow customers to arrange page areas and display content conditionally. The ability to organize and combine content in a modular fashion allows a wide degree of flexibility in crafting pages while maintaining a consistent look-and-feel across an entire site.

Oracle Endeca Commerce consists of the following components:

  • Oracle Commerce Advanced JDBC Column Handler
  • Oracle Commerce Content Acquisition System
  • Oracle Commerce Developer Studio
  • Oracle Commerce Document Conversion
  • Oracle Commerce MDEX Engine
  • Oracle Commerce Tools and Frameworks
  • Oracle Commerce Guided Search
  • Oracle Commerce Platform Services 

This product includes the following user interfaces:

  • Workbench and Experience Manager. These user interfaces (UIs) use a combination of technologies, including Oracle JET, other HTML5-based technologies, and JSP
  • Developer Studio: a legacy Microsoft Foundation Classes (MFC)-based application, most of whose functionality has been re-implemented in Workbench  
  • Java-based installers
  • A legacy reference website, Discover Electronics, that illustrates how a customer who uses Oracle Endeca Commerce in a standalone manner - that is, without an integration with Oracle ATG Web Commerce - could use the product to build a website

The Experience Manager user interface allows a business user to upload and store media, including video content, intended for display on the customer's website. The product provides a video player that the business user can use to preview an uploaded video within an editor. The product does not include its own prerecorded audio or video content, except for a short sample video that demonstrates that the editor's video player supports the use of a caption file.

Date:

02-Oct-2019

Contact Information:

accessible_ww@oracle.com

Notes:

The following UIs, described above, are excluded from this VPAT:

  • Developer Studio
  • Java-based installers 
  • Discover Electronics

In addition, this VPAT does not cover how content is rendered or otherwise presented on the customer's website, because the product does not define or control this. The one exception is that the product provides a rich text editor that allows the customer to create rich text to be displayed on their website. This VPAT does cover the rich text created by that editor.

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

The product was tested for:

  • Images that convey information have meaningful alternative text using the ALT attribute
  • 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)
  • Pages, pop ups, modals, and applets have meaningful and unique titles
  • Controls have an associated name
  • Non-text characters are not used or have meaningful alternative text
  • CAPTCHAs are not used
  • The video player in the product's media editor supports the use of caption files
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Not Applicable

There is no pre-recorded audio-only or video-only content.

1.2.2 Captions (Prerecorded) (Level A)Supports

The product was tested for:

  • A business user who uploads a video intended for display on a website can also upload a caption file and associate it with the video. When the business user previews the video in the product's media editor and turns on captioning, the caption file supplies the captions.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Partially Supports

The product was tested for:

  • The product documentation advises customers to ensure that the soundtrack of any uploaded video is sufficiently descriptive of the visible content to communicate its meaning fully to a user who is visually impaired.
  • The product documentation advises customers to supply a text file containing an alternate description of any uploaded video.

Exceptions:

  • The video player provided in the media editor needs to support the use of an audio description as well as controls that allow the user to select an audio description. (30148086)
1.2.4 Captions (Live) (Level AA)Not Applicable

The product does not provide or support live media.

1.2.5 Audio Description (Prerecorded) (Level AA)Partially Supports

The product was tested for:

  • The product documentation advises customers to ensure that the soundtrack of any uploaded video is sufficiently descriptive of the visible content to communicate its meaning fully to an end user who is visually impaired.

Exceptions:

  • The video player provided in the media editor needs to support the use of an audio description as well as controls that allow the user to select an audio description. (30148086)
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 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
  • Sections of content have meaningful headers, and their structure and hierarchy are meaningful
  • Groups of components are marked up with their description
  • Style sheets are used only to change the layout and presentation on the screen

Exceptions:

  • In Experience Manager Rule List views, a screen reader does not read the column names, nor indicate that the columns are sortable. (25338972)
  • In the product documentation, the row headers on tables need to be more meaningful. (26934986)
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)Not SupportedThis product has not yet been evaluated for this criteria
1.3.5 Identify Input Purpose (Level AA)Not SupportedThis product has not yet been evaluated for this criteria
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 - i.e., no information is conveyed by color alone
  • Information conveyed by color has a contrast ratio of at least 3:1
1.4.2 Audio Control(Level A)Not Applicable

The product does not include automatically playing audio.

1.4.3 Contrast (Minimum) (Level AA)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
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)Not SupportedThis product has not yet been evaluated for this criteria
1.4.11 Non-text Contrast (Level AA)Not SupportedThis product has not yet been evaluated for this criteria
1.4.12 Text Spacing (Level AA)Not SupportedThis product has not yet been evaluated for this criteria
1.4.13 Content on Hover or Focus (Level AA)Not SupportedThis product has not yet been evaluated for this criteria
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)

Exceptions:

  • In Experience Manager, to close the Project popover using the Esc key, the user must first use Tab or Shift-Tab to move focus to one of the fields at the top of the popover. (30048931)
  • When focus is on a menu option reached from the Workbench toolbar, the Esc key does not close the menu; the keyboard user must tab through the options to exit the menu. (29445718)
  • In Experience Manager, in the Project popover, a Chrome user who uses the keyboard to move focus to a project must sometimes press Enter twice to enter the project. (29290272)
  • In Experience Manager, in the List views, a keyboard user does not have a convenient way to move from the table headers to the table contents, or to move quickly between rows, without traversing the headers and cells. (30210426)
  • In Experience Manager, there is no keyboard alternative for drag and drop in the "mini-tree" of sections and cartridges within a rule or page. The workaround is to delete and re-add a cartridge. (24611047)
2.1.2 No Keyboard Trap (Level A)Supports

The product was tested for:

  • Movement of focus through the controls on the page using the keyboard only, with no "keyboard trap" that prevents focus from moving away from any control
2.1.4 Character Key Shortcuts (Level A)Not SupportedThis product has not yet been evaluated for this criteria
2.2.1 Timing Adjustable(Level A)Supports

The product was tested for:

  • Time limits in the product can be extended with at least 20 seconds warning up to 10 times
2.2.2 Pause, Stop, Hide (Level A)Supports

The product was tested for: 

  • The product does not present moving, blinking, or scrolling content
  • For any auto-updating that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause and stop the auto-updates.
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)Partially Supports

The product was tested for:

  • The keyboard user can skip the navigation tree in the left-hand pane and go right to the editor in the right-hand pane
  • The only other content that is repeated is the header bar, which contains only three options to be traversed

Exceptions:

  • The product documentation needs a "Skip to Main Content" link. (26934844)
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

Exceptions:

  • In the CAS Console and Keyword Redirects UIs, focus does not behave correctly in tables that occur within modals. (29132411, 29191539)
  • In the CAS Console, focus order is not consistent when tabbing backward vs. forward through the List view. (29160182, 29126354)
  • In Experience Manager, there are cases where focus remains on an overlay that lies behind the one that is currently active. (26634456)
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 are fully inter-linked to one another via a top-level menu that is always present
  • Pages contain controls that enable reaching other 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)Partially Supports

The product was tested for:

  • Visual indication of the location of the focus

Exceptions:

  • Focus is not visible on Workbench toolbar elements and megamenu options on home page. (29290243)
  • In Experience Manager, focus is not visible on some elements of the Schedule modal within the editor of a page or rule. (28499732)
2.5.1 Pointer Gestures (Level A)Not SupportedThis product has not yet been evaluated for this criteria
2.5.2 Pointer Cancellation (Level A)Not SupportedThis product has not yet been evaluated for this criteria
2.5.3 Label in Name (Level A)Not SupportedThis product has not yet been evaluated for this criteria
2.5.4 Motion Actuation (Level A)Not SupportedThis product has not yet been evaluated for this criteria
3.1.1 Language of Page(Level A)Supports

The product was tested for:

  • Pages have properly set lang attributes
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: 

  • Navigation mechanisms that are used in a group of pages are used consistently, with navigation elements appearing in the same relative order on the various pages.
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)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
  • Pages validate to the HTML specification

Exceptions:

  • Duplicate IDs are found on product documentation pages. (26324715)
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:

  • When a user tries to log into Workbench using the Chrome browser, but provides invalid input, a screen reader does not read the resulting error correctly. A workaround is to use Firefox. (29420569)
  • In the User Management UI, a screen reader does not read the value selected from the "Permission from Groups" dropdown in the editor's General tab. (27106342)
  • In the Experience Manager Manifest panel that is displayed with Preview, when a user segment or a device is selected, a screen reader does not read the selected value. (21414593)
  • In Experience Manager, in a rule that includes the Rich Text Editor, a screen reader reads "Rich Text Editor" twice. (24903474)
  • In Experience Manager, when the Project Contents list opens, a screen reader reads extraneous information. (21437353)
4.1.3 Status Messages (Level AA)Not SupportedThis product has not yet been evaluated for this criteria

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 ControlsSupports

The product was tested for:

  • A business user who uploads a video intended for display on a website can also upload a caption file and associate it with the video. When the business user previews the video in the product's media editor and turns on captioning, the caption file supplies the captions. The controls for turning captions on and off are provided at the same user interface level as the volume controls. 
503.4.2 Audio Description ControlsNot Supported

The product was tested for:

  • User controls for the selection of audio description are provided at the same menu level as the user controls for volume or program selection

Exceptions:

  • The video player provided in the media editor needs to support the use of an audio description as well as controls that allow the user to select an audio description. (30148086)
 504 Authoring ToolsHeading cell - no response requiredHeading cell - no response required
504.2 Content Creation or EditingSupports

See the WCAG 2.0 Section.

504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot Applicable

The product does not convert file formats.

504.2.2 PDF ExportNot Applicable

The product does not generate PDF exports.

504.3 PromptsPartially Supports

The product documentation encourages customers to create accessible content as follows:

  • It states that the Rich Text Editor allows creation of accessible content.
  • It encourages customers who specify a video file for display on their website to do the following:
    • Provide a soundtrack that is sufficiently descriptive of the visible content to communicate its meaning fully to an end user who is visually impaired.
    • Upload a caption file for the video and associate it with the video, so that captioning functions in the editor's video player.
    • Customize the Media editor to include 1) a field for identifying an associated caption file, 2) a field for identifying an associated text file containing an alternative description of the video, and 3) a field for identifying an associated audio file that describes the video; and supply these associated files along with any video to be displayed on the site.
  • It encourages customers who use the Media Editor to display an image on the website to provide text in the Alt Text field, so that Assistive Technology can read the alt text to the user.
  • It encourages customers to test their website content for accessibility.

Exceptions:

  • The out-of-the-box Media Editor needs to provide fields for a text alternative, an audio alternative, and a caption file, to encourage the business user to supply these files when specifying a video to be displayed on their website. (30147134)
504.4 TemplatesSupports

The product was tested for:

  • The product provides customizable "cartridges" that generate JSON or XML that can be used to display text, images, and videos on a website based on rules. A business user can use these cartridges to create content that conforms to the WCAG 2.0 AA standards. The rendering technology is independent of the cartridges.

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 FeaturesSupports

The product was tested for:

  • The Workbench User's Guide contains a chapter explaining how to navigate the user interface using the keyboard, as well as how to take advantage of other accessibility features (for example, pausing and stopping the auto-updating of information, and uploading a caption file for a video). The chapter mentions that our rich text editor allows creation of accessible content. It encourages business users to create accessible content and to test their websites for accessibility. The product's compatibility with assistive technology is available out of the box, with no action needed on the user's part. 
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 available 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.