Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Java Platform, Standard Edition, Development Kit (Java SE JDK) updated3 8u65/8u66

Product Description:

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

Oracle Java Development Kit (JDK) 8u60 is an update release of JDK 8, 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 platform does not conform to Accessibility guidelines and is not included in this VPAT.

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

The following are known exceptions:

Installer (excluding MAC OS) Outages:

JDK-7058227 Images on the installer (Sponsor Dialog) do not have meaningful alternative text
JDK-8081477 Using High Contrast color scheme, text in some JDK dialogs have hard-to-read foreground/background colors

Swing UI Outages:

JDK-7181878 JFileChooser does not fully implement/reflect Windows' High Contrast mode
JDK-8025804 NPE when JAWS is running and press backspace in bugster password entry field
JDK-8036043 Fusion Middleware Upgrade Assistant: NPE when using JAWS

Mac OS Platform Outages:

JDK-7124281, JDK-7124221, JDK-7124293, JDK-7124297, JDK-7124526, JDK-7124292, JDK-7124291, JDK-7124301, JDK-7124285, JDK-7124284, JDK-7124298, JDK-7124280, JDK-8028225, JDK-8031587, JDK-8027707, JDK-8061381, JDK-8061379, JDK-8061359 - Voice Over related bugs.
JDK-7124240 Multi-select lists and trees are unusable by people using screen readers
JDK-7124241 No Visual indication when button or check box is focused
JDK-7124299, JDK-7124527 SwingSet2 Internal Frames Demo related bugs
JDK-8027385 JVM crash or hang when screen is zoomed
JDK-8061381 Accelerators do not spell for JMenultems by VoiceOver
JDK-8061379 JComboBox works strangely with VoiceOver
JDK-8061359 Checkbox toggles on Space press but does not spell by VoiceOver

Java Monitoring and Management Console

JDK-7043941 JConsole User Guide Link from the Help menu is not accessible by keyboard

Java FX

RT-39205 ListView selection range is not voiced at all
RT-39136 TableView contents of the whole row are not explorable
RT-39184 HelloTableView wrong check box selected (keyboard vs Mouse Focus Selection)
RT-39111 In HelloMenu Sample, when using Left/Right Arrow keys to move along menu bar, the menu bar items are not spoken using JAWS or Narrator
RT-39109 DatePicker Under JAWS speaks the wrong date after using arrow keys to move highlighted date across month boundaries
RT-39070 Can't activate calendar popup of DatePicker when voice over is enabled
RT-39059 TreView CTRL+ Combinations does not read the newly focused item
RT-38532 Any selected item is heard as Graphics 73
RT-37435 Modena apps does not respond to VoiceOver
RT-39607 In TableView, Voiceover on Mac reads wrong column name when traversing Simple Table with Arrow keys
RT-39606 Progress Indicator 's Label is not visible in High Contrast
RT-39600 Editable ComboBox and DatePicker text fields: VoiceOver does not read characters
RT-39588 ListView row items not voiced when using CTRL-Up/Down Arrow
RT-39388 Focus is not visible on Charts
RT-39301 No focus highlight on header of non-collapsable title pane

Date:

16-Mar-2018

Archive Note:

This VPAT applies to only version 8u65/8u66. It does not apply to any versions of Oracle Java Platform, Standard Edition, Development Kit (Java SE JDK) after this. This VPAT has been superseded by Oracle Java Platform, Standard Edition, Development Kit Updated3 (Java SE JDK) 9.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

Java Control Panel
Policy Tool
Visual VM
AWT applications and applets
Install, MAC OS only
Java SE JDK on the UNIX OS and Linux platforms.

Java provides Access Bridge to allow access by Windows based Assistive Technology. To enable the Java Access Bridge please refer to
http://docs.oracle.com/javase/8/docs/technotes/guides/access/enable_and_test.html#enabling_jab

Dependent Products

