Oracle Accessibility Conformance Report

The product was tested for:

• Functional images have alternative text.
• Consistency of bitmaps, symbols and icons.
• 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
• Non-text characters are not used or have meaningful alternative text
• CAPTCHAs are not used

The documentation was tested for:

• Images that convey information have meaningful alternative text by using ALT or a link to a page containing a text description of the image
• Images that are decorative are marked up using ALT=”” or CSS background images
• Non-text characters are not used
• CAPTCHAs are not used

The product was tested for:

• The product does not use HTML/Style sheets/Flash/Silverlight/scripts etc to present information.
• Lists are contained within a List Component
• Assistive Technology (AT) is used to test that labels for controls are correctly organized.

Exception (bug 31519439) : JOverflow parses a heap dump and  presents it in a tabular format. This tabular information from JOverflow Tab is not fully accessible

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

The product was tested for:

• The AT reading sequence matches the logical reading sequence

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

• The view and operation are an application function allowed by Operating System, not a Toolkit one. We 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 product and 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 conveyed by color is available in alternative text formats.

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

Exception (bug 25296447): The Flight Recorder UI contains a page which is named "Java Application" which displays e.g. thread activity. This graph contains information about events occurring in different threads, but the contrast between the colors of the events and the backdrop can be too low. Suggested workaround: view the data in any of the alternative forms, e.g. as table data (text) in the "Event Browser" page.

Exception (bug 32246564): The Flight Recorder UI contains a page named "Threads" which is graphical representation of thread lanes and JFR events on threads . This graph contains information about events occurring in different threads, and contains some buttons and fields for zoom in/out, and filtering threads lines.  The contrast between the colors of the buttons, text fields and the backdrop can be too low. Suggested workaround: view the data in any of the alternative forms, e.g. as table data (text) in the "Event Browser" page.

The documentation was tested for:

• 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

The documentation was tested for:

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

Images of text are not used in the product.

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 content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions

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

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

Exception (bug 25296447): The Flight Recorder UI contains a page which is named "Java Application" which displays e.g. thread activity. This graph contains information about events occurring in different threads, but the contrast between the colors of the events and the backdrop can be too low. Suggested workaround: view the data in any of the alternative forms, e.g. as table data (text) in the "Event Browser" page.

Exception (bug 32246564): The Flight Recorder UI contains a page named "Threads" which is graphical representation of thread lanes and JFR events on threads . This graph contains information about events occurring in different threads, and contains some buttons and fields for zoom in/out, and filtering threads lines.  The contrast between the colors of the buttons, text fields and the backdrop can be too low. Suggested workaround: view the data in any of the alternative forms, e.g. as table data (text) in the "Event Browser" page.

The documentation was tested for:

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

The product and documentation were tested for:

• In content implemented using markup language, 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: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
• Hoverable: If pointer hover can trigger the additional content, then 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
• proper operation of unique keystrokes, including those listed in the product documentation
• the ability to use the keyboard aids StickyKeys, ToggleKeys and FilterKeys

Exception (bug 25290049): In some tables it is not possible to change the width of the column using the keyboard only. Suggested workaround: Make JMC as large as possible. If text is still not visible it is possible to copy the text of one or more rows and then paste it into e.g. a text editor.

Exception (bug 25296303): In the JMX Console you can add a custom chart for an MBean value. If this MBean value is unknown to JMC, the user needs to specify the type of the MBean attribute, so that a correct y-axis can be displayed. When the user needs to do this, the dialog that appears is trickier to use with keyboard only. With a mouse you can click on a column and select a suitable unit in a combobox. With the keyboard you can't move the focus to this column. Suggested workaround: Make sure the row is selected and then produce the context menu. The suitable unit can be selected in the menu that appears.

Exception (bug 25289821): You can create custom pages in the flight recorder UI. If you create a custom page and use the keyboard to navigate it, the button "Group by" cannot be reached by tabbing. Suggested workaround: Access the feature using the context menu instead.

Exception (bug 25296409): In JDK Mission Control, the user interface for flight recordings contain a page named "Automated Analysis Result". The page has two variants: one with a simple table, and one with a column based page layout. On the latter variant of this page, you cannot use the keyboard to expand and/or collapse the displayed rule results. Suggested workaround: Use the alternative view of the page, where the information is displayed in a table. (The table view is the default view when accessibility mode has been enabled in Preferences in JMC).

