Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle GoldenGate EM Plugin 13.5.1.0.0 for Enterprise Manager Cloud Control 13c Release 5 13.5

Product Description:

Oracle GoldenGate Enterprise Manager Plug-in, part of the Management Pack for Oracle GoldenGate,  provides a browser-based graphical user interface and automated alerting capabilities to monitor Oracle GoldenGate instances through Oracle Enterprise Manager.

Date:

18-Jan-2022

Archive Note:

This VPAT applies to only version 13.5. It does not apply to any versions of Oracle GoldenGate EM Plugin 13.5.1.0.0 for Enterprise Manager Cloud Control 13c Release 5 after this. This VPAT has been superseded by Oracle GoldenGate EM Plugin 13.5.2.0.0 for Enterprise Manager Cloud Control 13c Release 5 13.5.

Contact Information:

accessible_ww@oracle.com

Notes:

Oracle GoldenGatePlug-in for EMCC documentation available in the following formats are excluded: PDF Documentation

Dependent Products


This product interacts with or is built with the other Oracle products listedin this section. Click below to view information about the accessibility ofthese dependent products. Products listed are the versions available at thetime of publication of this document; newer documents may be available that supersedethese versions.

Evaluation Methods Used:

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

Accessibility Standards/Guidelines

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

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

Terms

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

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

WCAG 2.1 Report

Table 1 also documents conformance with:

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

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

Table 1: WCAG Conformance Criteria

Criteria
Conformance Level
Remarks and Explanations
1.1.1 Non-text Content (Level A)Supports

The CLI was tested for:

  • Images are not used
  • Non-text characters are not used
  • CAPTCHAs are not used

The WebUI was tested for:

  • Images that convey information have meaningful alternative text using ALT
  • Images that are decorative are marked up using ALT=”” or CSS background images
  • Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)
  • Titles for Objects and Applets are provided
  • Controls have an associated name
  • Text summary or alternative is provided for time-based media
  • Non-text characters are not used or have meaningful alternative text
  • CAPTCHAs are not used

The documentation was tested for:

  • Images that convey information have meaningful alternative text using ALT
  • The information shown in complex images such as charts is also available in an alternative textual and tabular format
  • CAPTCHAs are not used
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.4 Captions (Live) (Level AA)Not ApplicableThe product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)Not ApplicableThe product has no multimedia.
1.3.1 Info and Relationships (Level A)Supports

The CLI was tested for:

  • Headings follow standard text patterns for rendering headings
  • Lists follow standard text patterns for rendering lists
  • Paragraphs follow standard text patterns for rendering paragraphs
  • Tables follow standard text patterns for rendering tables

The WebUI 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

The documentation was tested for:

  • 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

 

1.3.2 Meaningful Sequence(Level A)Partially Supports

The CLI was tested for:

  • The correct reading sequence is discernible when output is rendered to a file

The WebUI and documentation were tested for:

  • The sequence of elements in the DOM matches a logical reading sequence

Exception: 

  • Bug 33628423 - Keyboard Tab key does not move in sequential order in Admin server Processes metrics table cell
1.3.3 Sensory Characteristics(Level A)Supports

The CLI was tested for:

  • Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound

The WebUI 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
1.3.4 Orientation (Level AA)Supports

The CLI was tested for:

  • Text display orientation in a command line user interface is based on the ability of the terminal application used.

The WebUI was tested for:

  • Text is displayed in both device orientations without loss of functionality or visibility of the text.
  • A fixed display orientation is not required for essential functionality. 

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)Not Applicable

The CLI was tested for:

  • Markup languages are not used to generate the user interface.

The WebUI and documentation were tested for:

  • There are no text fields that collect information about the user.
1.4.1 Use of Color(Level A)Supports

The CLI was tested for:

  • Information conveyed by color is available in text

The WebUI 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 ApplicableThe product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)Supports

The CLI was tested for:

  • Text has a contrast ratio of at least 4.5:1

The WebUI 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
1.4.4 Resize text(Level AA)Supports

The CLI was tested for:

  • Text can be resized up to 200% without loss of content or functionality when rendered in a GUI-based terminal application that supports text rendering sizes up to 200% larger than normal

The WebUI 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)Partially Supports

The CLI was tested for:

  • Images of text are not used

The WebUI 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

Exception:

  • Bug 33506271 - Screen Reader cannot read Process Health Overview, Alert Overview, and Chart Status of process details in Admin server
1.4.10 Reflow (Level AA)Partially Supports

The CLI was tested for:

  • Text information can reflow with only one direction of scrolling when rendered in a GUI-based terminal application that supports text rendering sizes up to 400% larger than normal.

The WebUI 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.

The documentation was tested for:

  • Text information reflows so that only one direction of scrolling is required while at 400% zoom.
  • Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.

Exceptions:

  • BUG 32429048 - Plugin information lost at 400% zoom
  • BUG 33478428 - Deployment detail page Horizontal Scroll bar is not available when user resize the web browser
  • BUG 33464534 - Horizontal and vertical scroll bar should be available for all sections in Admin server detail page
  • BUG 33424342 - Process search button is not visible if user resizes the process section in Admin server detail page
