Oracle Accessibility Conformance Report

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

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

Exception(s):

Bug 37011668 - Connection Details page status icon has incorrect HTML attributes

Bug 36942159 - Connection editing page has incorrect HTML attributes

Bug 36821075 - Search control on Home page has incorrect HTML attributes

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(s):

Bug 37007090 - Meaningful navigation sequence is incorrect to get to Next button, in the create User Management page

Bug 36867136 - Meaningful navigation sequence missing in Connection Details page, Properties and Datatype table

Bug 36860901 - Incorrect sequence when in error is encountered within Create Connection page

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

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.

Exception(s):

Bug 36896582 - Text cut-off and overlap issues are seen for multiple web pages when default orientation is changed

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.

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

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

Exception(s):

Bug 37007039 - Comparison Status element of Monitor Jobs page contrast ratio does not meet expected 4.5:1 ratio

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

Exception(s):

Bug 36851779 - Connections Details page content is not visible at 200% zoom

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

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.

Exception(s):

Bug 36851779 - Connections Details page content is not visible at 200% zoom

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

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

Exceptions(s):

Bug 36866822 - Page alignment issue in Connections page when text space is set as per WCAG 2.1 Text Spacing

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.

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)

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

The CLI, WebUI, and documentation were tested for:

• There are no single character keyboard shortcuts. 

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

The CLI, WebUI, and documentation were tested for:

• There is no moving, blinking or scrolling content

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

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

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

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

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

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

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

The CLI, WebUI, and documentation were tested for:

• Visual indication of the location of the focus

The CLI was tested for:

• Keyboard focus is not used

The WebUI and documentation were tested for:

• The initial position of user interface components receiving keyboard focus are not hidden entirely by author-created content.

The CLI, WebUI, and documentation were tested for:

• There are no multipoint or path-based gesture actions.

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

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.

The CLI, WebUI, and documentation were tested for:

• There are no functions that require motion of the device.

The CLI, WebUI, and documentation were tested for:

• There is no functionality that uses dragging movements.

The CLI and documentation were tested for:

• The product does not contain interactive targets

The WebUI was tested for:

• Interactive targets take up at least 24×24 CSS pixels of space, including white space around the target, and the space is not shared with another target.

The documentation was tested for:

• The documentation does not contain interactive targets

Exceptions(s):

Bug 38572999 - Connections and Pipeline page shows icons less than 24 by 24 CSS pixels

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

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

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

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

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

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

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 always automatically met.

The WebUI and documentation were tested for:

• Help mechanisms (or a link to different software containing help mechanisms) occur in the same order relative to other software content.

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

• The documentation does not have input fields, except for the Search field

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

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:

• User input is not required.

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:

• Changes to data are not allowed.

The CLI and WebUI were tested for:

• Re-entering information previously entered by or provided to the user is essential.
• Re-entering information previously entered by or provided to the user is required to ensure the security of content.

The documentation was tested for:

• There are no occurrences of information that the user needs to enter which has been previously entered.

The CLI was tested for:

• The product supports copy and paste while authenticating.

The WebUI was tested for: 

• The product supports password entry by password managers.
• The product supports copy and paste while authenticating.

The documentation was tested for:

• Authentication is not required.

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.

Exception(s):

Bug 36850676 - Screen Reader reads Connections pagination control as undefined pagination region

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.

The CLI was tested for:

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

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.

There are no specific Accessibility features that require documentation.

Product Documentation is in electronic format.