Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle GoldenGate 19.1 (Updated)

Product Description:

Oracle GoldenGate is a comprehensive software package for enabling the replication of data in heterogeneous data environments. The product set enables high availability solutions, real-time data integration, transactional change data capture, data replication, transformations, and verification between operational and analytical enterprise systems.

This VPAT covers Oracle GoldenGate (for Oracle), Oracle GoldenGate for Mainframe, and Oracle GoldenGate for Non-Oracle Database.

Oracle GoldenGate (for Oracle) is installed with Oracle Universal Installer (OUI).

Oracle GoldenGate for Non-Oracle Database and Mainframe are not installed with Oracle Universal installer (OUI).

Oracle GoldenGate is controlled using one of two Command Line Interfaces (CLI (GGSCI & AdminClient)) or through embedded HTML5 (WebUI) web pages.

Date:

26-Mar-2019

Archive Note:

This VPAT applies to only version 19.1 prior to 03-Mar-2021. It does not apply to any versions of Oracle GoldenGate after this. This VPAT has been superseded by Oracle GoldenGate 19.1 (Updated 3.1).

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following areas of the product:

Oracle Universal Installer (OUI): This is the technology used to install Oracle GoldenGate for Oracle. The alternative is to use the silent install option for OUI which is command-line interface.
Oracle GoldenGate documentation available in the following formats are excluded: PDF Documentation

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)	Partially Supports	The CLIs were tested for: Images are not used Non-text characters are not used or have meaningful alternative text CAPTCHAs are not used The WebUIs were tested for: Images that convey information have meaningful alternative text using ALT Images that are decorative are marked up using ALT=”” or CSS background images Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table) Titles for Objects and Applets are provided Controls have an associated name Text summary or alternative is provided for time-based media Client-side image maps specify the ALT attribute on each AREA element 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 Information shown in complex images such as charts is also available in an alternative textual form CAPTCHAs are not used The following defect was found: Bug 29316281 - Within the Performance Metric WebUI, the "Search table" table text box of the Message Overview table does not have a label and the Severity column "check box" image has no ALT text.
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)	Supports	The CLIs 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 WebUIs were tested for: User interface component labels are associated with the fields they are labeling Headings are encoded with HTML heading tags 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 CLIs were tested for: The correct reading sequence is discernible when output is rendered to a file The WebUIs were tested for: The sequence of elements in the DOM matches a logical reading sequence The documentation was tested for: The sequence of elements in the DOM matches a logical reading sequence The following defect was found: Bug 29450304 - In some elements of the WebUI, a correct meaningful sequence cannot be obtained.
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 WebUIs were tested for: Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound Instructions provided which refer to graphics included a reference to the text alternative of the graphic The 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)	Not Supported	This product has not yet been evaluated for this criteria
1.3.5 Identify Input Purpose (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
1.4.1 Use of Color(Level A)	Supports	The CLIs were tested for: Information conveyed by color is available in text The WebUIs were tested for: Information conveyed by color is available in alternative formats, such as shape, text, font weight 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 CLIs were tested for: Text has a contrast ratio of at least 4.5:1 The WebUIs 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 documentation was tested for: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1 Other text and images of text have a contrast ratio of at least 4.5:1 The following defect was found: Bug 29411502 - Multiple web pages of the WebUI have items with color contrast ratios of less than 4.5:1
1.4.4 Resize text(Level AA)	Partially Supports	The CLIs were 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 WebUIs were tested for: Text can be resized up to 200% without loss of content or functionality The documentation was tested for: Text can be resized up to 200% without loss of content or functionality The following defects were found: Bug 29291993 - In all pages of the WebUI, users cannot scroll on the menu when last menu item is selected at 200% zoom. Bug 29316614 - Some table details with the WebUI are no longer able to be fully scrolled though when zoomed to 200%.
1.4.5 Images of Text(Level AA)	Supports	The CLIs were tested for: Images of text are not used The WebUIs were 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 The documentation was tested for: Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential
1.4.10 Reflow (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
1.4.11 Non-text Contrast (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
1.4.12 Text Spacing (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
1.4.13 Content on Hover or Focus (Level AA)	Not Supported	This product has not yet been evaluated for this criteria
2.1.1 Keyboard(Level A)	Partially Supports	The CLIs are explicitly designed to be used entirely through a keyboard interface. The CLIs were tested for: ability to perform functions from the keyboard only The WebUIs 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 documentation was tested for: Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes The following defect was found: Bug 29315951 - Some elements within the WebUI do not open when keyboard focus is moved to them.
2.1.2 No Keyboard Trap (Level A)	Supports	The CLIs, WebUIs, 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 Supported	This product has not yet been evaluated for this criteria
2.2.1 Timing Adjustable(Level A)	Supports	The CLIs, WebUIS, and documentation were tested for: Time limits are not used
2.2.2 Pause, Stop, Hide (Level A)	Supports	The CLIs and WebUIs were tested for: Moving, blinking, or scrolling content that isn't a pure decoration is part of an essential activity The documentation was tested for: There is no moving, blinking or scrolling content
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	The CLIs, WebUIs, 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 CLIs were 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 WebUIs were tested for: A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page Structure and hierarchy is marked up with Header elements outside of repetitive navigation links WAI-ARIA Landmark elements are used outside of repetitive navigation links The 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
2.4.2 Page Titled(Level A)	Supports	The CLIs were tested for: The name of the software application is meaningful. The WebUIs were tested for: Pages have a meaningful title specified in the TITLE element The documentation was tested for: Pages have a meaningful title specified in the TITLE element
2.4.3 Focus Order(Level A)	Supports	The CLIs, WebUIs, 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 CLIs were tested for: Links are not used in the product The WebUIs 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 The documentation was 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 CLIs were 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 WebUIs were 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 CLIs were tested for: Labels are not used The WebUIs were tested for: Headers describe the topic or purpose of the content below them Labels describe the purpose of the associated field The documentation was tested for: 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 CLIs, WebUIs, and documentation were tested for: Visual indication of the location of the focus
2.5.1 Pointer Gestures (Level A)	Not Supported	This product has not yet been evaluated for this criteria
2.5.2 Pointer Cancellation (Level A)	Not Supported	This product has not yet been evaluated for this criteria
2.5.3 Label in Name (Level A)	Not Supported	This product has not yet been evaluated for this criteria
2.5.4 Motion Actuation (Level A)	Not Supported	This product has not yet been evaluated for this criteria
3.1.1 Language of Page(Level A)	Supports	The CLIs were tested for: This application only runs in English, therefore it is expected that the user is also running their assistive technology in English The WebUIs were tested for: Properly set lang attribute for each page The documentation was tested for: Properly set lang attribute for each page
3.1.2 Language of Parts(Level AA)	Supports	The CLIs were tested for: This application only runs in English, therefore it is expected that the user is also running their assistive technology in English The WebUIs were tested for: Proper use of lang attribute for text passages that are in a different language than that of the page The documentation was tested for: Proper use of lang attribute for text passages that are in a different language than that of the page
3.2.1 On Focus(Level A)	Partially Supports	The CLIs, WebUIs, and documentation were tested for: When an element receives focus, it does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window The following defect was found: Bug 29284505 - Some elements when selected via the keyboard with the WebUI, triggers a page down operation and causes the cursor to lose focus.
3.2.2 On Input(Level A)	Supports	The CLIs were tested for: User interface components are not used The WebUIs were tested for: Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window. The documentation was tested for: Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window.
3.2.3 Consistent Navigation(Level AA)	Supports	The CLIs were 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 WebUIs 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 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 CLIs were tested for: Images and controls are not used The WebUIs were tested for: Images and controls are used and identified consistently throughout the product The documentation was tested for: Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification(Level A)	Partially Supports	The CLIs 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 The WebUIs 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 following defect was found: Bug 29304648 - In some input fields of the WebUI, an error message cannot be determined using a screen reader when an incorrect entry is made.
3.3.2 Labels or Instructions (Level A)	Supports	The CLIs were tested for: Labels are not used The WebUIs were tested for: Labels or instructions are provided when the product requires user input The documentation was tested for: Labels or instructions are provided when the product requires user input
3.3.3 Error Suggestion (Level AA)	Partially Supports	The CLIs and WebUIs 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. The following defects were found: Bug 29343634 - Error suggestion is not given within the Administration Server WebUI when creating users and passwords and the wrong or unsupported format is entered.
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 WebUIs were tested for: Data is checked for input errors with an opportunity for the user to correct them
4.1.1 Parsing(Level A)	Supports	The Command Line Interfaces do not use markup language. 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 The WebUIs 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)	Supports	The CLIs were tested for: User interface components are not used The WebUIs were tested for: HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc. Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’. Custom controls have 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 The documentation was tested for: HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
4.1.3 Status Messages (Level AA)	Not Supported	This product has not yet been evaluated for this criteria

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 CLIs were tested for: Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts
502.3 Accessibility Services	Heading cell - no response required	Heading cell - no response required
502.3.1 Object Information	Not Applicable	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 CLIs were 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 Applicable	There are no specific Accessibility features that require 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.