Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle JDeveloper 11g R1 Fusion Apps Rel13

Product Description:

This ACR covers the user environment of Oracle JDeveloper 11g R1 Fusion Applications Release 13 ; the Installer and Upgrade Assistant are also covered. The Oracle Application Development Framework (ADF) 11g R1 Fusion Applications Release 13 output is not covered here, it is covered separately in the ADF 11g R1 Fusion Applications Release 13 VPAT listed in the Dependencies Section.

Date:

16-Sep-2022

Contact Information:

accessible_ww@oracle.com

Notes:

Users need to ensure that Accessbridge is enabled in the jdk.

Please see About JDeveloper Accessibility for information on the accessibility features of Oracle JDeveloper.

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.

ADF Faces Rich Client Components (output of JDeveloper), 11g R1 Fusion Apps Rel 13

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.1	Level A - Yes Level AA - Yes Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018	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.
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 Text summary or alternative is provided for time-based media Non-text characters are not used or have meaningful alternative text Captchas are not used Exceptions : Bug# 34455773 : The Screen Reader does not recognize elements in the Component Gallery dialog for the Gauge component. Bug# 34455909 : When the CPU profiler is run on an application selected in the Application navigator, the screenreader does not read any of the data or the method names in the table. Bug# 34455925 : The dialogs/windows inside of JDeveloper need to be made more discoverable by adding some text to the accessible description of dialogs/windows. Bug# 34455937 : In the Threads window of the debugger, using the up and down arrow button to move items in the table results in the screen reader reading the key that is pressed, rather than the selected item that is being moved. Bug# 34456002: Screen reader does not read the data in the message pane. The documentation was tested for: Images that convey information have meaningful alternative text using ALT 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 Information not conveyed using time-based media Non-text characters are not used or have meaningful alternative text CAPTCHAs are not used
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.4 Captions (Live) (Level AA)	Not Applicable	The product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)	Not Applicable	The 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: User interface component labels are associated with the fields they are labeling 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 Groups of components are marked up with their description Style sheets are used only to change the layout and presentation on the screen
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 Instructions provided which refer to graphics include a reference to the text alternative of the graphic The documentation was tested for: Instructions provided which refer to graphics included a reference to the text alternative of the graphic
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 documentation was tested for: Text displayed in both device orientations without loss of functionality or visibility of the text.
1.3.5 Identify Input Purpose (Level AA)	Not Applicable	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.
1.4.1 Use of Color(Level A)	Partially 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 Exceptions: Bug# 34454557 : The UI of the Extension editor is partially not readable in high contrast mode. Bug# 34455248 : When viewed in the high contrast mode, the Completion Insight Informational Popup is unreadable. Bug# 34456026 : When viewed in the high contrast mode, the Start page is unreadable. Bug# 34456039 : When viewed in the high contrast mode, the contents of the Application Overview page are unreadable. Bug# 34456266 : When viewed in the high contrast mode, the top portions of the UI rendered when we choose the "Find in Application files" menu of any given JAVA application is not visible. Bug# 34459238 : A modeller that is created in the high contrast mode, returns to the original color scheme when we scroll over it. Bug# 34456194 : When viewed in the high contrast mode, any given selected line of text inside a code editor is highlighted in light yellow, so any text that is not governed by syntax highlighting will not be visible to the user. The documentation was tested for: Information is not conveyed using color
1.4.2 Audio Control(Level A)	Not Applicable	The product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)	Partially Supports	The product was tested 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 Exceptions : Bug# 34454557 : The UI of the Extension editor is partially not readable in high contrast mode. Bug# 34455248 : When viewed in the high contrast mode, the Completion Insight Informational Popup is unreadable. Bug# 34456026 : When viewed in the high contrast mode, the Start page is unreadable. Bug# 34456039 : When viewed in the high contrast mode, the contents of the Application Overview page are unreadable. Bug# 34456266 : When viewed in the high contrast mode, the top portions of the UI rendered when we choose the "Find in Application files" menu of any given JAVA application is not visible. Bug# 34459238 : A modeller that is created in the high contrast mode, returns to the original color scheme when we scroll over it. Bug# 34456194 : When viewed in the high contrast mode, any given selected line of text inside a code editor is highlighted in light yellow, so any text that is not governed by syntax highlighting will not be visible to the user. The documentation 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
1.4.4 Resize text(Level AA)	Supports	The product was tested for: Text can be resized up to 200% without loss of content or functionality 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 of text are not used The documentation was tested for: Images of text are not used
1.4.10 Reflow (Level AA)	Supports	The product was tested for: Text information reflows so that only one direction of scrolling is required while at 400% zoom. The documentation was tested for: Text information reflows so that only one direction of scrolling is required while at 400% zoom.
1.4.11 Non-text Contrast (Level AA)	Supports	The product was tested for: Non-text items 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.
1.4.12 Text Spacing (Level AA)	Supports	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
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: 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 Exceptions : Bug# 34456215 : In the Stacks window of the debugger, the thread dropdown cannot be accessed using the keyboard. Bug# 34456229 : Cannot navigate through the Audit Log window tool bar using just the keyboard. Bug# 34456240 : In the Fusion Web ADF application, we cannot navigate to the find option in the Page Definition page using the keyboard. Bug# 34456263 : The Tasks window, opened by selecting the menu item 'Tasks' from the main menu 'View', allows the user to add filters to narrow the number of tasks displayed. The construction of such a filter is done in the 'Filter Tasks' dialog. However, if using the keyboard only it is only possible to add a new filter but not to modify its configuration. Bug# 34456311 : The gutter of the code editor is currently not accessible in the tab order and cannot be reached using just the keyboard. Bug# 34456329 : The search field and the terminate button in any Debugger Log window cannot be accessed using the keyboard. Bug# 34456349 : In an unbounded adf taskflow, when we select insert inside task-flow -> adf taskflow -> view, the resulting dialog is inaccessible. 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
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 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)	Not Applicable	The product was tested for: There are no single character keyboard shortcuts. The documentation was tested for: There are no single character keyboard shortcuts.
2.2.1 Timing Adjustable(Level A)	Not Applicable	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)	Not Applicable	The product was tested for: There is no moving, blinking or scrolling content The documentation was tested for: There is no moving, blinking or scrolling content
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	he 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)	Not Applicable	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)	Partially Supports	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. Exceptions : Bug# 34459283 : The Application Navigator Display Options and associated menu dropdowns do not show keyboard focus. Bug# 34458882 : When creating a servlet listener, if the finish button is clicked before the listener context is selected, an error dialog is displayed. However, focus is on the OK button and cannot move from that button, and the text of the error is not ready. 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)	Not Applicable	The product was tested for : 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.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 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 The documentation was tested for: Visual indication of the location of the focus
2.5.1 Pointer Gestures (Level A)	Not Applicable	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.
2.5.2 Pointer Cancellation (Level A)	Not Applicable	The product was tested for: There are no single pointer operations. The documentation was tested for: There are no single pointer operations.
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: There are no user interface components labeled with text or images of text.
2.5.4 Motion Actuation (Level A)	Not Applicable	The product was tested for: There are no functions that require motion of the device. The documentation was 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
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 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
3.2.2 On Input(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 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)	Not Applicable	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 The documentation was tested for: Images and controls which are used and identified consistently
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: Content does not require user input
3.3.3 Error Suggestion (Level AA)	Not Supported	The product was tested for: Where suggestions for fixing an input error are known, they are provided to the user. Exception : Bug# 22384911 : Suggestions for correction of input errors are not provided. The documentation was tested for: Content does not require user input
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)	Supports	The product was tested for: Submissions can be reversed by the user. The documentation was tested for: The documentation does not require user input that modifies user controllable data
4.1.1 Parsing(Level A)	Supports	The product was tested for : Markup languages aren't used to generate the user interface 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 ID
4.1.2 Name, Role, Value (Level A)	Partially 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 Exceptions : Bug# 34461073 : When dropping a JSF html message component onto a facelet, a dialog dropdown list is displayed; the text in this list is not recognized by the screen reader. The workaround is to use the Property Inspector to change the 'for' property of h:message. Bug# 34459905: When using code insight, and arrowing down through the list of available choices, the screen reader does not read the items listed. 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 Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’.
4.1.3 Status Messages (Level AA)	Partially Supports	The product was tested for: Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus. Exceptions: Bug 34499590: When a user searches for a particular file, search results will be displayed which says the number of matches and number of files searched. A screen reader announces 100% and does not read the number of files searched and a number of matches. The documentation was tested for: There are no status messages

2018 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	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility Features	Supports	The product was tested for: Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts
502.3 Accessibility Services	Heading cell - no response required	Heading cell - no response required
502.3.1 Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and Headers	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.4 Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.6 Label Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.8 Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.10 List of Actions	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on Objects	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.14 Event Notification	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility Features	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
503 Applications	Heading cell - no response required	Heading cell - no response required
503.2 User Preferences	Not Supported	Bug 34499212 - 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	Supports	See the responses in the WCAG 2.0 section of this report.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	Oracle JDeveloper does not perform format conversion
504.2.2 PDF Export	Not Applicable	Product does not export PDF
504.3 Prompts	Supports	Oracle JDeveloper provides Audit Rules functionality that provides users feedback on content to conform to Accessibility requirements.
504.4 Templates	Supports	Product does not provide templates

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	Supports	Please see About JDeveloper Accessibility for information on the accessibility features of Oracle JDeveloper.
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.