Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Documents Cloud Service: Web-DOCS (updated3) 17.1

Product Description:

The Oracle Documents Cloud Service web user interface provides a browser based view into the Oracle Documents Cloud Service.

Document content is organized within the service in a folder hierarchy, and the user interface provides a Windows Explorer style navigation paradigm. There is also a correspondingly similar search mechanism for finding content directly. Search results are listed in the same files and folders view. The product provides a document viewer that shows images of the document pages and a thumbnail view for faster navigation. The viewer is really just an image of the document however and as such isn't read out by a screen reader, therefore users should use the download feature to view the file in the the native application on their desktop.

One of the primary focuses of the product is collaboration. User can share their folders and files with other members of their tenant as well as the general public. Users can also participate in conversations about stand alone topics or about a particular file or folder. In order to post and reply within a conversation a user should be aware of the following

Within the General preferences area, under 'Change the way you submit your messages' a user can choose 'Use the Enter key to post messages and replies; use Shift+Enter to create new lines'. This way a user can type and hit enter to post a message without the need for any other keyboard shortcuts
Within the message editor a user can also use Alt+Shift+T to go go to the editor controls and user can then tab through them and get to the Post button (if user has typed in a message). More help is available by typing Alt+0

There is also place for users to set basic preferences about how the system operates for them and a place where users can find installation packages for the Oracle Documents desktop and mobile applications

Users with the role of an administrator also have access to similar configurations as the user preferences but they are settings at the tenant admin level.

Date:

29-Mar-2018

Archive Note:

This VPAT applies to only version 17.1. It does not apply to any versions of Oracle Documents Cloud Service: Web-DOCS after this. This VPAT has been superseded by Oracle Content and Experience Cloud: Content 18.4.

Contact Information:

accessible_ww@oracle.com

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.0, at https://www.w3.org/TR/2008/REC-WCAG20-20081211/	Level A - Yes Level AA - Yes Level AAA - No
Section 508 as published in 2017, at https://www.Section508.gov	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.
Supports with Exceptions: Some functionality of the product does not meet the criteria.
Does Not Support: Majority of functionality of the product does not meet the criteria.
Not Applicable: The criteria are not relevant to the product.

WCAG 2.0 Report

Table 1 also documents conformance with:

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

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

