Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Private Cloud Appliance Controller Software 3.0.1

Product Description:

Oracle Private Cloud Appliance (PCA) Controller Software is software that manages the different components in a rack. This software is responsible for initialization of the Management Nodes, Compute Nodes, Storage and Network elements. Two Graphical User Interfaces (GUIs/UIs) and a Command Line Interface (CLI) are provided to manage and monitor the components. The UIs are written in JavaScript and the CLI is written in Java. The software components are installed at the factory.

Date:

27-Sep-2021

Contact Information:

accessible_ww@oracle.com

Notes:

This ACR does not cover Kubernetes workload monitoring operator.

This ACR does not cover the Oracle Cloud Infrastructure Documentation Tool.

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 web UIs were tested for: Images that convey information have meaningful alternative text using ALT Images that are decorative are marked up using ALT=”” or CSS background images Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table) Input fields have associated labels Controls have an associated name Text summary or alternative is provided for time-based media Non-text characters are not used CAPTCHAs are not used The CLI was tested for: Images are not used Non-text characters are not used CAPTCHAs are not used The documentation 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) Input fields have associated labels Controls have an associated name Text summary or alternative is provided for time-based media Non-text characters are not used 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 web UIs were tested for: User interface component labels are associated with the fields they are labeling Headings are encoded with HTML heading tags Style sheets are used only to change the layout and presentation on the screen List markup is used for marking up lists Table markup is used for marking up data tables, including row and column headers Layout tables use appropriate markup The CLI was tested for: Headings follow standard text patterns for rendering headings Lists follow standard text patterns for rendering lists Paragraphs follow standard text patterns for rendering paragraphs Tables follow standard text patterns for rendering tables The documentation was tested for: User interface component labels are associated with the fields they are labeling Headings are encoded with HTML heading tags Style sheets are used only to change the layout and presentation on the screen List markup is used for marking up lists Table markup is used for marking up data tables, including row and column headers Layout tables use appropriate markup
1.3.2 Meaningful Sequence(Level A)	Supports	The web UIs were tested for: The sequence of elements in the DOM matches a logical reading sequence The CLI was tested for: The correct reading sequence is discernible when output is rendered to a file The documentation was tested for: The sequence presented matches a logical reading sequence.
1.3.3 Sensory Characteristics(Level A)	Supports	The Web UIs were tested for: Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound Instructions provided which refer to graphics included a reference to the text alternative of the graphic The CLI 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 The documenation 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.3.4 Orientation (Level AA)	Supports	The Web UIs have been tested for: Text is displayed in both device orientations without loss of functionality or visibility of the text. The CLI has been tested for: Text display orientation in a command line user interface is based on the ability of the terminal application used. The documentation has been 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 web UIs were tested for: Text fields which collect information about the user contain the appropriate autocomplete content attribute. The CLI was tested for: Text fields which collect information about the user contain the appropriate autocomplete content attribute. The documentation was tested for: There are no text fields that collect information about the user.
1.4.1 Use of Color(Level A)	Supports	The web UIs were tested for: Information conveyed by color has a contrast ratio of at least 3:1 Information conveyed by color is available in alternative formats, such as shape, text, font weight The CLI was tested for: Information conveyed by color is available in text. The documentation was tested for: Information conveyed by color has a contrast ratio of at least 3:1 Information conveyed by color is available in alternative formats, such as shape, text, font weight
1.4.2 Audio Control(Level A)	Not Applicable
1.4.3 Contrast (Minimum) (Level AA)	Supports	The web UIs were tested for: Small text has a contrast ratio of at least 4.5:1 Large scale text over 18pt has a contrast ratio of at least 3:1 The CLI was tested for: Text has a contrast ratio of at least 4.5:1 The documentation was tested for: Small text has a contrast ratio of at least 4.5:1 Large scale text over 18pt has a contrast ratio of at least 3:1
1.4.4 Resize text(Level AA)	Supports	The web UIs have been tested for Text can be resized up to 200% without loss of content or functionality The CLI has been tested for Text can be resized up to 200% without loss of content or functionality when rendered in a GUI-based terminal application that supports text rendering sizes up to 200% larger than normal The documentation 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 web UIs were tested for: Images of text are not used The CLI was tested for: Images of text are not used The documentation was tested for: Images of text are not used
1.4.10 Reflow (Level AA)	Supports	The web UIs were 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. The CLI was tested for: Text information can reflow with only one direction of scrolling when rendered in a GUI-based terminal application that supports text rendering sizes up to 400% larger than normal. The documentation 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.
1.4.11 Non-text Contrast (Level AA)	Supports	The web UIs were tested for: Non-text items have a contrast ratio of at least 3:1 The CLI was tested for: Graphics are not used Non-text characters are not used The documentation was tested for: Non-text items have a contrast ratio of at least 3:1
1.4.12 Text Spacing (Level AA)	Supports	The web UIs were tested for: When the following attributes and no others are modified there is no loss in functionality or content: Line height (line spacing) to at least 1.5 times the font size Spacing following paragraphs to at least 2 times the font size Letter spacing (tracking) to at least 0.12 times the font size Word spacing to at least 0.16 times the font size The CLI was tested for: Text is not rendered using markup languages. The documentation 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 web UIs were tested for: Dismissable -The content can be dismissed without moving the pointer or keyboard focus Hoverable - When pointer hover triggers additional content, the pointer can be moved over the additional content without the additional content disappearing Persistent - The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid. Information appears on hover or focus using default browser behavior, such as the title attribute of components. The CLI was tested for: There is no content that appears on hover or focus. The documentation 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)	Supports	The web UIs, documentation and the CLI are explicitly designed to be used entirely through a keyboard interface. The web UIs were tested for: Proper operation of unique keystrokes, including those listed in the product documentation Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes. The CLI was tested for: Proper operation of unique keystrokes Ability to perform functions from the keyboard only The documentation was tested for: Proper operation of unique keystrokes, including those listed in the product documentation Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes.
2.1.2 No Keyboard Trap (Level A)	Supports	The web UIs were tested for: Movement of focus through screen controls only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control The CLI was tested for: Keyboard focus is not used. The documentation was tested for: Movement of focus through screen controls 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 web UIs were tested for: There are no single character keyboard shortcuts The CLI was tested for: There are no single character keyboard shortcuts The documentation was tested for: There are no single character keyboard shortcuts
2.2.1 Timing Adjustable(Level A)	Supports	The web UIs were tested for: Time Adjustable - the web content access time can be extended by choosing to remain on the page before it times out Time limits can be adjusted to at least 10 times longer before encountered Time limits can be extended with at least 20 seconds warning up to at least 10 times The CLI was tested for: Time limits can be adjusted to at least 10 times longer before encountered Time limits can be extended with at least 20 seconds warning The documentation was tested for: Time limits are not used
2.2.2 Pause, Stop, Hide (Level A)	Supports	The web UIs were tested for: There is no moving, blinking, or scrolling content Auto updating pages allow the auto updating functionality to be disabled and the time between automatic updates may be adjusted The CLI was tested for: There is no moving, blinking or scrolling content There is no auto updating information The documentation was tested for: There is no moving, blinking or scrolling content There is no auto updating information
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	The web UIs were tested for: No portion of the screen flickers or flashes with a frequency between 2Hz and 55Hz The CLI was tested for: No portion of the screen flickers or flashes with a frequency between 2Hz and 55Hz The documentation was tested for: No portion of the screen flickers or flashes with a frequency between 2Hz and 55Hz
2.4.1 Bypass Blocks(Level A)	Supports	The web UIs were 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 The CLI 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 is always automatically met The documentation was tested for: Structure and hierarchy is marked up with Header elements outside of repetitive navigation links
2.4.2 Page Titled(Level A)	Supports	The web UIs were tested for: The name of the software application is meaningful Pages have a meaningful title specified in the TITLE element The CLI was tested for: The name of the software application is meaningful The documentation was tested for: Pages have a meaningful title specified in the TITLE element
2.4.3 Focus Order(Level A)	Supports	The web UIs were tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence The CLI was tested for: Keyboard focus is not used The documentation 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)	Supports	The web UIs were tested for: The text of links is sufficient to describe their purpose The CLI was tested for: Links are not used in the product The documentation was tested for: The text of links is sufficient to describe their purpose
2.4.5 Multiple Ways(Level AA)	Supports	The web UIs were tested for: Pages are fully inter-linked to each other Multiple ways to navigate to pages that are not one step in a succession Page contains controls that enable reaching all pages The CLI 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 is always automatically met The documentation was tested for: Pages are fully inter-linked to each other Page contains controls that enable reaching all pages Pages are in a site table of contents
2.4.6 Headings and Labels(Level AA)	Supports	The web UIs were tested for: Headers describe the topic or purpose of the content below them Labels describe the purpose of the associated field The CLI was tested for: Headers describe the topic or purpose of the content below them Labels are not used The documentation 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 web UIs were tested for: Visual indication of the location of the focus The CLI was tested for: Keyboard focus is not used The documentation was tested for: Visual indication of the location of the focus
2.5.1 Pointer Gestures (Level A)	Supports	The web UIs were tested for: There are no multipoint or path-based gesture actions The CLI was tested for: There are no multipoint or path-based gesture actions The documentation was tested for: There are no multipoint or path-based gesture actions
2.5.2 Pointer Cancellation (Level A)	Supports	The web UIs were tested for: When an operation uses a single pointer, the down-event of the pointer is not used to execute any part of the function 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 The CLI was tested for: There are no single pointer operations Documentation 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
2.5.3 Label in Name (Level A)	Supports	The web UIs were tested for: Labels do not include images of text User interface components that include text and have a label have a name that contains the text that is presented visually The CLI has been tested for: User interface components are not used The documentation 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 web UIs were tested for: There are no functions that require motion of the device The CLI was tested for: There are no functions that require motion of the device The documentation was tested for: There are no functions that require motion of the device
3.1.1 Language of Page(Level A)	Supports	The web UIs were tested for: Properly set lang attribute for each page The CLI was tested for: This application only runs in English, therefore it is expected that the user is also running their assistive technology in English, where applicable The documentation was tested for: Properly set lang attribute for each page
3.1.2 Language of Parts(Level AA)	Supports	The Web UIs were tested for: Proper use of lang attribute for text passages that are in a different language than that of the page The CLI was tested for: This application only runs in English, therefore it is expected that the user is also running their assistive technology in English, where applicable. The documentation 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 web UIs were tested for: When an element receives focus, it does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window The CLI was tested for: Keyboard focus is not used The documentation 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 web UIs were 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 The CLI was tested for: User interface components are not used The documentation 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 web UIs were tested for: Pages that are grouped together into sets with a common navigation mechanism utilize the navigation mechanism in the same fashion, with navigation elements appearing in the same relative order. The CLI 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 is always automatically met. The documentation was tested for: Pages that are grouped together into sets with a common navigation mechanism utilize the navigation mechanism in the same fashion, with navigation elements appearing in the same relative order.
3.2.4 Consistent Identification(Level AA)	Supports	The web UIs were tested for: Images and controls are used and identified consistently throughout the product The CLI was tested for: Images and controls are not used The documentation was tested for: Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification(Level A)	Supports	The web UIs were tested for: When input errors are detected, they are described to the user in text, including identifying the item where the error occurred The CLI was tested for: When input errors are detected, they are described to the user in text, including identifying the item where the error occurred The web UIs were 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 web UIs were tested for: Labels or instructions are provided when the product requires user input The CLI was tested for: Labels or instructions are provided when the product requires user input The documentation was tested for: Labels or instructions are provided when the product requires user input
3.3.3 Error Suggestion (Level AA)	Supports	The web UIs were tested for: Where suggestions for fixing an input error are known, they are provided to the user The CLI was tested for: Where suggestions for fixing an input error are known, they are provided to the user The documentation 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 web UIs were tested for: 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 The CLI was tested for 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 The documentation was tested for 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 web UIs were 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 The CLI was tested for: Markup languages aren't used to generate the user interface. The documentation 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)	Supports	The web UIs were tested for: HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc. Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’ Custom controls have a meaningful programatically exposed name The CLI was tested for: User interface components are not used The documentation 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 a meaningful programatically exposed name
4.1.3 Status Messages (Level AA)	Supports	The web UIs have been tested for: Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus The CLI was tested for: Markup languages aren't used to generate the user interface Documentation was tested for: There are no status messages

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	Supports	The CLI was tested for: Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts.
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	Supports	The CLI was tested for: Responds to platform settings for color, contrast, font type, font size, and focus cursor
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 Oracle Private Cloud Appliance documentation will have an accessibility section in the release notes. The release notes have not been published yet, but will be located within the following URL: https://docs.oracle.com/en/engineered-systems/private-cloud-appliance/.
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.