Oracle Accessibility Conformance Report

The product was tested for:

• Images are not used
• CAPTCHAs are not used

The documentation and JavaDoc 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
• Controls have an associated name
• Time-based media is not used
• Non-text characters are not used
• CAPTCHAs are not used

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

The documentation and JavaDoc were 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
• Groups of components are marked up with their description
• Style sheets are used only to change the layout and presentation on the screen

The product was tested for:

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

The documentation and JavaDoc were tested for:

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

The product 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 documentation and JavaDoc were tested for:

• Instructions provided which refer to graphics included a reference to the text alternative of the graphic

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

The documentation and JavaDoc were tested for:

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

The product was tested for:

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

The documentation and JavaDoc were tested for:

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

The product was tested for:

•  Information is not conveyed using color

The documentation and JavaDoc were 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 product was tested for:

• The text has a contrast ratio of at least 4.5:1

The JavaDoc was tested for:

• The text has 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 texts and images of text have a contrast ratio of at least 4.5:1

Exceptions:

Bug 28193474: Large-scale text and images of large-scale text have a contrast ratio lower than 3:1

The product 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 documentation and JavaDoc were tested for:

• Text can be resized up to 200% without loss of content or functionality
• Text resizes up to 200% using the platform's Large Print or enlarged font setting
• Text resizes up to 200% using the platform's built-in magnifier or zoom feature

Exceptions:

Bug 28193464: Header menu button text gets cut with Firefox web browser view 200%. Suggested workaround: zoom in with the Chrome web browser.

The product and JavaDoc were 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

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 documentation and JavaDoc were tested for:

• Text information reflows so that only one direction of scrolling is required while at 400% zoom
• Content that requires a two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content
• Javadoc has instances that cannot flow to the next line, for example, fully qualified method names have no spaces. Scrolling horizontally and vertically will be required there

Exceptions:

Bug 33749742 - Javadocs at 400% zoom require horizontal and vertical scrolling for the text content.

The product was tested for:

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

The documentation and JavaDoc were tested for:

• The visual presentation of the User Interface Components and Graphical Objects have a contrast ratio of at least 3:1

The product was tested for:

• Text is not rendered using markup languages

The documentation and JavaDoc 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 the 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 product was tested for:

• There is no content that appears on hover or focus

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

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

The product was tested for:

• There are no single-character keyboard shortcuts

The documentation and JavaDoc were tested for:

• Single-character keyboard shortcuts are only active when that component has focus

The product, documentation, and JavaDoc were tested for:

• Time limits are not used

The product, documentation, and JavaDoc were tested for:

• There is no moving, blinking or scrolling content.

The product, documentation, and JavaDoc were tested for:

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

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 and JavaDoc were tested for:

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

The product was tested for:

• The name of the software application is meaningful

The documentation and JavaDoc were tested for:

• Pages have a meaningful title specified in the TITLE element

The product, documentation, and JavaDoc were tested for:

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

Exceptions:

Bug 28192865: The focus is invisible when using Tab and Control buttons to navigate around the website in Firefox browser. Suggested workaround: start Firefox in Safe Mode; open the website from Chrome browser which highlights the focus location.

The product was tested for:

• Links are not used in the product

The documentation and JavaDoc were tested for:

• The text of links and their surrounding paragraph, list, table cell (with marked up table headers) is sufficient to describe their purpose

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 and JavaDoc were tested for:

• Pages are in a site table of contents
• Pages are fully inter-linked to each other

The product, documentation, and JavaDoc were tested for:

• Headers describe the topic or purpose of the content below them.
• Labels describe the purpose of the associated field.

The product, documentation, and JavaDoc were tested for:

• Visual indication of the location of the focus

Exceptions:

Bug 28192865: The focus is invisible when using Tab and Control buttons to navigate around the website in Firefox browser. Suggested workaround: start Firefox in Safe Mode; open the website from Chrome browser which highlights the focus location.

The product, documentation, and JavaDoc were tested for:

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

The product was tested for:

• When an operation uses a single pointer, the up-event reverses any outcome of the preceding down-even

The documentation and JavaDoc were tested for:

• There are no single pointer operations

The product was tested for:

• User interface components are not used

The documentation and JavaDoc were tested for:

• User interface components with labels that include text or images of text, the name contains the text that is presented visually

The product, documentation, and JavaDoc were tested for:

• There are no functions that require motion of the device

The product was tested for:

• The product only runs in English, therefore it is expected that the user is also running their assistive technology in English, where applicable

The documentation and JavaDoc were tested for:

• Properly set lang attribute for each page

The product was tested for:

• The product only runs in English, therefore it is expected that the user is also running their assistive technology in English, where applicable.

The documentation and JavaDoc were tested for:

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

The product, documentation, and JavaDoc 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 product was tested for:

• In circumstances where changing the value of the components causes a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window, warning is given prior to the user interacting with those user-interface components

The documentation and JavaDoc 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

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 and JavaDoc 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 product was tested for:

• Images and controls are not used

The documentation and JavaDoc were tested for:

• Images and controls are used and identified consistently

The product was 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 and JavaDoc were tested for:

• The documentation and JavaDoc do not have input fields, except for the Search field

The product was tested for:

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

The documentation and JavaDoc were tested for:

• Content does not require user input

The product was tested for:

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

The documentation and JavaDoc were tested for:

• Content does not require user input

The product was tested for:

• Submissions can be reversed by the user
• Data can be reviewed, corrected, and confirmed by the user before they are finalized

The documentation and JavaDoc were tested for:

• The documentation and JavaDoc do not allow for changes to data

The product was tested for:

• Markup languages aren not used to generate the user interface

The documentation and JavaDoc 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
• Pages validate to the HTML specification

The product was tested for:

• User interface components are not used

The documentation and JavaDoc were tested for:

• HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
• Frames have a meaningful title specified in the title attribute

The product, documentation and JavaDoc were tested for:

• There are no status messages

The product was tested for:

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

The product was tested for:

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

Oracle JDK 17 provides Access Bridge to allow access by Windows based Assistive Technology. To activate accessibility features on Microsoft Windows systems, refer to the Java Accessibility Guide.

Product documentation is in electronic format