Oracle Accessibility Conformance Report

The product was 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
• Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table), or the containers of the complex images are filled with simple image children whose information is exposed via AccessibleName and/or AccessibleDescription
• Data tables include a summary or caption, programmatically connected with the table as the AccessibleTable's AccessibleSummary
• Controls have an AccessibleName, or a label control with an AccessibleName has been programmatically associated with it
• Time-based media is not used
• Non-text characters are not used
• CAPTCHAs are not used

Exceptions:

• Bug 37374792: Due to Java Swing bug VoiceOver control option left/right arrow doesn't move between menus on macOS. Suggested workaround is to use the macOS menu system by starting with -Dapple.laf.useScreenMenuBar=true
• Bug 37541541: Due to Java Swing bug VoiceOver doesn't announce untick on toggling the checkbox with "space" key on macOS
• Bug 37370736: Due to JPopupMenu Java Swing bug VoiceOver reading incorrect number of items in submenu of JPopupMenu on macOS
• Bug 37374434: Due to Java Swing bug VoiceOver reads the spinner value 10 as 1 when user iterates to 10 for the first time on macOS
• Bug 37374706: Due to Spinner Java Swing bug VoiceOver reads the spinner value wrong and sometime partially on macOS
• Bug 37375466: Due to JTree Java Swing bug VoiceOver missed or incorrectly announced on JTree on macOS
• Bug 37370890: Due to JTabbedPane Java Swing bug VoiceOver missed or incorrectly announced on tab items of JTabbedPane on macOS

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
• 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 product was 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
• Style sheets are used only to change the layout and presentation on the screen
• 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

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

• The accessibility hierarchy is logical

The documentation was tested for:

• HTML markup and coding of text that provides a correct and 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 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 product was tested for:

• Text is displayed in both device orientations without loss of functionality or visibility of the text.
• The view and operation are an application function allowed by Operating System. Java UI Toolkit (Swing) neither enable nor prevent an application supporting this.

The documentation was tested for:

• Text is displayed in both device orientations without loss of functionality or visibility of the text.
• The view and operation are a function allowed by browser. The JavaDoc API documentation is working in a browser: If orientation works for the browser, then it works for the JavaDoc API documentation.

The product was tested for:

• Text fields which collect information about the user contain the appropriate autocomplete content attribute.
• Input Purpose identification and Auto-complete are an application function allowed by Operating System. Java UI Toolkit (Swing) neither enable nor prevent an application supporting this.

The documentation was tested for:

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

The product 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
• Information conveyed by color has a contrast ratio of at least 3:1

The product was testing 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 product was tested for:

• Text resizes up to 200% using the platform's Large Print or enlarged font setting
• Text (and application) resizes up to 200% using the platform's built-in magnifier or zoom feature

The documentation was tested for:

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

The product was tested for:

• Images have meaningful alternative text and repeated images and icons have a consistent alternate text.

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 product 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.
• An alternative mobile user interface is available and is accessed from the main application.
• Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.
  • JavaDoc API documentation has instances where there will be scrolling both horizontally and veritically due to fully qualified method names having no spaces and so can't flow to the next line.

The product was tested for:

• Java2D and Swing provides enough APIs for an application to support this by doing its own text layout, but there's no high level UI components that do it, it means the application defines the mark up language
• The visual presentation of the User Interface Components and Graphical Objects have a contrast ratio of at least 3:1

The documentation was tested for:

• Non-text items have a contrast ratio of at least 3:1

The product was tested for:

• Java2D and Swing provides enough APIs for an application to support this by doing its own text layout, but there's no high level UI components that do it, it means the application defines the mark up language

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

• Dismissible -The content is dismissed when moving the pointer or keyboard focus
• Hoverable - When pointer hover triggers additional content, the pointer cannot be moved over the additional content without the additional content disappearing
• Persistent - The additional content does not remain visible when the hover or focus trigger is removed.
• Information appears on hover or focus using default browser behavior, such as the title attribute of components.

The product was tested for:

• The GUIs can be navigated by keyboard only.

Exceptions:

• Bug 37374792: Due to Java Swing bug VoiceOver control option left/right arrow doesn't move between menus on macOS. Suggested workaround is to use the macOS menu system by starting with -Dapple.laf.useScreenMenuBar=true
• Bug 37541541: Due to Java Swing bug VoiceOver doesn't announce untick on toggling the checkbox with "space" key on macOS

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
• The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms)

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

• Single character keyboard shortcuts can be turned off
• Single character keyboard shortcuts can be remapped
• Single character keyboard shortcuts are only active when that component has focus

The documentation was tested for:

• There are no single character keyboard shortcuts.

The product was tested for:

• Time limits are not used

The documentation was tested for:

• Time limits are not used

The product was tested for:

• Moving, blinking, scrolling information can be paused.

The documentation was tested for:

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

The product was tested for:

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

The documentation was 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 does not apply.

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

• The name of the software application is meaningful.

The documentation was tested for:

• Pages have a meaningful title specified in the <title> element.

The product was tested for:

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

The documentation was tested for:

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

The product was tested for:

• The text of links and their surrounding paragraph, list, 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, 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 does not apply.

The documentation was tested for:

• Pages can be found using the provided "search" function
• Pages are in a site table of contents
• Page contains controls that enable reaching all pages

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

The product was tested for:

• Visual indication of the location of the focus

The documentation was tested for:

• Visual indication of the location of the focus

The product was tested for:

• The component is not hidden due to user interface component content opened by the user

The documentation was tested for:

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

The product was tested for:

