Oracle Accessibility Conformance Report

The CLI was tested for:

• Images are not used
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

Java GUIs were tested for:

• Images that convey information are embedded within standard user interface components and have a meaningful AccessibleName and/or AccessibleDescription
• Images that are decorative are embedded within standard user interface components and have neither an AccessibleName nor an AccessibleDescription
• Controls have an AccessibleName, or a label control with an AccessibleName has been programmatically associated with it
• 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
• Images that are decorative are marked up using ALT=”” or CSS background images
• 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 CLI was tested for:

• Headings follow standard text patterns for rendering headings
• Lists follow standard text patterns for rendering lists

Java GUIs were tested for:

• User interface component labels are associated with the fields they are labeling via the LabelFor and LabeledBy relations
• Headings are marked as such with a Group relation from the header to the items beneath the header
• Groups of components are marked as such,with a Group relation from the header of the group to the members of the group
• Lists are contained within a List component
• Tables are contained within a Table component,implement the AccessibleTable interface,provide an AccessibleSummary,and contain include row and column headers where appropriate

Following bugs found in Java GUIs:

• Bug 39044499 : Screen Reader Reads Entire Line Instead of Selected Value for "configure scope wizard" under Analyze option
• Bug 39044986 : Checkbox Labels Not Read by Screen Reader in Visual Navigator
• Bug 39044935 : Dropdown Values Not Read by Screen Reader in File Converter Settings
• Bug 39045012 : Textbox Labels Not Read by Screen Reader in Configuration Wizard and other Wizards as well where Textbox filed is there

The Documentation was tested for:

• Data tables specify SUMMARY or CAPTION
• Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate
• Layout tables use appropriate markup
• Headings are encoded with HTML heading tags
• List markup is used for marking up lists

The CLI was tested for:

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

Java GUIs were tested for:

• The accessibility hierarchy is logical

The Documentation was tested for:

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

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 sounds

Java GUIs 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

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, colour, or sound
• Instructions provided which refer to graphics included a reference to the text alternative of the graphic

The CLI , Java GUIs  and Documentation were tested for:

• Text is displayed in both device orientations without loss of functionality or visibility of the text.

The CLI and Documentation were tested for:

• There are no text fields that collect information about the user.

Java GUIs were tested for:

• Text fields which collect information about the user contain the appropriate autocomplete content attribute.

The CLI and Documentation were tested for:

• Information conveyed by color is available in text

Java GUIs were tested for:

• Information conveyed by color is available in alternative formats,such as shape,text and font weight
• Information conveyed by color has a contrast ratio of at least 3:1

The CLI was tested for:

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

Java GUIs 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 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

Java GUIs was tested for:

• Text resizes up to 200% using the platform's Large Print or enlarged font setting

The Documentation was tested for:

• Text can be resized up to 200% without loss of content or functionality

The CLI , Java GUIs and Documentation were tested for:

• Images of text are not used

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 Java GUIs and Documentation were 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 CLI was tested for:

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

The Java GUIs 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 Java GUIs were tested for:

• The product does not have content implemented using markup languages that support editing the text style properties in this criteria.

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

The Java GUIs 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 CLI and Documentation were tested for:

• There is no content that appears on hover or focus

The CLI and Java GUIs were tested for:

• Ability to perform functions from the keyboard only
• Proper operation of unique keystrokes and access keys, including those listed in the product documentation
• logical movement of focus through the controls

Following defects were found:

• Bug 39045070 : Dropdown in DB2 datafile Table Column Not Accessible via Keyboard in Reload DB2 Data / Reload DBFileData Wizard
• Bug 39044563 : Dropdown Not Appearing with Keyboard for "Type" column value in configure scope Wizard

The Documentation 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 CLI and Java GUIs 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 Documentation was tested for :

• Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control

The CLI ,Java GUIs and Documentation were tested for:

• There are no single character keyboard shortcuts

The CLI , Java GUIs and Documentation were tested for:

• Time limits are not used

The Web GUI, Non-web GUI, CLI and Documentation were tested for:

• There is no moving, blinking, scrolling or auto-updating content.