1.4.11 Non-text Contrast (Level AA)Supports

The CLI was tested for:

  • Graphics are not used
  • Non-text characters are not used

The WebUI and documentation were tested for:

  • Non-text items have a contrast ratio of at least 3:1
1.4.12 Text Spacing (Level AA)Partially Supports

The CLI was tested for:

  • Text is not rendered using markup languages.

The WebUI and documentation were tested for:

  • When the following attributes and no others are modified there is no loss in functionality or content:
    • Line height (line spacing) to at least 1.5 times the font size
    • Spacing following paragraphs to at least  2 times the font size
    • Letter spacing (tracking) to at least 0.12 times the font size
    • Word spacing to at least 0.16 times the font size

Exception:

  • BUG 32429415 - Receiver server Menu Text is not Readable with Text Spacing
1.4.13 Content on Hover or Focus (Level AA)Supports

The CLI was tested for:

  • There is no content that appears on hover or focus.

The WebUI 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:

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

The CLI is explicitly designed to be used entirely through a keyboard interface.

The CLI was tested for:

  • ability to perform functions from the keyboard only
  • proper operation of unique keystrokes, including those listed in the product documentation

The WebUI 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)
2.1.2 No Keyboard Trap (Level A)Supports

The CLI, WebUI, 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)Not Applicable

The CLI, WebUI, and documentation were tested for:

  • There are no single character keyboard shortcuts. 
2.2.1 Timing Adjustable(Level A)Supports

The CLI was tested for:

  • Time limits are not used

The WebUI was tested for:

  • Time limits in the product can be turned off before they are encountered
  • Time limits in the product can be adjusted to at least 10 times longer before encountered
  • Time limits in the product can be extended with at least 20 seconds warning up to 10 times

The documentation was tested for:

  • Time limits are not used
2.2.2 Pause, Stop, Hide (Level A)Not Applicable

The CLI, WebUI, 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 CLI, WebUI, 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)Partially Supports

The CLI was tested for:

  • Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline is automatically met.

The WebUI 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:

  • 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

Exception: 

  • BUG 32328515 - Bypass Blocks does not exist in GoldenGate Target Page
2.4.2 Page Titled(Level A)Partially Supports

The CLI was tested for:

  • The name of the software application is meaningful.

The WebUI and documentation were tested for:

  • Pages have a meaningful title specified in the TITLE element

Exception:

  • BUG 32429562 - Auto discovery input popup frame does not have a Title
2.4.3 Focus Order(Level A)Partially Supports

The CLI, WebUI, and documentation were tested for:

  • Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence

Exception:

  • Bug 33628423 - Keyboard Tab key does not move in sequential order in Admin server Processes metrics table cell
2.4.4 Link Purpose (In Context)(Level A)Supports

The CLI was tested for:

  • Links are not used in the product

The WebUI 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 CLI was tested for:

  • Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline is automatically met.

The WebUI 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
2.4.6 Headings and Labels(Level AA)Supports

The CLI was tested for:

  • Labels are not used

The WebUI 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 CLI, WebUI, and documentation were tested for:

  • Visual indication of the location of the focus
2.5.1 Pointer Gestures (Level A)Not Applicable

The CLI, WebUI, and documentation were tested for:

  • There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)Supports

The CLI was tested for:

  • There are no single pointer operations

The WebUI was tested for:

  • When an operation uses a single pointer, the down-event of the pointer is not used to execute any part of the function.
  • When an operation uses a single pointer, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion.

The documentation was tested for:

  • There are no single pointer operations
2.5.3 Label in Name (Level A)Supports

The CLI was tested for:

  • User interface components are not used

The WebUI 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.

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)Not Applicable

The CLI, WebUI, and documentation were tested for:

  • There are no functions that require motion of the device.
3.1.1 Language of Page(Level A)Supports

The CLI  was tested for:

  • This application only runs in English, therefore it is expected that the user is also running their assistive technology in English

The WebUI and documentation were tested for:

  • Properly set lang attribute for each page
3.1.2 Language of Parts(Level AA)Supports

The CLI  was tested for:

  • This application only runs in English, therefore it is expected that the user is also running their assistive technology in English

The WebUI and documentation were tested for:

  • Proper use of lang attribute for text passages that are in a different language than that of the page
3.2.1 On Focus(Level A)Supports

The CLI, WebUI, 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 CLI was tested for:

  • User interface components are not used

The WebUI and documentation were tested for:

  • Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window
3.2.3 Consistent Navigation(Level AA)Supports

The CLI was tested for:

  • Oracle non-Web software products, including bundles and suites of software, do not behave as a set of software programs as the term is defined. Therefore this guideline is automatically met.

The WebUI and documentation 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
3.2.4 Consistent Identification(Level AA)Supports

The CLI was tested for:

  • Images and controls are not used

The WebUI 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 documentation
3.3.1 Error Identification(Level A)Supports

The CLI, WebUI, and documentation were tested for:

  • When input errors are detected, they are described to the user in text, including identifying the item where the error occurred
3.3.2 Labels or Instructions (Level A)Supports

The CLI was tested for:

  • Labels are not used

