Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle WebCenter Sites 12.2.1.4.0 (Update3.1)

Product Description:

WebCenter Sites is used to create websites e.g. oracle.com. At an abstract level - WebCenter Sites product provides two things: 1. A content management framework and a dynamic rendering / caching mechanism that clients use to create their website. 2. A Contributor User Interface (UI) that will provide the content management functionality. On top of this, clients can code Java Server Pages (JSPs) to customize their website (we provide Application Program Interfaces (APIs) to access content from WebCenter Sites and use the underlying rendering/caching mechanism). The markup required for making the final website accessible is the client's responsibility.

Date:

31-Mar-2021

Contact Information:

accessible_ww@oracle.com

Notes:

This ACR does not cover the following product areas:

Admin UI
The WYSIWYG (What You See Is What You Get) Site Contributor tool

Evaluation Methods Used:

Oracle's policy is to design, develop and test both products and documentation to be accessible. The recommended styles of testing for accessibility include: (i) algorithmic automated tests, (ii) human judgement tests such as tool-assisted tests, visual inspection and manual operation, and (iii) testing with assistive technology by people with and without disabilities. Additional information about Oracle's accessibility program is available on http://www.oracle.com/corporate/accessibility/index.html

Accessibility Standards/Guidelines

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

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

Terms

The terms used in the Conformance Level information are defined as follows:

Supports: The functionality of the product has at least one method that meets the criteria without known defects or meets with equivalent facilitation.
Partially Supports: Some functionality of the product does not meet the criteria.
Does Not Support: Majority of functionality of the product does not meet the criteria.
Not Applicable: The criteria are not relevant to the product.

WCAG 2.1 Report

Table 1 also documents conformance with:

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