This product interacts with or is built with the other Oracle products listedin this section. Click below to view information about the accessibility ofthese dependent products. Products listed are the versions available at thetime of publication of this document; newer documents may be available that supersedethese versions.

Oracle Java Mission Control updated3 5.5

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/Guideline	Included In Report
Web Content Accessibility Guidelines 2.0, at https://www.w3.org/TR/2008/REC-WCAG20-20081211/	Level A - Yes Level AA - Yes Level AAA - No
Section 508 as published in 2017, at https://www.Section508.gov	Yes

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.
Supports with Exceptions: 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.0 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.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content (Level A)	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
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Supports	The product was tested for: No Pre-recorded audio-only or video-only content is being used
1.2.2 Captions (Prerecorded) (Level A)	Supports	The product was tested for: No Pre-recorded video content is being used
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Supports	The product was tested for: No pre-recorded video is being used
1.2.4 Captions (Live) (Level AA)	Supports	The product was tested for: No live audio content in video is being used
1.2.5 Audio Description (Prerecorded) (Level AA)	Supports	The product was tested for : No pre-recorded video is being used
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
1.3.2 Meaningful Sequence(Level A)	Supports	The product was tested for: The accessibility hierarchy is logical
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
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
1.4.2 Audio Control(Level A)	Supports	The product was tested for: No automatically playing audio is used
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 All other 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
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.
2.1.1 Keyboard(Level A)	Supports with Exceptions	The product was tested for: The GUIs can be navigated by keyboard only except for the following known outage:JConsole: User guide link from Help menu isn't accessible via keyboard. Tracked in bug 7043941
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
2.2.1 Timing Adjustable(Level A)	Supports	The product 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.
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
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.
2.4.2 Page Titled(Level A)	Supports	The product was tested for: The name of the software application is meaningful.
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.
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), or preceding heading is sufficient to describe their purpose.
2.4.5 Multiple Ways(Level AA)	Supports	The JavaDoc portion of the product was tested for: Pages can be found using the provided "search" function Page contains controls that enable reaching all pages This guideline does not apply for the non-Web portion of the product.
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
2.4.7 Focus Visible(Level AA)	Supports	The product was tested for: Visual indication of the location of the focus
3.1.1 Language of Page(Level A)	Supports	The product was tested for: Properly set locale/language
3.1.2 Language of Parts(Level AA)	Supports	The product was tested for: Properly set locale/language for text passages that are in a different language than that of the software
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
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
3.2.3 Consistent Navigation(Level AA)	Supports	The JavaDoc portion of the product 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 There are no navigational mechanisms that are repeated 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.
3.2.4 Consistent Identification(Level AA)	Supports	The product 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
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
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
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)	Supports	The product was tested for: There are no legal, financial or data input
4.1.1 Parsing(Level A)	Supports with Exceptions	The product was tested for: Markup elements have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique Ids Markup content validate to the appropriate markup specification(s) Markup languages aren't used to generate the user interface The JavaDoc for the JDK supports this guideline with exceptions: there are some HTML4 issues in the JavaDocs. 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. When the Java class files include documentation that are not well-formed and thus making the output not accessible for AT. This is tracked in bugs, JDK-8032489, JDK-8033071.
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

