Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Application Express (APEX) 19.1

Product Description:

Oracle APEX is a modern web-based development framework for building web applications, and a no-cost feature of the Oracle Database. The framework relies on modern web technologies and standards including HTML5, JavaScript, CSS and WAI-ARIA.

There are known issues with this product, which are listed in this document under one or more of the following categories where appropriate:

Development Environment - The development environment for APEX.
Database Applications - Standard, developer-built web applications using the full framework capability.
Websheet Applications - Targeted not just at developers, 'Websheets' allow non-technical users to also put content on the web, and provide a different interface to the more common 'Database' applications.
Documentation - The documentation for APEX.

Date:

19-Feb-2019

Archive Note:

This VPAT applies to only version 19.1. It does not apply to any versions of Oracle Application Express (APEX) after this. This VPAT has been superseded by Oracle Application Express (APEX) 19.2.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

Interactive Grid Component - The Interactive Grid is a native region type that supports powerful reporting and multi-row editing capability. It is available to use in applications built with APEX, and also used in the Development Environment on a small number of pages. An alternative for the reporting capability is the Interactive Report region type. An alternative for the multi-row editing capability is the Tabular Form region type.
Calendar Component, Month and Week Views - The calendar is a native region type that supports viewing calendar and event information. It is available to use in applications built with APEX, and also used in the Development Environment on a small number of pages. An alternative to the month and week views is the list view, which is covered by this VPAT and available in the same region type.
SQL Workshop Module - Module used to maintain database objects for your applications. An alternative would be to connect to your database schema via a different tool (such as SQL Developer), if direct access to the database is available.
Theme Roller - Module available to developers allowing declarative definition of look and feel.
Data Grids in the Websheet runtime - Sub-module of a Websheet application, where ad-hoc multi-row data can be maintained. There is currently no alternative.
The Oracle by Example (OBE) tutorials are using templates that have not been accessibility tested. This issue is tracked with Oracle bug 26608336.
Help documentation provided in PDF format.
External content (web pages served from non-APEX-Workspace domains).

