Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Enterprise Single Sign-On Suite Plus 11.1.2.4.0

Product Description:

Enterprise Single Sign-On(ESSO) Suite Plus is a set of components designed to facilitate fast and secure access to applications and computing environments. The primary component of the suite is Logon Manager which facilitates application logon, by managing end user's passwords and injecting them into the application on behalf of the user when required. With ESSO, end users do have to remember their passwords or even type them into the applications.

ESSO Administration Console interacts with the Logon Manager and facilitates management and administration of ESSO attributes.

To manage Microsoft Windows password, the suite also contains a self service Password Reset module that allows users to reset their Microsoft Windows password without calling the help desk in instances where they have forgotten it. This component allows the use of Smart card, Proximity cards or biometric authentication onto the Microsoft Windows workstation, eliminating all the passwords in an enterprise without any additional software.

Provisioning Gateway module enables system administrators to directly distribute, reset, remove, or delete user credentials in Logon Manager without the need for any user involvement.

Logon Manager has Web UI and is also a Windows application. ESSO Administration Console is Windows application only. Self Service Password Reset module is Web UI only, while provisioning gateway has Web UI and is also a Windows application.

Date:

20-Jul-2021

Contact Information:

accessible_ww@oracle.com

Notes:

The following is excluded from this ACR:

PDF product documentation
PGCLI (Provisioning Gateway CLI)

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 UI and documentation 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 Titles for Objects and Applets are provided Controls have an associated name Client-side image maps specify the ALT attribute on each AREA element. CAPTCHAs are not used The Windows applications were tested for: Images are not used Non-text characters are not used 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 Web UI 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 Exception: Bug 32872297: There is no distinction between reports layout and data table in Provisioning Gateway & Password Reset UI The Windows applications were 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 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
1.3.2 Meaningful Sequence(Level A)	Partially Supports	The Web UI was tested for: The sequence of elements in the DOM matches a logical reading sequence Exception: Bug 32872381: UI Sequence is not correct in Credentials Windows of Logon Manager The Windows applications were tested for: The correct reading sequence is discernible when output is rendered to a file The documentation was tested for: The sequence of elements in the DOM matches a logical reading sequence
1.3.3 Sensory Characteristics(Level A)	Supports	The Web UI 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 Windows applications and documentation 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
1.3.4 Orientation (Level AA)	Partially Supports	The Web UI was tested for: Text is displayed in both device orientations without loss of functionality or visibility of the text. The Windows Application were tested for: Text is displayed in both device orientations without loss of functionality or visibility of the text. Exception: Bug 32869448: visibility of the text is lost with the orientation change in the administration console The documentation was 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 UI was tested for: Text fields which collect information about the user contain the appropriate autocomplete content attribute. The Windows applications were tested for: Markup languages aren't used to generate the user interface. 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 UI was tested for: Information is not conveyed using color The Windows applications were tested for: Information conveyed by color is available in text 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)	Partially Supports	The Web UI and documentation were tested for: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1 Other text and images of text have a contrast ratio of at least 4.5:1 The Windows applications were tested for: Other text and images of text have a contrast ratio of at least 4.5:1 Exception: Bug 32871774: Screens in Password Reset and Provisioning Gateway do not conform to contrast guidelines
1.4.4 Resize text(Level AA)	Supports	The Web UI, Windows applications and documentation were 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 UI, Windows applications and documentation were tested for: Images of text are not used
1.4.10 Reflow (Level AA)	Partially Supports	The Web UI and Windows Application were tested for: Text information reflows so that only one direction of scrolling is required while at 400% zoom. Exception: Bug 32856906: At 400% zoom, Password Reset and Provisioning Gateway requires both vertical and horizontal scrolling The documentation was tested for: Text information reflows so that only one direction of scrolling is required while at 400% zoom.
1.4.11 Non-text Contrast (Level AA)	Supports	The Web UI and documentation were tested for: Non-text items have a contrast ratio of at least 3:1 The Windows applications were tested for: Graphics are not used Non-text characters are not used
1.4.12 Text Spacing (Level AA)	Partially Supports	The Web UI 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 Exception: Bug 32857061: Part of the text content is not visible in Provisioning Gateway when text spacing is enabled The Windows applications were 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 UI and Windows applications 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. The documentation was tested for: There is no content that appears on hover or focus.
2.1.1 Keyboard(Level A)	Partially Supports	The Web UI and documentation were 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) The Windows application 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) Exception: Bug 32870088: Tab flow is not in a sequence in Administration Console
2.1.2 No Keyboard Trap (Level A)	Supports	The Web UI, Windows applications and documentation were tested for: Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control
2.1.4 Character Key Shortcuts (Level A)	Supports	The Web UI, Windows applications and documentation were tested for: There are no single character keyboard shortcuts.
2.2.1 Timing Adjustable(Level A)	Supports	The Web UI and Windows applications were tested for : Time limits used are part of a real-time event, or an essential activity The documentation was tested for: Time limits are not used
2.2.2 Pause, Stop, Hide (Level A)	Supports	The Web UI, Windows applications and documentation were tested for : There is no moving, blinking or scrolling content
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	The Web UI, Windows applications and documentation were 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 Web UI and documentation 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 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.
2.4.2 Page Titled(Level A)	Supports	The Web UI and documentation were tested for: Pages have a meaningful title specified in the TITLE element The Windows applications were tested for: The name of the software application is meaningful.
2.4.3 Focus Order(Level A)	Supports	The Web UI, Windows application and documentation were 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 UI, Windows application and documentation were tested for: The text of links and their surrounding paragraph, list, or table cell (with marked up table headers), is sufficient to describe their purpose
2.4.5 Multiple Ways(Level AA)	Supports	The Web UI was tested for : Pages are fully inter-linked to each other Page contains controls that enable reaching all pages The documentation 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 eachother Page contains controls that enable reaching all pages 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.
2.4.6 Headings and Labels(Level AA)	Supports	The Web UI, Windows applications and documentation were 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 UI, Windows applications and documentation were tested for: Visual indication of the location of the focus
2.5.1 Pointer Gestures (Level A)	Supports	The Web UI, Windows applications and documentation were tested for: There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)	Supports	The Web UI 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 Windows applications and documentation were tested for: There are no single pointer operations
2.5.3 Label in Name (Level A)	Partially Supports	The Web UI 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. The Windows application were 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. Exception: Bug 32879066: Label elements for the following do not contain the text or name associated to it: Password Reset Settings UI Password Reset Password Complexity UI Password Reset Reset Services UI Password Reset Storage UI Password Reset Logging UI Password Reset Reporting UI Password Reset Enrollment UI 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 Web UI, Windows applications and documentation were tested for: There are no functions that require motion of the device.
3.1.1 Language of Page(Level A)	Partially Supports	The Web UI was tested for: Properly set lang attribute for each page Exception: Bug 32856935: Provisioning Gateway UI page does not have a lang element. The Windows applications were tested for: Application is in the locale/language of the underlying platform The documentation was tested for: Properly set lang attribute for each page
3.1.2 Language of Parts(Level AA)	Supports	The Web UI and documentation were tested for: Proper use of lang attribute for text passages that are in a different language than that of the page The Windows applications were tested for: Text passages generated by the application are in the locale/language of the underlying platform
3.2.1 On Focus(Level A)	Supports	The Web UI, Windows applications and documentation 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
3.2.2 On Input(Level A)	Supports	The Web UI andWindows applications were tested for: In circumstances where changing the value of the components causes a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window, warning is given prior to the user interacting with those user-interface components 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 In circumstances where changing the value of the components causes a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window, warning is given prior to the user interacting with those user-interface components
3.2.3 Consistent Navigation(Level AA)	Partially Supports	The Web UI and Windows applications were 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: Bug 32871389: Left pane is not reachable using keyboard in Password Manager and Provisioning Gateway 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 Web UI, Windows applications and documentation were tested for: Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification(Level A)	Partially Supports	The Web UI 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 Windows applications were tested for: When input errors are detected, they are described to the user in text, including identifying the item where the error occurred Exception: Bug 32871571: Unable to read status and error messages from dialogs. 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 Web UI was tested for: Labels or instructions are provided when the product requires user input Exception: Bug 32856873: Label elements in calendar, event log, enroll user, reset client, management client screens do not contain the text or name associated to it The Windows application and documentation were tested for: Labels or instructions are provided when the product requires user input
3.3.3 Error Suggestion (Level AA)	Partially Supports	The Windows applications were tested for: Where suggestions for fixing an input error are known, they are provided to the user Exception: Bug 32871571: Unable to read status and error messages from dialogs. The documentation was tested for: The documentation does not have input fields, except for the Search field.
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)	Supports	The Web UI, Windows applications and documentation were tested for: Submissions can be reversed by the user Data is checked for input errors with an opportunity for the user to correct them Data can be reviewed, corrected, and confirmed by the user before they are finalized
4.1.1 Parsing(Level A)	Partially Supports	The Web UI 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 Exception: Bug 32856873: Elements in calendar, event log, enroll user, reset client, management client screens have duplicate Ids or attribute names. The Windows applications were 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
4.1.2 Name, Role, Value (Level A)	Partially Supports	The Web UI 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 a meaningful programmatically exposed name Frames have a meaningful title specified in the title attribute Exception: Bug 32856873: Label elements in calendar, event log, enroll user, reset client, management client screens do not contain the text or name associated to it The Windows applications were tested for: Form fields are named by their associated labels 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. Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’ Custom controls have appropriate roles specified using the role attribute Custom controls have appropriate state and property information conveyed using the relevant WAI-ARIA or HTML5 attributes Custom controls have a meaningful programmatically exposed name Frames have a meaningful title specified in the title attribute
4.1.3 Status Messages (Level AA)	Partially Supports	The Web UI was tested for: Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus. The Windows applications were tested for: Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus. Exception: Bug 32871571: Unable to read status and error messages from dialogs. 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	Supports	The Windows application was tested for: Software does not disrupt platform features that are defined in the platform documentation as accessibility features.
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	Supports	The Windows application was tested for: Responds to platform settings for color, contrast, font type, font size, and focus cursor
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	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	Product documentation does not have any accessibility and compatibility features listed. Exception: Bug 32954212: ESSO documentation does not include any accessibility and compatibility features
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.