Note: When reporting on conformance with the WCAG 2.1 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content (Level A)	Supports	The product was tested for: Images that convey information have meaningful alternative text using ALT Images that are decorative are marked up using ALT=”” or CSS background images Titles for Objects and Applets are provided Controls have an associated name Layout tables use appropriate markup Text summary or alternative is provided for time-based media Non-text characters are not used CAPTCHAs are not used. The documentation was tested for: Images that convey information have meaningful alternative text Images that are decorative are marked up using ALT=”” or CSS background images Titles for Objects and Applets are provided Controls have an associated name Time-based media is not used Image maps are not used Non-text characters have meaningful alternative text CAPTCHAs are not used
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.4 Captions (Live) (Level AA)	Not Applicable	The product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)	Not Applicable	The 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 labeling Headings are encoded with HTML heading tags List markup is used for marking up lists Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate Data tables specify SUMMARY or CAPTION Layout tables use appropriate markup Groups of components are marked up with their description Style sheets are used only to change the layout and presentation on the screen Below are the bugs for the exceptions: Bug 25589296 - Segment/Basic/Flex/Page have Role separator Elements that have children which take focus. Bug 25517508 - Accessible Names are not associated with tables in Contributor UI The documentation 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, table captions/summaries where appropriate) Data tables specify SUMMARY or CAPTION where appropriate Layout tables are not used Groups of components are not used Style sheets are used only to change the layout and presentation on the screen
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 Below are the bugs for the exceptions: Bug 17508251 - Screen Reader doesn't read warning message when invalid input entered in to tag field. Bug 18726080 - Only part of the workflow status page is read by the Screen Reader Bug 21066071 - Screen Reader doesn't read Warning messages in Login screen. Bug 21175206 - Screen Reader doesn't read the field name for Pulldown,Uploader,typeAhead attribute editors Bug 23014040 - Screen Reader doesn't read segment assets correctly. Bug 23068859 - Unable to select Start and End Date in ABTest page using keyboard Bug 23069023 - Unable to select Edit button in A/BTest Report page using keyboard Bug 25524003 - Unable to Click Asset Translation Delete button using space button The documentation was tested for: Content is available in a meaningful 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 included a reference to the text alternative of the graphic The documentation 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. Images have meaningful text alternative.
1.3.4 Orientation (Level AA)	Supports	The product was tested for Text is displayed in both device orientations without loss of functionality or visibility of the text. The documentation was tested for: Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.
1.3.5 Identify Input Purpose (Level AA)	Not Supported	The product was tested for : Text fields that collect information about the user contain the appropriate autocomplete content attribute. Below is the bug for exception: When adding details for a user on the WEM (Web Experience Management) Admin screen, autocomplete is currently off (Bug 32546916) 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 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 The documentation was tested for: Information conveyed by color is available in alternative formats, such as shape, text, font weight
1.4.2 Audio Control(Level A)	Not Applicable	The product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)	Supports	The product was tested for: Large-scale text and images of large-scale text are tested for a contrast ratio of at least 3:1 Other text and images of text are tested for a contrast ratio of at least 4.5:1 The documentation 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)	Partially Supports	The product was tested for: Text can be resized up to 200% without loss of content or functionality Below are the bugs for the exceptions: Bug 21178211 - Mobility Preview page is getting disturbed upon zoom to 150% and more. Bug 21178143 - Select Layout popup is not visible when asset preview page is zoomed to 200% 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 product was tested for Images of text are not used The documentation was tested for: Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential
1.4.10 Reflow (Level AA)	Partially Supports	The product was tested for : Text information reflows so that only one direction of scrolling is required while at 400% zoom. Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content. Below is the bug for exception: WebCenter Sites Contributor UI is not completely responsive at 400% zoom. The user cannot perform all actions at 400% zoom. (Bug 32559508) The documentation was tested for: Content is presented without loss of information or functionality, and without requiring scrolling in two dimensions except for parts of the content which require two-dimensional layout for usage or meaning. Text information reflows so that only one direction of scrolling is required while at 400% zoom.
1.4.11 Non-text Contrast (Level AA)	Partially Supports	The product was tested for: Non-text items have a contrast ratio of at least 3:1 Below are the bugs for exceptions: Graphical objects do not have the required contrast ratio of 3:1. In different areas of WebCenter Sites Contributor UI, few graphical buttons are not as per the required ratio. (Bug 32559551, 32617566) 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 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 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 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. 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.
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) Below are the bugs for the exceptions: Bug 25524003 - Unable to Click Asset Translation Delete button using space button (Screen Reader) Bug 23069023 - A/BTest Report page, Unable to select Edit button using keyboard. The documentation was tested for: The logical tab order through the controls and selectable elements Ability to access page elements (links and buttons) Ability to perform functions from the keyboard only Logical movement of focus through the controls
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 The documentation was tested for: Movement of focus through 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 product was tested for: There are no single character keyboard shortcuts. The documentation was tested for: There is no single character keyboard shortcut in content
2.2.1 Timing Adjustable(Level A)	Supports	The product was tested for : Time limits are not used The documentation 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 found in the product. The documentation was tested for: No moving, blinking or scrolling content No auto-updating information
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 The documentation 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 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 product was tested for: Pages have a meaningful title specified in the TITLE element The documentation 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. Below are the bugs for the exceptions: Bug 23068859 - Focus order missing and unable to move to Start and End Date field. 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 product was tested for: The text of links and their surrounding paragraph, list, table cell (with marked up table headers), or preceding heading is sufficient to describe their purpose The documentation was tested for: The purpose of a link can be determined from the link text or from the surrounding text.
2.4.5 Multiple Ways(Level AA)	Supports	The product was tested for: Pages are contained in a "site map" Pages can be found using the provided "search" function Pages are in a site table of contents Pages are fully inter-linked to each other Page contains controls that enable reaching all pages The documentation was tested for: Pages contain controls that enable reaching other pages Pages can be found using the provided "Search" function
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 The documentation was tested for: Headings and labels describe topic or purpose.
2.4.7 Focus Visible(Level AA)	Supports	The product was tested for: Visual indication of the location of the focus. The documentation was tested for: Location of focus is visible.
2.5.1 Pointer Gestures (Level A)	Supports	The product 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 product was tested for 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 documentation was tested for: 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)	Partially Supports	The product has been tested for : User interface components that include text or images of text and have a label, have a name that contains the text that is presented visually. Below is the bug for exception: When a user performs a search in WCS Contributor UI, few buttons do not have discernible text. (Bug 32548581) The documentation was 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. 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 product was tested for: Properly set lang attribute for each page The documentation was tested for: Properly set lang attribute for each page
3.1.2 Language of Parts(Level AA)	Partially 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 Below are the bugs for the exceptions: Bug 21143894 - In RTL-> Content Menu -> Submenu dropdown options are not shown fully Bug 21143807 - In RTL, Context menu & submenu overlap each other in Cont UI tree. The documentation was tested for: Text passages are in the same language as 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 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 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 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 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. The documentation 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 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 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. The documentation was tested for: The documentation does not have input fields, except for the Search field
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 Below are the bugs for the exceptions: Bug 21175206 - Screen Reader doesn't read the field name for Pulldown,Uploader,typeAhead attribute editor. The documentation was tested for: Content does not require 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 in message form as well as read properly by screen reader. The documentation was tested for: Content does not require user input
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. The documentation was tested for: The documentation does not require user input that modifies user controllable data
4.1.1 Parsing(Level A)	Supports	The product was tested for Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs. 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)	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’. Frames have a meaningful title specified in the title attribute Below are the bugs for the exceptions: 18018143 - Values in the multi-valued attribute dialog are not read properly by the screen reader. Currently, text and image values are recognized and read as buttons. 21175206 - Screen Reader doesn't read the field name for Pulldown,Uploader,typeAhead attribute editor 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.
4.1.3 Status Messages (Level AA)	Supports	The product was tested for: Status messages have roles or properties set so information is conveyed to assistive technology without the component receiving focus. The 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	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of Color	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without Speech	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited Manipulation	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and Strength	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning Abilities	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

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	The product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility Features	Not Applicable	The product is designed to be isolated from the underlying platform.
502.3 Accessibility Services	Heading cell - no response required	Heading cell - no response required
502.3.1 Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and Headers	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.4 Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.6 Label Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.8 Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.10 List of Actions	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on Objects	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.14 Event Notification	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility Features	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
503 Applications	Heading cell - no response required	Heading cell - no response required
503.2 User Preferences	Not Applicable	The product is designed to be isolated from the underlying platform.
503.3 Alternative User Interfaces	Not Applicable	The product does not have assistive technology features.
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	The product has no multimedia.
503.4.2 Audio Description Controls	Not Applicable	The product has no multimedia.
504 Authoring Tools	Heading cell - no response required	Heading cell - no response required
504.2 Content Creation or Editing	Supports	The markup required for making the final website accessible is the client's responsibility.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	Product does not perform format conversion
504.2.2 PDF Export	Not Applicable	This product does not export PDF
504.3 Prompts	Not Supported	BUG 26193530 Product does not conform to 504.3
504.4 Templates	Not Supported	BUG 26193542 Product does not provide templates

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	Oracle WebCenter Sites accessibility features are documented in Accessibility Features and Tips for Oracle WebCenter Sites.
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	Not Applicable	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.