Oracle Accessibility Conformance Report

The product was tested for:

• Controls, Input: Controls that accept user input are used. These controls do not have alternative text as they would be in conflict with the JSR.

• Time-Based Media: Prerecorded audio is used. There is no alternate presentation associated with this content as it would be in conflict with the JSR.

• Test : There is no non-text content that is used as a test or excercise.

• Content that creates a sensory experience is not used.

• CAPTCHAs are not used.

• Decoration, Formatting, Invisible: No such content is used.

The documentation was tested for:

• Non text content is not used in the Documentation.

The product was tested for:

• Prerecorded audio is used. There is no alternative as it would be in conflict with the JSR.
• Prerecorded video is not used.

The documentation was tested for:

• Audio/video content is not used for the Documentation.

The product was tested for:

• Prerecorded audio content is used. No captions are provided for this content as it would be in conflict with the JSR.

The documentation was tested for:

• No audio content is used for the Documentation.

The product was tested for:

• No video is used in the product.

The documentation was tested for:

• No video is used in the product.

The product was tested for:

• No live audio content in video is being used

The documentation was tested for:

• No live audio content in video is being used

The product was tested for:

• There is no pre-recorded video

The documentation was tested for:

• There is no pre-recorded video

The product was tested for:

• Lists are contained within a List component

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

The product was tested for:

• The accessibility hierarchy is logical.

The documentation was tested for:

• The sequence of elements 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 was tested for:

• Sensory characteristics are not used or relied upon.

The product was tested for:

• Content does not restrict its view and operation to a single display orientation.

The documentation was tested for:

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

The product was tested for:

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

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 text formats.

The documentation was tested for:

• Information is not conveyed using color.

The product was tested for:

• No automatically playing audio is used.

The documentation was tested for:

• No automatically playing audio is used.

The product was tested for:

• Text has a contrast ratio of at least 4.5:1
• This product does not have user selected contrast and color selections.

The documentation was tested for:

• Text has a contrast ratio of at least 4.5:1 when seen in the browser.

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

• Images of text are not used.

The documentation was tested for:

• Images of text are not used.

The product was tested for:

• Content can be presented without loss of information or functionality
• 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.

The product was tested for:

• The visual presentation of the user interface components 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:

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

• There is no content that appears on hover or focus.

The product was tested for:

• Ability to perform functions from the keyboard only.
• Logical movement of focus through the controls.
• The GUI is usable through mouse and keyboard input.

The documentation was tested for:

• Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes.

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.
• Keyboard focus is not used.

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:

• There are no single character keyboard shortcuts.

The documentation was tested for:

• There are no single character keyboard shortcuts.

The product was tested for:

• Time limits in the product can be turned off before they are encountered.
• Time limits in the product can be adjusted to at least 10 times longer before encountered.
• Time limits used are part of a real-time event, or an essential activity.

The documentation was tested for:

• Time limits are not used.

The product was tested for:

• There is no moving, blinking or scrolling content
• There IS auto-updated text (Auto updated data is for progress indication only)

While non-critical,  'auto-updated text' currently can not be hidden in all JavaTest UIs that support progress indication. 

Exception:

Bug CODETOOLS-7900303: 'auto-updated text' currently can not be hidden in all JavaTest UIs that support progress indication.

(publicly available by searching https://bugs.openjdk.java.net)

The documentation was tested for:

• There is no moving, blinking or scrolling 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 ‘Contents’ link is provided to skip repetitive navigation links at the top of the page.

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:

• Links are used in the GUI. The text of links and their surrounding context is sufficient to describe their purpose.

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.

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 are in a site table of contents.
• Pages are fully inter-linked to each other.

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:

• No keyboard operable controls are used.

The product was tested for:

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

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, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion.

The documentation was tested for:

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

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

The documentation was tested for:

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

The product was tested for:

•  Functionality that can be operated by device motion.

The documentation was tested for:

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

The product was tested for:

• Locale/language settings are not used by the product.

The documentation was tested for:

• Properly set lang attribute for each page.

The product was tested for:

• Locale/language settings are not used by the product.

The documentation was tested for:

• Proper use of 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:

• No input controls are used in documentation.

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.

The product was tested for:

• Proper descriptive error messages that identify the item in error.

The documentation was tested for:

• No input controls are used in the Documentation.

The product was tested for:

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

The documentation was tested for:

• No input controls are used in the Documentation.

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:

• No input controls are used in the Documentation.

The product was tested for:

• There are no Legal, Financial, or Data inputs.

The documentation was tested for:

• There are no Legal, Financial, or Data inputs.

The product was tested for:

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

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

• User interface components have a programmatically associated name and role.
• 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’.
• Frames have a meaningful title specified in the title attribute.

The product was tested for:

• There are no status messages.

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

• Respect of platform settings for color, contrast, font type, font size, and focus cursor.
• JCK supports this criterion via the JavaTest Harness User Interface.

The product was tested for:

• JCK contains audio only content that does not have captions as it would be a conflict with the JSR. As a result, the controls for captions does not apply.

The product was tested for:

• JCK contains audio only content that does not have captions due to it would be a conflict with the JSR. As a result, the controls for audio description does not apply.

The JCK User's Guide chapter 8 "Java Compatibility Kit Accessibility Information" includes a description of Platform features for accessibility and how these may be used with assistive technology. User's Guide is bundled with the product.

JCK 15 provides documentation in electronic formats only.

JCK support is through the Java Licensing (JLE) organization.  They provide a support engineer email and phone number per licensee. That person can provide information about accessibility features of the product.

JCK customers have access to electronic support through email with their assigned support engineer provided by the JLE organization. Hearing-impaired customers in the U.S. who wish to speak to their assigned support engineer 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.