Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Java Platform, Standard Edition, Development Kit 11 (Updated 2)

Product Description:

Oracle's implementation of the Java Standard Edition (SE) 11 Platform Specification as defined by JSR 384.

Oracle Java Development Kit (JDK) 11 is the next major release after JDK 10, Java Development Kit that contains the runtime (JVM and class libraries) as well as a collection of programming tools.

This VPAT covers the Oracle Java Platform, Standard Edition, Development Kit (Java SE JDK) on the Windows and Mac OS X platforms. Java SE JDK on the UNIX OS and Linux platforms does not conform to Accessibility guidelines and are not included in this VPAT.

Developers are required to use Swing controls whenever possible to implement accessible UI for their applications. Applications written using AWT, or JavaFX will not be accessible.

Date:

08-Feb-2021

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

  • Policy Tool
  • AWT applications and applets
  • PDF Documentation

In Windows, Java provides Access Bridge to allow access by Windows based Assistive Technology. 

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/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.1Level A - Yes
Level AA - Yes
Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018Yes

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 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 25961034: Due to no accessibility support for Java Swing's JTree on macOS VoiceOver says nothing as a JTree tree is navigated, expanded/collapsed, selected.
  • Bug 25961164: Due to ColorChoose Java Swing bug on macOS VoiceOver announces spin box control as radio button on macOS platform.
  • Bug 25961174: Due to Java Swing bug Checkbox toggles on Space press but is not spoken by VoiceOver. Suggested workaround: move focus away and back again.
  • Bug 25961063: Due to Java Swing bug nothing heard from VoiceOver when tabbing between a nested tab group and a parent tab group on macOS platform.
  • Bug 25961053: Due to Java Swing bug in UI tabbing, when in a tab group if you arrow between tabs there are no VoiceOver announcements on macOS platform.
  • Bug 25919240: Due to Java Swing's JTables bug accessible JTables always reported as empty on macOS platform. In case to click or use the keyboard to navigate the table, VoiceOver says nothing.
  • Bug 25961038: Due to Java Swing's bug VoiceOver reads percentages rather than the actual values for sliders on macOS platform.
  • Bug 25961113: Due to Java Swing's Combobox bug when focus is gained on a non-editable combo box VoiceOver does not read the value on macOS platform. VoiceOver doesn't read the contents of the combo box. Suggested workaround: hover the mouse over the Combobox control and try to switch or select from the list then user could hear the value.
  • Bug 31309238: Due to Java Swing's JSliders and JColorChooser bugs VoiceOver does not always announce the value of JSliders in JColorChooser

The documentation was tested for:

  • Images that convey information have meaningful alternative text using ALT or longer descriptive text in a separate page
  • 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)
  • Controls have an associated name
  • Time-based media is not used
  • Non-text characters are not used
  • CAPTCHAs are not used

The JavaDoc was tested for:

  • Images that convey information have meaningful alternative text using ALT or longer descriptive text in a separate page
  • 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)
  • Controls have an associated name
  • Time-based media is not used
  • Non-text characters are not used
  • CAPTCHAs are not used
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.4 Captions (Live) (Level AA)Not ApplicableThe product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)Not ApplicableThe product has no multimedia.
1.3.1 Info and Relationships (Level A)Supports

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:

  • 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
1.3.2 Meaningful Sequence(Level A)Supports

The product was tested for:

  • The accessibility hierarchy is logical

The documentation was tested for:

  • The sequence of elements in the DOM matches a logical reading sequence
1.3.3 Sensory Characteristics(Level A)Supports

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
1.3.4 Orientation (Level AA)Supports

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. Javadoc neither enable nor prevent a browser supporting this.
1.3.5 Identify Input Purpose (Level AA)Supports

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:

  • Javadoc itself doesn’t have any Input box, just links.
1.4.1 Use of Color(Level A)Supports

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
1.4.2 Audio Control(Level A)Not ApplicableThe product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)Supports

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:

  • Text and images of text have a contrast ratio of at least 4.5:1
1.4.4 Resize text(Level AA)Supports

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
1.4.5 Images of Text(Level AA)Supports

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
1.4.10 Reflow (Level AA)Supports

The product 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.
  • Javadoc has instances where there will be scrolling both horizontally and veritically due to fully qualified method names have no spaces and so can't flow to the next line.
1.4.11 Non-text Contrast (Level AA)Supports

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:

  • The visual presentation of the User Interface Components and Graphical Objects have a contrast ratio of at least 3:1
1.4.12 Text Spacing (Level AA)Supports

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:

  • 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
1.4.13 Content on Hover or Focus (Level AA)Supports

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:

  • There is no content that appears on hover or focus.
2.1.1 Keyboard(Level A)Partially Supports

The product was tested for:

  • The GUIs can be navigated by keyboard only.

Exceptions:

  • Bug 25961312: VoiceOver cursor doesn't track Swing keyboard focus on macOS. When using the menu system the VoiceOver cursor starts off on the first menu item but doesn't track focus when the arrow keys are used to move within a menu.
  • Bug 25919248: Alt doesn’t move to menubar; Alt + aKey doesn’t activate menu. Suggested workaround: F10 can be used to move to the menubar.

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)
2.1.2 No Keyboard Trap (Level A)Supports

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
2.1.4 Character Key Shortcuts (Level A)Supports

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.
2.2.1 Timing Adjustable(Level A)Supports

The product was tested for:

  • Time limits are not used

The documentation was tested for:

  • Time limits are not used
2.2.2 Pause, Stop, Hide (Level A)Supports

The product was tested for:

  • Moving, blinking, scrolling information can be paused.

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 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
2.4.1 Bypass Blocks(Level A)Supports

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:

  • Structure and hierarchy is marked up with Header elements outside of repetitive navigation links.