Table 1: WCAG Conformance Criteria

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content (Level A)	Supports with Exceptions	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 Non-text characters are not used or have meaningful alternative text There is no CAPTCHA used within the product Exceptions: Folder and file images do not have meaningful alternative text. Folders have folder images that state when it a personal folder or shared folder. Files have file type images that describe type of file using common application icons such as a Microsoft Office Word document or a PDF document. These images are not announced to screen readers. (Bug 16950284) The Message Edit box to post a message in a conversation is not descriptive to screen readers. When a conversation is created for a file or a folder, users have the ability to post messages to the conversation. The Post Message edit box does not have a descriptive name. (Bug 21666869) Images that are decorative in Login dialog are not marked up properly. (Bug 21828625)
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Supports with Exceptions	The product was tested for Pre-recorded Audio has an equivalent alternate presentation of that content Pre-recorded video has either an equivalent alternate presentation or the audio track provides equivalent information to the video track Exceptions: Pre-recorded videos are included in the embedded help. These videos do not include an audio track or captions (Bug 22365042) but the associated help articles provide an equivalent presentation of the information. However, this is not clearly labelled. (Bug 25225098)
1.2.2 Captions (Prerecorded) (Level A)	Supports with Exceptions	The product was tested for Pre-recorded video includes captions embedded in the media (potentially as a second version of the media) Exceptions: Pre-recorded videos are included in the embedded help. These videos do not include an audio track or captions (Bug 22365042) but the associated help articles provide an equivalent presentation of the information. However, this is not clearly labelled. (Bug 25225098)
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Supports with Exceptions	The product was tested for Pre-recorded video includes a second audio track with audio descriptions Pre-recorded video includes an alternative to the video Exceptions: Pre-recorded videos are included in the embedded help. These videos do not include an audio track or captions (Bug 22365042) but the associated help articles provide an equivalent presentation of the information. However, this is not clearly labelled. (Bug 25225098)
1.2.4 Captions (Live) (Level AA)	Supports	The product was tested for: No live audio content in video is being used
1.2.5 Audio Description (Prerecorded) (Level AA)	Supports with Exceptions	The product was tested for Pre-recorded video includes a second audio track with audio descriptions Exception: Pre-recorded videos are included in the embedded help. These videos do not include an audio track or captions (Bug 22365042) but the associated help articles provide an equivalent presentation of the information. However, this is not clearly labelled. (Bug 25225098)
1.3.1 Info and Relationships (Level A)	Supports with Exceptions	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 Exceptions: The Properties dialog heading is not descriptive to screen readers. When the Properties dialog opens for a file or folder, the file name or folder name is the heading of the dialog. (Bug 17195038) The Message Edit box to post a message in a conversation is not descriptive to screen readers. When a conversation is created for a file or a folder, users have the ability to post messages to the conversation. The Post Message edit box does not have a descriptive name. (bug 21666869) A conversation post message to an annotation image is not accessible. Users have the ability to add an annotation to a file (in the form of a "pushpin" image or a "highlighted" area) that is viewed in the preview page for the file. In order to add this annotation image, a post message has to be created and saved with the annotation image. When selecting this annotation image, after it has been created, the associated post message information is not accessible. (Bug 21677582) The "Save your Identity Domain" check box in the Login dialog does not have a descriptive label. (Bug 19337657) On the Login page, headings are not properly marked up. (Bug 22294270)
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.
1.4.1 Use of Color(Level A)	Supports with Exceptions	The product was tested for: Information conveyed by color is available in alternative formats, such as shape, text, font weight Information conveyed by color has a contrast ratio of at least 3:1 Exceptions: On the Login page, an error message is displayed if the user enters the wrong credentials. This is displayed using a red font color, but no other means are used to highlight the error. (Bug 22293738) When viewing a person's profile page, the active presence indicator is in a green color that does not pass color contrast guidelines. (Bug 25140626) The text in the Analytics Page does not meet the contrast ratio requirements. (Bug 25268213)
1.4.2 Audio Control(Level A)	Supports	The product was tested for: No automatically playing audio is used
1.4.3 Contrast (Minimum) (Level AA)	Supports with Exceptions	The product was tested for: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1 Other text and images of text have a contrast ratio of at least 4.5:1 Exceptions: When viewing a person's profile page, the active presence indicator is in a green color that does not pass color contrast guidelines. (Bug 25140626) The text in the Analytics page does not meet the contrast ratio requirements. (Bug 25268213)
1.4.4 Resize text(Level AA)	Supports	The product was tested for: Text can be resized up to 200% without loss of content or functionality.
1.4.5 Images of Text(Level AA)	Supports	The product was tested for: Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential.
2.1.1 Keyboard(Level A)	Supports with Exceptions	The product was tested for: Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms) Exceptions: A user has the ability to upload a file using the keyboard in the Web user interface. However, a user cannot cancel a file upload using the keyboard. During a file upload, a Notification bar appears across the top of the page showing the upload progress. This Notification bar has a Details and Cancel link that allows a user to cancel an upload. These links are not accessible when using Internet Explorer. (Bug 17905435) A user has the ability to go to the location where a file is being uploaded from the Notification bar. The file location is a link that directs the user to the user's home page or another folder. This file location link is not accessible. (Bug 19488780) A user has the ability to add an annotation to a file when viewed in the file view page. When the annotation on the page is selected via keyboard in file view, the associated post message is not accessible. (Bug 21677582) In the Admin interface, navigating through the Create Custom Property Groups is not read correctly. (Bug 24359674) When a user enters a conversation, the message text and time stamp are not read correctly. (Bug 25214304) A user has the ability to add a boolean field to a file's Custom Properties. Users can navigate to the field via the keyboard, but cannot trigger a change to the field (Bug 25267447)
2.1.2 No Keyboard Trap (Level A)	Supports	The product was tested for: Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control.
2.2.1 Timing Adjustable(Level A)	Supports	The product was tested for : Time limits used are part of a real-time event, or an essential activity Oracle Cloud Documents Service have a standard 8 hour authentication token validity period which will force a user to re-login after 8 hours. This is considered an essential activity as per Oracle Cloud security guidelines. There are no other time limits used.
2.2.2 Pause, Stop, Hide (Level A)	Supports	The product was tested for: There is no moving, blinking or scrolling content.
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	The product was tested for: No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz
2.4.1 Bypass Blocks(Level A)	Supports with Exceptions	The product was tested for: A ‘Skip to page content’ link is provided to skip repetitive navigation links at the top of the page. Exception: When using the web interface, the initial focus is on the first item in a folder listing, thereby skipping the navigation links provided at the top of the page. Once an item is selected, a list of menu items appears for that specific item in the menu bar or right click menu. For example, a folder item will have menu options to Open Item to view contents, to Move Item to another folder, to Copy Item to another folder, to Delete Item, to Share the folder with others, to Upload files to this folder, to Rename the folder, and view folder Properties information. Similar menu items appear for a file. If there are many items in a user's home page, a keyboard user will need to go through a series of steps to select menu items in a long folder listing. It would be more efficient for a keyboard user to have some options available via access/shortcut key to perform most frequently used actions like Share and Upload document. (Bug 16922445)
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)	Supports with Exceptions	The product was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence Exceptions: Keyboard focus does not remain in the Upload Details dialog. During a file upload, a Notification bar appears across the top of the page showing the upload progress. This Notification bar has a Details link that opens the Upload Details dialog. When this dialog opens, a user must navigate through the entire web page using the keyboard to be able to close the dialog. (Bug 16741735) A user has the ability to add an annotation to a file when viewed in the file view page. When an annotation on the page is selected via keyboard in the file view page, the associated post message does not receive keyboard focus. (Bug 21677582) A user has the ability to add a boolean field to a file's Custom Properties. Users can navigate to the field via the keyboard, but cannot trigger a change to the field (Bug 25267447)
2.4.4 Link Purpose (In Context)(Level A)	Supports with Exceptions	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 Exception: The Web user interface has the ability to preview a file in a viewer. Information about the contents of this image cannot be programmatically determined. (Bug 16589530)
2.4.5 Multiple Ways(Level AA)	Supports	The product was tested for Pages can be found using the provided "search" function
2.4.6 Headings and Labels(Level AA)	Supports with Exceptions	The product was tested for: Headers describe the topic or purpose of the content below them Labels describe the purpose of the associated field Exceptions The Properties dialog heading is not descriptive to screen readers. When the Properties dialog opens for a file or folder, the file name or folder name is the heading of the dialog. (Bug 17195038) The Message Edit box to post a message in a conversation is not descriptive to screen readers. When a conversation is created for a file or a folder, users have the ability to post messages to the conversation. The Post Message edit box does not have a descriptive name. (bug 21666869) A conversation post message to an annotation image is not accessible. Users have the ability to add an annotation to a file (in the form of a "pushpin" image or a "highlighted" area) that is viewed in the preview page for the file. In order to add this annotation image, a post message has to be created and saved with the annotation image. When selecting this annotation image, after it has been created, the associated post message information is not accessible. (Bug 21677582) The "Save your Identity Domain" check box in the Login dialog does not have a descriptive label. (Bug 19337657) On the Login page, headings are not properly marked up. (Bug 22294270) The user icon within the conversation view does not have a descriptive label. (Bug 24408509) In the Admin interface, navigating through the Create Custom Property Groups is not read correctly. (Bug 24359674)
2.4.7 Focus Visible(Level AA)	Supports with Exceptions	The product was tested for: Visual indication of the location of the focus Exception: When adding a user to a folder, it is hard to see which user is currently selected. (Bug 22613387)
3.1.1 Language of Page(Level A)	Supports with Exceptions	The product was tested for: Properly set lang attribute for each page Exception: The Login dialog has no language attribute. (Bug 20021413)
3.1.2 Language of Parts(Level AA)	Supports with Exceptions	The product was tested for: Proper use of lang attribute for text passages that are in a different language than that of the page Exception: The Login dialog has no language attribute. (Bug 20021413)
3.2.1 On Focus(Level A)	Supports with Exceptions	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 Exceptions: The Preferences page is refreshed when the user changes the Language settings. (Bug 19481981) A conversation post message to an annotation image is not accessible. Users have the ability to add an annotation to a file (in the form of a "pushpin" image or a "highlighted" area) that is viewed in the preview page for the file. In order to add this annotation image, a post message has to be created and saved with the annotation image. When selecting this annotation image, after it has been created, the associated post message information is not accessible. (Bug 21677582)
3.2.2 On Input(Level A)	Supports with Exceptions	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. Exceptions The Preferences page is refreshed when the user changes the Language settings. (Bug 19481981) A conversation post message to an annotation image is not accessible. Users have the ability to add an annotation to a file (in the form of a "pushpin" image or a "highlighted" area) that is viewed in the preview page for the file. In order to add this annotation image, a post message has to be created and saved with the annotation image. When selecting this annotation image, after it has been created, the associated post message information is not accessible. (Bug 21677582)
3.2.3 Consistent Navigation(Level AA)	Supports with Exceptions	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 Exception: Navigation through the conversation list and document list are not consistent. (Bug 22578666)
3.2.4 Consistent Identification(Level AA)	Supports	The product was tested for: Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification(Level A)	Supports	The product was tested for: When input errors are detected, they are described to the user in text, including identifying the item where the error occurred
3.3.2 Labels or Instructions (Level A)	Supports with Exceptions	The product was tested for: Labels or instructions are provided when the product requires user input. Exceptions The Message Edit box to post a message in a conversation is not descriptive to screen readers. When a conversation is created for a file or a folder, users have the ability to post messages to the conversation. The Post Message edit box does not have a descriptive name. (bug 21666869) The "Save your Identity Domain" check box in the Login dialog does not have a descriptive label. (Bug 19337657)
3.3.3 Error Suggestion (Level AA)	Supports	The product was tested for: Where suggestions for fixing an input error are known, they are provided to the user
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)	Supports	The product was tested for: Submissions can be reversed by the user Data is checked for input errors with an opportunity for the user to correct them Data can be reviewed, corrected, and confirmed by the user before they are finalized
4.1.1 Parsing(Level A)	Supports	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
4.1.2 Name, Role, Value (Level A)	Supports with Exceptions	The product was tested for: HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc. Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’. Custom controls have appropriate roles specified using the role attribute Custom controls have appropriate state and property information conveyed using the relevant WAI-ARIA or HTML5 attributes Custom controls have a meaningful programatically exposed name Frames have a meaningful title specified in the title attribute Exceptions: The Properties dialog heading is not descriptive to screen readers. When the Properties dialog opens for a file or folder, the file name or folder name is the heading of the dialog. (Bug 17195038) The Message Edit box to post a message in a conversation is not descriptive to screen readers. When a conversation is created for a file or a folder, users have the ability to post messages to the conversation. The Post Message edit box does not have a descriptive name. (bug 21666869) A conversation post message to an annotation image is not accessible. Users have the ability to add an annotation to a file (in the form of a "pushpin" image or a "highlighted" area) that is viewed in the preview page for the file. In order to add this annotation image, a post message has to be created and saved with the annotation image. When selecting this annotation image, after it has been created, the associated post message information is not accessible. (Bug 21677582) The "Save your Identity Domain" check box in the Login dialog does not have a descriptive label. (Bug 19337657) On the Login page, if there is an error because of bad credentials, the error message is not properly marked up. (Bug 22293738)

2017 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 Supported	BUG 26545666 - Need Controls for the Selection of Captions on Videos
503.4.2 Audio Description Controls	Not Supported	BUG 26545657 - Need User Controls for the Selection of Audio Descriptions
504 Authoring Tools	Heading cell - no response required	Heading cell - no response required
504.2 Content Creation or Editing	Not Applicable	The product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	The product is not an authoring tool.
504.2.2 PDF Export	Not Applicable	The product is not an authoring tool.
504.3 Prompts	Not Applicable	The product is not an authoring tool.
504.4 Templates	Not Applicable	The product is not an authoring tool.

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	Not Supported	BUG 26175494 Product does not have Accessibility Features documentation
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.