The CLI , Java GUIs  and Documentation were tested for:

• No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz.

The CLI and Java GUIs 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 Documentation was tested for:

• Structure and hierarchy are marked up with Header elements outside of repetitive navigation links

The CLI , Java GUIs and Documentation were tested for:

• Pages have a meaningful title specified in the TITLE element.

The CLI was tested for:

• Keyboard focus is not used

The Java GUIs 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 and Java GUIs were tested for:

• Links are not used in the product

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

The CLI and Java GUIs 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 Documentation was tested for:

• Pages can be found using the provided "Search" function.
• Pages are in a site table of contents.
• Pages contain controls that enable reaching other pages

The CLI , Java GUIs 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 , Java GUIs and Documentation were tested for:

• Visual indication of the location of the focus

The CLI was tested for:

• Keyboard focus is not used

The Java GUIs 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 , Java GUIs and Documentation were tested for:

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

The CLI and Java GUIs were tested for:

• There are no single pointer operations.

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

The CLI was tested for:

• There are no user interface components labeled with text or images of text.

The Java GUIs and Documentation 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

The CLI ,Java GUIs and Documentation were tested for:

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

The CLI , Java GUIs and Documentation were tested for:

• There is no functionality that uses dragging movements.

The CLI was tested for:

• The CLI does not contain interactive targets.

The Java GUIs were 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:

• 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 function can be achieved through a different control in the same software that meets this criterion.
• The target is in a sentence or its size is otherwise constrained by the line-height of non-target text.

The CLI was tested for:

• English is used for the locale/language setting, therefore it is expected that the user is also running their assistive technology in English, where applicable.

The Java GUIs were tested for:

• Properly set locale/language.

The Documentation was tested for:

• Properly set "lang" attribute for a given page.

The CLI was tested for:

• English is used for the locale/language setting, therefore it is expected that the user is also running their assistive technology in English, where applicable.

The Java GUIs were tested for:

• Properly set locale/language for text passages that are in a different language than that of the software.

The Documentation was tested for:

• Proper use of the “lang” attribute for text passages that are in a different language than that of the page

The CLI was tested for:

• Keyboard focus is not used.

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

• User interface components are not used.

The Java GUIs and Documentation were tested for:

• Changes in the value of user interface components 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 CLI and Java GUIs 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 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.

The CLI was tested for

• Images and controls are not used

Java GUIs 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 documentation

The CLI , Java GUIs  and Documentation were tested for:

• None of the following help mechanisms exist: Human contact details, human contact mechanisms, self-help options, automated contact mechanisms.

The CLI and Java GUIs were tested for:

• When input errors are detected, they are described to the user in text, including identifying the item where the error occurs

The Documentation was tested for:

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

The CLI , Java GUIs and Documentation were tested for:

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

The CLI and Java GUIs 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 does not require user input, except for the Search field

The CLI and Java GUIs were 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:

• The documentation does not require user input that modifies user controllable data.

The CLI, Java GUIs and Documentation were tested for:

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

The CLI, Java GUIs and Documentation were 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 Java GUIs were tested for:

• User interface components have a programmatically associated AccessibleName and AccessibleRole as defined by the Java Accessibility API
• State information, properties, and values are programmatically exposed for user interface components

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 a meaningful programatically exposed name
• Frames have a meaningful title specified in the title attribute

Following defect was found:

• Bug 39056533 : Script links not navigable to sub-sections

The CLI, Java GUIs and Documentation were tested for:

• There are no status messages.

The CLI, Java GUIs and Documentation were tested for:

• Does not disrupt platform accessibility features such as sticky keys, high contrast and large fonts.

The CLI, Java GUIs and Documentation were tested for:

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

The product documentation does not contain a dedicated section describing accessibility or compatibility features. The application relies primarily on accessibility capabilities provided by the underlying operating system and the Eclipse platform. Assistive technologies such as screen readers, keyboard navigation, and display customization are supported through these platforms. Users should consult the operating system and Eclipse documentation for instructions on enabling and using these accessibility features.

Bug 39056533 : Documentation does not include a dedicated section describing accessibility and compatibility features

Product documentation is in electronic format.