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

The product was tested for:

• No Pre-recorded audio-only or video-only content is being used

The product was tested for:

• No Pre-recorded video content is being used

The product was tested for:

• No pre-recorded video is being used

The product was tested for:

• No live audio content in video is being used

The product was tested for :

• No pre-recorded video is being 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 product was tested for:

• The accessibility hierarchy is logical

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

• No automatically playing audio is used

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

• Images of text are not used

The product is composed of components that have full keyboard operation implemented as documented in the Appendix A Keyboard Shortcuts, Mnemonics, and Other Keyboard Operations of the Java Look and Feel Design Guidelines. Where the product uses components developed after this document was published, those components use the WAI-ARIA Keyboard Bindings and Behaviors, or other keyboard operation as documented in the product documentation.

The product was tested for:

• ability to perform functions from the keyboard only
• logical movement of focus through the controls
• proper operation of unique keystrokes, including those listed in the product documentation

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 product 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 product 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 is always automatically met.

The product was tested for:

• The name of the software application is meaningful.

The product was tested for:

• Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence, as per the Appendix A Keyboard Shortcuts, Mnemonics, and Other Keyboard Operations section of the Java Look and Feel Design Guidelines, or where appropriate the WAI-ARIA Keyboard Bindings and Behaviors, or other keyboard operation as documented in the product documentation.

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

1.) JavaTest serves a web page that allows a user to control and monitor test execution.  Links on this page follow this guideline, and provide link context by setting accessible strings. All assistive strings are manually evaluated as part of the JavaTest QA process. Also, The QA team randomly surveys HTML content and inspects HTML constructs for alternate string content.

2.) A The same HTML help content (that used to be displayed in JavaHelp) is now rendered in the (users specified) default browser

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 always automatically met.

The product was tested for:

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

Exception:

Bug JDK-4512626: Non-editable JTextArea provides no visual indication of keyboard focus

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

The product was tested for:

• Visual indication of the location of the focus

The product was tested for:

• Properly set locale/language

The product was tested for:

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

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

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 always automatically met.

The product was tested for:

• Images and controls are used and identified consistently throughout the product

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

• Data is checked for input errors with an opportunity for the user to correct them
• Data can be reviewed, corrected, and confirmed by the user before they are finalized

The product was tested for:

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

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

• (No) disruption of platform features that are defined in the platform documentation as accessibility features.

The product was tested for :

• Respect of platform settings for color, contrast, font type, font size, and focus cursor.

Documentation was not updated on this release, and does not fulfill the requirement to provide explanation of accessibility and compatibility features required by the Hardware and Software guidelines.

JBS issue CODETOOLS-7902122 has been submitted, to account for required doc changes for the updated accessibility guidelines.

JavaTest Harness 5.0 only provides documentation in electronic formats.

JavaTest 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.

JavaTest 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.