2.4.2 Page Titled(Level A)Supports

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
2.4.3 Focus Order(Level A)Supports

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.
2.4.4 Link Purpose (In Context)(Level A)Supports

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.
2.4.5 Multiple Ways(Level AA)Supports

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

  • Pages can be found using the provided "search" function
  • Page contains controls that enable reaching all pages

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
2.4.6 Headings and Labels(Level AA)Supports

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
  • Labels are not used
2.4.7 Focus Visible(Level AA)Supports

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
2.5.1 Pointer Gestures (Level A)Supports

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

  • There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)Supports

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, the up-event reverses any outcome of the preceding down-event
2.5.3 Label in Name (Level A)Supports

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 with labels that include text or images of text, the name contains the text that is presented visually
2.5.4 Motion Actuation (Level A)Supports

The product and documentation were tested for:

  • There are no functions that require motion of the device.
3.1.1 Language of Page(Level A)Supports

The product was tested for:

  • Properly set locale/language

The documentation was tested for:

  • Properly set lang attribute for each page
3.1.2 Language of Parts(Level AA)Supports

he 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.
3.2.1 On Focus(Level A)Supports

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
3.2.2 On Input(Level A)Supports

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:

  • User interface components are not used
3.2.3 Consistent Navigation(Level AA)Supports

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

  • There are no navigational mechanisms that are repeated

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 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
3.3.1 Error Identification(Level A)Supports

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.
3.3.2 Labels or Instructions (Level A)Supports

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
3.3.3 Error Suggestion (Level AA)Supports

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:

  • The documentation does not have input fields, except for the Search field.
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)Supports

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:

  • The documentation does not allow for changes to data.
4.1.1 Parsing(Level A)Supports

The product was tested for:

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

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 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
4.1.2 Name, Role, Value (Level A)Supports

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

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)Supports

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.

back to top

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria
Conformance Level
Remarks and Explanations
302.1 Without VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of ColorNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without SpeechNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited ManipulationNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and StrengthNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning AbilitiesNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

back to top

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 AASupportsSee the responses in the WCAG 2.0 section of this report.
 502 Interoperability with Assistive TechnologyHeading cell - no response requiredHeading cell - no response required
502.2.1 User Control of Accessibility FeaturesPartially Supports

Platform software provides user control over platform features defined in platform documentation covers the Java SE JDK on the Windows and Mac OS X platforms. Java SE JDK on the UNIX OS and Linux platforms does not conform to Accessibility guidelines and is not included in this VPAT.

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

502.2.2 No Disruption of Accessibility FeaturesSupports

The product was tested for:

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

 502.3 Accessibility ServicesHeading cell - no response requiredHeading cell - no response required
502.3.1 Object InformationSupports

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
502.3.2 Modification of Object InformationSupports

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
502.3.3 Row, Column, and HeadersSupports

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
502.3.4 ValuesSupports

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
502.3.5 Modification of ValuesSupports

The product was tested for:

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

The product was tested for:

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

The product was tested for:

  • The accessibility hierarchy is logical
502.3.8 TextSupports

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.
502.3.9 Modification of TextSupports

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.
502.3.10 List of ActionsSupports

The product was tested for:

  • Properly execute a list of actions
502.3.11 Actions on ObjectsSupports

The product was tested for:

  • Properly execute available actions on objects
502.3.12 Focus CursorPartially Supports

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

Exception:

  • Bug 25961312: VoiceOver cursor doesn't track Swing keyboard focus on macOS. When using the menu system the VoiceOver cursor starts off on the first menu item but doesn't track focus when the arrow keys are used to move within a menu.
502.3.13 Modification of Focus CursorSupports

The product was tested for:

  • Visual indication of the location of the focus modification
502.3.14 Event NotificationSupports

The product was tested for:

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

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
 503 ApplicationsHeading cell - no response requiredHeading cell - no response required
503.2 User PreferencesSupports

The product was tested for:

  • Responds to platform settings for color, contrast, font type, font size, and focus cursor
503.3 Alternative User InterfacesNot ApplicableThe product does not have assistive technology features.
 503.4 User Controls for Captions and Audio DescriptionHeading cell - no response requiredHeading cell - no response required
503.4.1 Caption ControlsNot ApplicableThe product has no multimedia.
503.4.2 Audio Description ControlsNot ApplicableThe product has no multimedia.
 504 Authoring ToolsHeading cell - no response requiredHeading cell - no response required
504.2 Content Creation or EditingNot ApplicableThe product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot ApplicableThe product is not an authoring tool.
504.2.2 PDF ExportNot ApplicableThe product is not an authoring tool.
504.3 PromptsNot ApplicableThe product is not an authoring tool.
504.4 TemplatesNot ApplicableThe product is not an authoring tool.

back to top

Chapter 6: Support Documentation and Services

Criteria
Conformance Level
Remarks and Explanations
 602 Support DocumentationHeading cell - no response requiredHeading cell - no response required
602.2 Accessibility and Compatibility FeaturesSupports

JDK 11 provides Java Access Bridge, Java Accessibility API (JAAPI), and Java Accessibility Utilities to enable you to create accessible applications. Java Accessibility Guide is here: https://docs.oracle.com/javase/11/access/java-accessibility-overview.htm

602.3 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support DocumentationNot Applicable

Product documentation is in electronic format.

 603 Support ServicesHeading cell - no response requiredHeading cell - no response required
603.2 Information on Accessibility and Compatibility FeaturesSupportsOracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication NeedsSupportsOracle 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.

back to top

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.