The WebUI and documentation were tested for:

  • Labels or instructions are provided when the product requires user input

 

3.3.3 Error Suggestion (Level AA)Supports

The CLI and WebUI were tested for:

  • Where suggestions for fixing an input error are known, they are provided to the user

The documentation was tested for:

  • The documentation has no input fields, except for the search field.
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)Supports

Data modification or deletion is not a part of the GoldenGate CLIs or documentation.

The WebUI was tested for:

  • Data is checked for input errors with an opportunity for the user to correct them
  • Data can be reviewed, corrected, and confirmed by the user before they are finalized

The documentation was tested for:

  • Data modification or deletion is not a part of the documentation.
4.1.1 Parsing(Level A)Supports

The Command Line Interface does not use markup language.

The WebUI and documentation were tested for:

  • Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs.
4.1.2 Name, Role, Value (Level A)Partially Supports

The CLI was tested for:

  • User interface components are not used

The WebUI 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

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.

Exceptions:

  • Bug 32447152 - List box does not have Alternate Text in Extract Report file tab
  • Bug 33510481 - Screen Reader does not read GoldenGate Deployment's names drop-down menu in Service Manager Detail page
4.1.3 Status Messages (Level AA)Not Applicable

The CLI was tested for:

  • Markup languages aren't used to generate the user interface.

The WebUI and documentation were tested for:

  • There are no status messages.

back to top

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria
Conformance Level
Remarks and Explanations
302.1 Without VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of ColorNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without SpeechNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited ManipulationNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and StrengthNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning AbilitiesNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

back to top

Chapter 4: Hardware

These criteria are all Not Applicable because the product is not Hardware

Chapter 5: Software

Criteria
Conformance Level
Remarks and Explanations
501.1 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
 502 Interoperability with Assistive TechnologyHeading cell - no response requiredHeading cell - no response required
502.2.1 User Control of Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility FeaturesSupports

The CLI was tested for:

  • Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts

Oracle GoldenGate OEM PlugIn is a web-application which runs in the browser and hence this criteria is not applicable to the product.

 502.3 Accessibility ServicesHeading cell - no response requiredHeading cell - no response required
502.3.1 Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and HeadersNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.4 ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.6 Label RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.8 TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.10 List of ActionsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on ObjectsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.14 Event NotificationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
 503 ApplicationsHeading cell - no response requiredHeading cell - no response required
503.2 User PreferencesSupports

The CLIs were tested for:

  • Responds to platform settings for color, contrast, font type, font size, and focus cursor

Not applicable for the WebUI and documentation, as they only use technologies that run in a browser.

503.3 Alternative User InterfacesNot ApplicableThe product does not have assistive technology features.
 503.4 User Controls for Captions and Audio DescriptionHeading cell - no response requiredHeading cell - no response required
503.4.1 Caption ControlsNot ApplicableThe product has no multimedia.
503.4.2 Audio Description ControlsNot ApplicableThe product has no multimedia.
 504 Authoring ToolsHeading cell - no response requiredHeading cell - no response required
504.2 Content Creation or EditingNot ApplicableThe product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot ApplicableThe product is not an authoring tool.
504.2.2 PDF ExportNot ApplicableThe product is not an authoring tool.
504.3 PromptsNot ApplicableThe product is not an authoring tool.
504.4 TemplatesNot ApplicableThe product is not an authoring tool.

back to top

Chapter 6: Support Documentation and Services

Criteria
Conformance Level
Remarks and Explanations
 602 Support DocumentationHeading cell - no response requiredHeading cell - no response required
602.2 Accessibility and Compatibility FeaturesNot Applicable

There are no specific Accessibility features that require documentation.

602.3 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support DocumentationNot Applicable

Product Documentation is in electronic format.

 603 Support ServicesHeading cell - no response requiredHeading cell - no response required
603.2 Information on Accessibility and Compatibility FeaturesSupportsOracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication NeedsSupportsOracle customers have access to electronic support through My Oracle Support or by calling Oracle Support at 1.800.223.1711. Hearing-impaired customers in the U.S. who wish to speak to an Oracle Support representative may use a telecommunications relay service (TRS). Information about the TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of telephone numbers is available at https://www.fcc.gov/general/telecommunications-relay-services-directory. International hearing-impaired customers should use the TRS at +1.605.224.1837. An Oracle Support engineer will respond to technical issues according to the standard service request process.

back to top

Oracle Legal Disclaimer

The information above describes this product's ability to support the applicableStandards/Guidelines, subject to Oracle's interpretation of those standards(available at https://www.oracle.com/corporate/accessibility/policy.html#standards-tab) and the remarks in this document. For more information regarding the accessibility status of this product or other Oracle products, see http://www.oracle.com/corporate/accessibility or contact: accessible_ww@oracle.com.

This document is provided for information purposes only and the contents hereof are subject to change without notice. Oracle Corporation does not warrant that this document is error free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Oracle Corporation specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Oracle further makes no representation concerning the ability of assistive technologies or other products to interoperate with Oracle products. This document addresses the named product(s) only and not prerequisite products for which Oracle supplies restricted use licenses.