Exception (bug 25289977): The Flight Recorder UI contains some charts. If you use a mouse you can select parts of the charts, but this is not possible if you are using keyboard only. Suggested workaround:

1. Move the focus to the chart you would like to make a selection in.
2. When the chart has the focus, select "Store and Set as Focused Selection" in the context menu.
3. Change to the "Event Browser" page.
4. Verify that the selection you made is still selected at the top. Uncheck the checkbox "Show concurrent".
5. All events from the chart are now listed in the table below. Select the part you wanted select in the table.
6. If you wish, return to the chart with this selection.

Exception (bug 32246564): In JDK Mission Control, the user interface for flight recordings contain a page named "Threads" which is graphical representation of thread lanes and JFR events on threads, Its not possible to make selections within the graph or editing the thread lanes within this graph, suggested work around is to view the data from in Event Browser page. 

Exception (bug 32269279): Coherence Tab Pack is an extensible plugins by Oracle on JMC's  JMX Console Tab.This is not part of Standard JMC application, but users can install them based on requirement. Coherence Tab Pack provides visualizations for Custom JMX Beans sent by Coherence Cache Cluster/Server to JMC. It contains sub tabs for showing details of Machines, Members, Services, Caches etc in a running Coherence Cluster. The sub tabs under the main Coherence Tab are not navigable, as focus does not reach on these tabs. suggested work around is to view the data from MBean Browser

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:

• A mechanism is available to turn the shortcut off;
• A mechanism is available to remap the shortcut to use one or more non-printable keyboard character
• 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 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:

• Moving, blinking, or scrolling information that is designed to last for more than three seconds can be paused.
• Moving, blinking, or scrolling content that isn't a pure decoration is part of an essential activity.

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:

• 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

Exception (bug 25289821): You can create custom pages in the flight recorder UI. If you create a custom page and use the keyboard to navigate it, the button "Group by" cannot be reached by tabbing. Suggested workaround: Access the feature using the context menu instead.

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 context is sufficient to describe their purpose

The documentation was tested for:

• The text of links and their surrounding context 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 for the product.

The documentation was tested for:

• Pages can be found using the provided "search" function
• Pages are in a site table of contents

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

The product was tested for:

• Visual indication of the location of the focus

Exception (bug 25290139): The focus is not always visible in tables with 0-1 rows. No workaround is suggested, other than treating the table as if it had focus even if it is not apparent in the UI. 

The documentation was tested for:

• Visual indication of the location of the focus

The product was tested for:

• functionalities that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture

Exception (bug 25289977): The Flight Recorder UI contains some charts. If you use a mouse you can select parts of the charts, but this is not possible if you are using keyboard only. Suggested workaround:

1. Move the focus to the chart you would like to make a selection in.
2. When the chart has the focus, select "Store and Set as Focused Selection" in the context menu.
3. Change to the "Event Browser" page.
4. Verify that the selection you made is still selected at the top. Uncheck the checkbox "Show concurrent".
5. All events from the chart are now listed in the table below. Select the part you wanted select in the table.
6. If you wish, return to the chart with this selection.

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

The documentation was tested for:

• There are no single pointer operations

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

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

The product was tested for:

• Properly set locale/language

The documentation was tested for:

• Properly set language 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 language 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 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

The documentation was tested for:

• User interface components are not used

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 for the product.

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:

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

• The documentation does not have input fields, except for the Search field.

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

• The documentation does not allow for changes to data.

The product was tested for:

• Markup languages are used internally in ways never available to assistive technology or to a user agent

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.

The product was tested for:

• Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus.

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:

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

The product documentation describes:

• Accessibility modes, either at installation or runtime
• Special keystrokes needed to operate controls
• Workarounds

Find accessibility-related documentation in the online help; see the section "Accessibility in JDK Mission Control". Alternatively, see "Accessibility in Java Mission Control" in Java Platform, Standard Edition Java Mission Control User's Guide:

https://docs.oracle.com/en/java/java-components/jdk-mission-control/8/user-guide/index.html

Product documentation is in electronic format.