• Multipoint or path-based gesture actions can be completed using a different input modality.
• The multipoint or path-based gestures for operation and pointer actions are an application function allowed by Operating System. Java UI Toolkit (Swing) neither enable nor prevent an application supporting this.

The documentation was tested for:

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

The product 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
• When an operation uses a single pointer, the up-event reverses any outcome of the preceding down-event
• The pointer actions using a single pointer are an application function allowed by Operating System. Java UI Toolkit (Swing itself) neither enable nor prevent an application supporting this.

The documentation was tested for:

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

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

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 does not apply.

The documentation was tested for:

• All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging.

The product was tested for:

• The size of the User Interface target for pointer inputs

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 target is in a sentence or its size is otherwise constrained by the line-height of non-target text.

The product was tested for:

• Properly set locale/language

The documentation was tested for:

• Properly set "lang" attribute for each page

The product was 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 product was 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 documentation was 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 product was 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 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.

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 does not apply.

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

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 does not apply.

The documentation was tested for:

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

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

• The documentation does 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 was tested for:

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

The product was tested for:

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

The documentation was tested for:

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

The product was tested for:

• Submissions are generally reversible, and if they are complicated to reverse, Oracle JDK asks for confirmation from user before submission.

The documentation was tested for:

• Changes to data are not allowed.

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 does not apply.

The documentation was tested for:

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

The product and documentation were tested for:

• Authentication does not rely upon a cognitive functional test.

The product was tested for:

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

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 Java API documentation is generated by the javadoc tool using the Java source files as input. The tool produces accessible HTML if the input is well-formed.

The product was 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
• Event notification of changes to names, states, properties, and values is available to assistive technologies

Exceptions:

• Bug 37370736: Due to JPopupMenu Java Swing bug VoiceOver reading incorrect number of items in submenu of JPopupMenu on macOS
• Bug 37374434: Due to Java Swing bug VoiceOver reads the spinner value 10 as 1 when user iterates to 10 for the first time on macOS
• Bug 37374706: Due to Spinner Java Swing bug VoiceOver reads the spinner value wrong and sometime partially on macOS
• Bug 37375466: Due to JTree Java Swing bug VoiceOver missed or incorrectly announced on JTree on macOS
• Bug 37370890: Due to JTabbedPane Java Swing bug VoiceOver missed or incorrectly announced on tab items of JTabbedPane on macOS

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.

The product and documentation were tested for:

• There are no status messages.
• Java UI Toolkit (Swing itself) doesn't show mark up language features and Status messages as well.

Platform software provides user control over platform features defined in platform documentation covers the Java SE JDK on the Windows and macOS platforms.

We recommend developers use Swing controls whenever possible to implement accessible UI for their applications. Applications written using AWT will not be accessible.

The product was tested for:

• Software does not disrupt platform features that are defined in the platform documentation as accessibility features.

The product was 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
• Event notification of changes to names, states, properties, and values is available to assistive technologies

Exceptions:

• Bug 37370736: Due to JPopupMenu Java Swing bug VoiceOver reading incorrect number of items in submenu of JPopupMenu on macOS
• Bug 37374434: Due to Java Swing bug VoiceOver reads the spinner value 10 as 1 when user iterates to 10 for the first time on macOS
• Bug 37374706: Due to Spinner Java Swing bug VoiceOver reads the spinner value wrong and sometime partially on macOS
• Bug 37375466: Due to JTree Java Swing bug VoiceOver missed or incorrectly announced on JTree on macOS
• Bug 37370890: Due to JTabbedPane Java Swing bug VoiceOver missed or incorrectly announced on tab items of JTabbedPane on macOS

The product was tested for:

• State information, properties, and values are programmatically exposed for user interface components
• Event notification of changes to names, states, properties, and values is available to assistive technologies

The product was 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
• Style sheets are used only to change the layout and presentation on the screen
• 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

The product was tested for:

• State information, properties, and values are programmatically exposed for user interface components
• Event notification of changes to names, states, properties, and values is available to assistive technologies

The product was tested for:

• Event notification of changes to names, states, properties, and values is available to assistive technologies

The product was tested for:

• User interface component labels are associated with the fields they are labeling via the LabelFor and LabeledBy relations

The product was tested for:

• The accessibility hierarchy is logical

The product was tested for:

• User interface components that display text either:
  • Expose a copy of their text as the AccessibleName (e.g. the text of a JButton), and/or
  • Expose their text via the AccessibleText interface.

The product was tested for:

• User interface components that display text either:
  • Expose a copy of their text as the AccessibleName (e.g. the text of a JButton), and/or
  • Expose their text via the AccessibleText interface.

The product was tested for:

• Properly execute a list of actions

The product was tested for:

• Properly execute available actions on objects

The product was tested for:

• Visual indication of the location of the focus cursor, focus tracking, text insertion point and selection attributes
• 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
• Event notification of changes to names, states, properties, and values is available to assistive technologies

The product was tested for:

• Visual indication of the location of the focus modification

The product was tested for:

• Event notification of changes to names, states, properties, descriptions, boundaries and values is available to assistive technologies

The product was tested for:

• No automatically playing audio is used
• No Pre-recorded audio-only content is being used
• No live audio content is being used
• Enable sequential entry of multiple (chorded) keystrokes
• Provide adjustment of delay before key acceptance
• Provide adjustment of same-key double-strike acceptance

The product was tested for:

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

JDK 21 provides Java Access Bridge, Java Accessibility API (JAAPI), and Java Accessibility Utilities that enable you to create accessible applications. See Java Platform, Standard Edition Java Accessibility Guide for more information:

https://docs.oracle.com/en/java/javase/21/access/java-accessibility-overview.html

Product documentation is in electronic format.