Oracle APEX is capable of generating web applications that meet the standards, as long as the developer follows the guidelines and applies accessibility standards appropriately. To help achieve this, please see the product documentation described in section 602.2.

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.

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 have meaningful alternative text using ALT Images that are decorative are marked up using ALT=”” or CSS background images Controls have an associated name Non-text characters are not used or have meaningful alternative text
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 with Exceptions	The product was tested for: No Pre-recorded video content is being used Exceptions: Affecting Documentation: Videos on the Application Express YouTube channel are missing closed captions. This issue is tracked with Oracle bug 29370906.
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 with Exceptions	The product 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 summaries where appropriate Data tables specify ARIA-LABEL or SUMMARY 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 Exceptions: Affecting Development Environment: The 'Quick Edit' and 'Live Template Options' features, available as a developer of an application via the developer toolbar, are inaccessible to screen readers user. You can use quick edit with keyboard-alone, where the cursor keys allow you to navigate through the runtime page and select the page component you wish to edit, however these components do not have any accessible label, meaning screen readers will not be able to identify them. Because Live Template Options is available via the Quick Edit feature, then this also means this is not accessible to screen reader users. Screen readers users will need to navigate to components to edit via the App Builder in the traditional way, so without the convenience of being able to go straight to a component to edit from the runtime. Also Template Options will need to be edited in the App Builder and saved, and then the page refreshed to see the effect of the change in the runtime, so without the convenience of the Live Template Option feature. This issue is tracked with Oracle bug 25153940. In many places across the development environment, the BOLD tag is used to emphasize text. This should be replaced with the STRONG tag. This issue is tracked with Oracle bug 29347790. Affecting Development Environment, Websheet Applications and Database Applications: Classic and Interactive report regions of Application Express currently have no declarative way of defining row headers. This issue is tracked with Oracle bug 14198644. The modern inline date pickers are not usable with screen readers or magnification due to focus not being set correctly. The data table is also missing a caption or summary text to describe the data in the table. Users can however enter the date manually into the date input field. This issue is tracked with Oracle bug 9740473. Affecting Documentation: The data tables rendered in the 'JavaScript API Reference' chapter of the documentation are missing an accessible name, and the containing cells are missing row headers. This issue is tracked with Oracle bug 29370396.
1.3.2 Meaningful Sequence(Level A)	Supports	The product 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
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
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 with Exceptions	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 Exceptions: Affecting Documentation: The 'JavaScript API Reference' chapter of the documentation has text that does not meet the minimum contrast requirements. This issue is tracked with Oracle bug 29370357.
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
1.4.5 Images of Text(Level AA)	Supports	The product 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
2.1.1 Keyboard(Level A)	Supports with Exceptions	The product 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, including those listed in the product documentation The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms) Exceptions: Affecting Development Environment and Database Applications: Although icon buttons used in our development environment and in Database Applications have an accessible name (using ARIA-LABEL), they also have a TITLE attribute which displays to mouse users on hover, however keyboard users have no way of perceiving this text. This issue is tracked with Oracle bug 28293186.
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 with Exceptions	The product was tested for: Time limits in the product can be turned off before they are encountered Exceptions: Affecting Development Environment and Websheet Applications: The Maximum Session Length and Maximum Session Idle Time time-outs, which are configured by the Application Express instance administrator, cannot be extended by an end-user. This issue is tracked with Oracle bug 14616880.
2.2.2 Pause, Stop, Hide (Level A)	Supports	The product was tested for: There is no moving, blinking or scrolling content
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 with Exceptions	The product was tested for: A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page. Structure and hierarchy is marked up with Header elements outside of repetitive navigation links WAI-ARIA Landmark elements are used outside of repetitive navigation links Exceptions: Affecting Development Environment and Websheet Applications: There are no 'Skip to Main Content' links implemented for the Development Environment, or in Websheet Applications. This issue is tracked with Oracle bug 27782291. Affecting Documentation: There are no 'Skip to Main Content' links implemented for the 'JavaScript API Reference' chapter of the documentation. This issue is tracked with Oracle bug 29370292.
2.4.2 Page Titled(Level A)	Supports	The product was tested for: Pages have a meaningful title specified in the TITLE element
2.4.3 Focus Order(Level A)	Supports with Exceptions	The product was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence Exceptions: Affecting Development Environment: On the workspace login page, at the bottom of the page there are three vertical sections containing links to further resources. Below the three sections there are four icons linking to different social media channels. Focus order takes you to the four social icons after tabbing through second section, however focus should instead take you to the four social icon links after tabbing through the third section. This issue is tracked with Oracle bug 29347837. Affecting Development Environment, Websheet Applications and Database Applications: When a validation fails on a form page, although the error will be announced to screen readers, we do not explicitly set the focus to help the user more quickly deal with fixing the errors. This issue is tracked with Oracle bug 26878709.
2.4.4 Link Purpose (In Context)(Level A)	Supports with Exceptions	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 Exceptions: Affecting Database Applications: In a Database Application using the Universal Theme, when the 'Card' report template has the template option 'Display Subtitle' unchecked, this results in the text "#CARD_SUBTITLE#" still being rendered in the link text. This issue is tracked with Oracle bug 29348961. Affecting Documentation: Bookmark links that appear next to specific sections in the 'JavaScript API Reference' chapter of the documentation have insufficient link text. This issue is tracked with Oracle bug #29370385.
2.4.5 Multiple Ways(Level AA)	Supports	The product was tested for: Pages are fully inter-linked to each other Pages can be found using the provided "search" function Page contains controls that enable reaching all pages
2.4.6 Headings and Labels(Level AA)	Supports with Exceptions	The product was tested for: Headers describe the topic or purpose of the content below them Labels describe the purpose of the associated field Exceptions: Affecting Development Environment: In Page Designer (where developers build and edit pages in APEX), the current heading structure needs improving to improve usability for users of Assistive Technology. This issue is tracked with Oracle bug 27782249. One of the administration pages for the Attribute Dictionary in APEX contains a 'Check All' style checkbox in the report's column header, which is missing label text. This issue is tracked with Oracle bug 20310474. Affecting Development Environment, Websheet Applications and Database Applications: Rendering a native check box item renders a DIV with role="group" that acts as a container for the group of check boxes and an ARIA-LABELLEDBY attribute providing the label for the group. This works well for check boxes that have more than one check box in the group, but when the check box only has one check box, it is incorrect to render this grouping markup. This issue is tracked with Oracle bug 18188460. Native checkbox and radio group item types contain duplicate labelling. This issue is tracked with Oracle bug 27810346.
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 lang attribute for each page
3.1.2 Language of Parts(Level AA)	Supports	The product was tested for: Proper use of lang attribute for text passages that are in a different language than that of the page
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 page, an additional change of keyboard focus, or the spawning of a pop-up 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 page, an additional change of keyboard focus, or the spawning of a pop-up window In circumstances where changing the value of the components causes a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window, warning is given prior to the user interacting with those user-interface components
3.2.3 Consistent Navigation(Level AA)	Supports	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
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 with Exceptions	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 Exceptions: Affecting Development Environment, Websheet Applications and Database Applications: Errors displayed in Interactive Report dialogs (for example when attempting to save a Filter with an empty 'Expression' value) just display a red border around the field in error, with no text explaining what the error is. This issue is tracked with Oracle bug 20697217.
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: Data is checked for input errors with an opportunity for the user to correct them When using the component creation wizards, the component data can be reviewed, corrected, and confirmed by the user before it is finalized
4.1.1 Parsing(Level A)	Supports with Exceptions	The product 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 Exceptions: Affecting Database Applications: If more than one Interactive Report Region are defined on one page, where more than one of those define a 'Link' column, then the 'Link' column heading rendered will contain duplicate ID values of 'LINK'. This issue is tracked with Oracle bug 20687795. Affecting Documentation: Some pages in the 'JavaScript API Reference' chapter of the documentation contain elements with duplicate IDs. This issue is tracked with Oracle bug #29370373.
4.1.2 Name, Role, Value (Level A)	Supports with Exceptions	The product was tested for: HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc. Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’ or 'invalid' Custom controls have appropriate roles specified using the role attribute Custom controls have appropriate state and property information conveyed using the relevant WAI-ARIA or HTML5 attributes Custom controls have a meaningful programatically exposed name Frames have a meaningful title specified in the title attribute Exceptions: Affecting Development Environment: The Code Editor item type, which is used in many places to enter SQL, PL/SQL and JavaScript code includes an auto-complete feature, providing suggestions specific to the code type. For example, in SQL and PL/SQL auto-complete provides suggestions of database objects, or page item names defined in the application that may need to be referenced from the code. The auto-complete functionality is not conveyed to assistive technologies. This issue is tracked with Oracle bug 20696803. Currently in the Property Editor, the display groups are marked up as DIV elements that are focusable with the keyboard. When focused, users can navigate between display groups with the Up and Down arrow keys, which aids keyboard support of the Property Editor. However, when the DIV is focused, screen readers can announce the display group title twice, and in addition can fail to announce the ARIA expanded state when the display group first gets focus (however, it is announced upon expand or collapse). This issue is tracked with Oracle bug 20693220. In Page Designer, it is possible to edit multiple components at the same time, however when using a screen reader, there is no indication that multiple items are selected. This issue is tracked with Oracle bug 29283988. In Page Designer, the splitter controls used to manage layout are poorly labelled and are missing ARIA-CONTROLS to point to relevant page area. This issue is tracked with Oracle bug 20693603. Affecting Development Environment and Database Applications: When logging into a workspace, or a Database Application using an appropriate authentication scheme, if the instance is set to have a delay for failed login attempts (setting in Instance Admin > Security > General Settings > Delay after failed login attempts in Seconds), and the user enters incorrect login details, a notification displays that includes a count down of the number of seconds before they can attempt logging in again. This count down is not announced properly to screen reader users. This issue is tracked with Oracle bug 29348302. The List View of the native Calendar region type uses DIVs with WAI-ARIA headings for the event list, however this should be implemented using more structured HTML. This issue is tracked with Oracle bug 27941145. In Page Designer > Property editor, the Yes / No style property types currently emit ARIA-REQUIRED on the grouping DIV around the input elements. This is invalid use of ARIA-REQUIRED. This issue is tracked with Oracle bug 27782266. Some configurations of 'required' attributes produce inconsistent output by screen readers, and may confuse users of assistive technology. This can lead to inconsistencies in what is emitted, and possibly confuse a user of Assistive Technology. This issue is tracked with Oracle bug 23761182.

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	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	Not Applicable	The product is designed to be isolated from the underlying platform.
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 Applicable	The product is designed to be isolated from the underlying platform.
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 does not provide a multimedia player.
503.4.2 Audio Description Controls	Not Applicable	The product does not provide a multimedia player.
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	Supports	The product contains no instance of either converting content from one format to another, or saving content in multiple formats.
504.2.2 PDF Export	Not Supported	Classic Report and Interactive Report native region types in APEX have the capability to export their data in PDF format. The PDF is not accessible.
504.3 Prompts	Supports	We mandate certain accessibility related attributes when building APEX applications (for example page titles, region titles, and button labels). The developer is responsible for ensuring the text provided is appropriate and meaningful. APEX includes a built-in tool called the Advisor, which can be run by developers as part of quality assurance of an APEX application. To help with other non-mandatory attributes defined by a developer, the Advisor includes a set of accessibility checks to highlight possible common accessibility problems (for example page items with no labels, or page regions with no row headers defined). The developer should review and fix such problems as part of their ongoing development process. We recommend to fix issues identified by the Advisor before doing other accessibility testing, for example testing with Assistive Technologies.
504.4 Templates	Supports	Developers should use the default 'Universal Theme' when building applications in APEX. This theme contains templates for different component types, which have been accessibility tested. In addition, developers can select different 'Theme Styles' for styling their applications in different ways. Theme Styles are labelled as being 'Accessibility Tested' if they have undergone accessibility testing. The default 'Vita' is accessibility tested.

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	The product documentation describes: Accessibility Guide, dedicated to helping you both use APEX, and build APEX apps that meet accessibility guidelines. Special keystrokes needed to operate controls Please visit the APEX documentation homepage and then select 'Accessibility Guide'.
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	Documentation is provided in electronic formats.
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.