2017 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria	Conformance Level	Remarks and Explanations
302.1 Without Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of Color	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without Speech	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited Manipulation	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and Strength	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning Abilities	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

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 AA	Supports	See the responses in the WCAG 2.0 section of this report.
502 Interoperability with Assistive Technology	Heading cell - no response required	Heading cell - no response required
502.2.1 User Control of Accessibility Features	Supports with Exceptions	Platform features as accessibility 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 JavaFX or 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 Features	Supports	Product was tested for: Software does not disrupt platform features that are defined in the platform documentation as accessibility features.
502.3 Accessibility Services	Heading cell - no response required	Heading cell - no response required
502.3.1 Object Information	Supports with Exceptions	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 25919145: Some content in the JDK installer's 'Custom Setup' dialog is not read by the screen reader. Bug 25919178: The screen reader reads inaccurate text content in the JRE installer's add-on software offer dialog. Bug 25919190: The screen reader does not read some content of the JRE installer's dialogs. Suggested workaround: INSERT+DOWN ARROW keys can be used to read through the entire document.
502.3.2 Modification of Object Information	Supports	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 Headers	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
502.3.4 Values	Supports	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 Values	Supports	The product was tested for: Event notification of changes to names, states, properties, and values is available to assistive technologies
502.3.6 Label Relationships	Supports	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 Relationships	Supports	The product was tested for: The accessibility hierarchy is logical
502.3.8 Text	Supports	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 Text	Supports	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 Actions	Supports	The product was tested for: Properly execute a list of actions
502.3.11 Actions on Objects	Supports	The product was tested for: Properly execute available actions on objects
502.3.12 Focus Cursor	Supports with Exceptions	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 Exceptions: Bug 25919202: The JRE installer window sometimes appears behind other windows. Suggested workaround: ALT+TAB keys can be used to cycle through open application windows and select the JRE installer's window. Bug 25918917: Selection doesn't follow VoiceOver focus. Suggested workaround: do not use VoiceOver navigation, i.e. Ctrl+Option+Arrows but to use just the arrows so the UI works as it would for a non-VoiceOver user. Bug 25919028: Focus not re-fired on ChoiceBox after popup is closed. Suggested workaround: Tab, Shift-Tab to refocus the control; then screen reader reads it. Bug 25919035: No focus highlight on header of non-collapsible title pane. Bug 25961324: Focus is not visible on Charts.
502.3.13 Modification of Focus Cursor	Supports with Exceptions	The product was tested for: Visual indication of the location of the focus modification Exceptions: Bug 25919202: The JRE installer window sometimes appears behind other windows. Suggested workaround: ALT+TAB keys can be used to cycle through open application windows and select the JRE installer's window. Bug 25918917: Selection doesn't follow VoiceOver focus. Suggested workaround: do not use VoiceOver navigation, i.e. Ctrl+Option+Arrows but to use just the arrows so the UI works as it would for a non-VoiceOver user. Bug 25919028: Focus not re-fired on ChoiceBox after popup is closed. Suggested workaround: Tab, Shift-Tab to refocus the control; then screen reader reads it.
502.3.14 Event Notification	Supports	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 Features	Supports	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 Applications	Heading cell - no response required	Heading cell - no response required
503.2 User Preferences	Not Supported	Bug 26184220 - Product does not permit user preferences
503.3 Alternative User Interfaces	Not Applicable	The product does not have assistive technology features.
503.4 User Controls for Captions and Audio Description	Heading cell - no response required	Heading cell - no response required
503.4.1 Caption Controls	Not Applicable	The product has no multimedia.
503.4.2 Audio Description Controls	Not Applicable	The product has no multimedia.
504 Authoring Tools	Heading cell - no response required	Heading cell - no response required
504.2 Content Creation or Editing	Not Applicable	The product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	The product is not an authoring tool.
504.2.2 PDF Export	Not Applicable	The product is not an authoring tool.
504.3 Prompts	Not Applicable	The product is not an authoring tool.
504.4 Templates	Not Applicable	The product is not an authoring tool.

Chapter 6: Support Documentation and Services

Criteria	Conformance Level	Remarks and Explanations
602 Support Documentation	Heading cell - no response required	Heading cell - no response required
602.2 Accessibility and Compatibility Features	Not Supported	BUG 26175494 Product does not have Accessibility Features documentation
602.3 Scope - Incorporation of WCAG 2.0 AA	Supports	See the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support Documentation	Not Applicable	Product documentation is in electronic format.
603 Support Services	Heading cell - no response required	Heading cell - no response required
603.2 Information on Accessibility and Compatibility Features	Supports	Oracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication Needs	Supports	Oracle 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.

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.