Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Forms 14c 14.1.2.0.0

Product Description:

This ACR covers the development and runtime environment of Oracle Forms. Oracle Forms is used to create custom applications, and includes features to make information available to users of assistive technology. Oracle Forms is capable of rendering content as described within this ACR, when an application developer uses it according to guidance provided in the reference manual, and follows other applicable accessibility standards and guidelines.

Date:

12-Jun-2024

Contact Information:

accessible_ww@oracle.com

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 Help Center (OHC), Self-Publishing May 2023

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)	Supports	The Non-Web UI was tested for: Images that convey information have meaningful alternative text Contains no images that are decorative Contains no complex images such as charts Data tables include a summary or caption, programmatically connected with the table Controls have an associated name Contains no time-based media Non-text characters are not used or have meaningful alternative text CAPTCHAs are not used Note: Toolbar buttons are not directly keyboard navigable, but their functionality is replicated using shortcut keys or menu entries. This is standard Windows behavior. The Web UI was tested for: Images that convey information have meaningful alternative text Contains no images that are decorative Contains no complex images such as charts Data tables include a summary or caption, programmatically connected with the table Controls have an associated name Contains no time-based media Non-text characters are not used or have meaningful alternative text CAPTCHAs are not used The Documentation was tested for: Images that convey information have meaningful alternative text Contains no images that are decorative Contains no complex images such as charts Data tables include a summary or caption, programmatically connected with the table Controls have an associated name Contains no 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	No pre-recorded audio-only or video-only content is being used.
1.2.2 Captions (Prerecorded) (Level A)	Not Applicable	Pre-recorded video content is not used.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Not Applicable	There is no pre-recorded video.
1.2.4 Captions (Live) (Level AA)	Not Applicable	Live audio content in video is not used.
1.2.5 Audio Description (Prerecorded) (Level AA)	Not Applicable	There is no pre-recorded video.
1.3.1 Info and Relationships (Level A)	Supports	The Non-Web UI was tested for: User interface component labels are associated with the fields they are labeling Headings are marked as such Lists are marked as such Tables are marked as such, including row and column headers and table captions/summaries where appropriate Groups of components are marked as such, with a description for the group The Web UI was tested for: User interface component labels are associated with the fields they are labeling Headings are marked as such Lists are marked as such Tables are marked as such, including row and column headers and table captions/summaries where appropriate Groups of components are marked as such, with a description for the group The Documentation was tested for: User interface component labels are associated with the fields they are labeling Headings are marked as such Lists are marked as such Tables are marked as such, including row and column headers and table captions/summaries where appropriate Groups of components are marked as such, with a description for the group
1.3.2 Meaningful Sequence(Level A)	Supports	The Non-Web UI was tested for: The platform's built-in AT reading/presentation sequence matches the logical reading sequence The Web UI was tested for: The sequence of elements in the DOM matches a logical reading sequence 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 Non-Web UI was tested for: Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound. The Web UI was tested for: Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound. The Documentation was tested for: Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound.
1.3.4 Orientation (Level AA)	Supports	The Non-Web UI was tested for: A fixed display orientation is required for essential functionality. The Web UI was tested for: A fixed display orientation is required for essential functionality. The Documentation was tested for: Text is displayed in both device orientations without loss of functionality or visibility of the text.
1.3.5 Identify Input Purpose (Level AA)	Not Applicable	There are no text fields that collect information about the user.
1.4.1 Use of Color(Level A)	Supports	The Non-Web UI was tested for: Information conveyed by color is available in alternative formats, such as shape, text, font weight Information conveyed by color has a contrast ratio of at least 3:1 The Web UI was tested for: Information conveyed by color is available in alternative formats, such as shape, text, font weight Information conveyed by color has a contrast ratio of at least 3:1 The Documentation 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)	Not Applicable	No automatically playing audio is used.
1.4.3 Contrast (Minimum) (Level AA)	Supports	The Non-Web UI 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 The Web UI 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 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 Non-Web UI was tested for: Text can be resized up to 200% without loss of content or functionality by changing the operating system font size. The Web UI 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)	Not Applicable	Images of text are not used.
1.4.10 Reflow (Level AA)	Supports	The Non-Web UI was tested for: Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content. The Web UI was tested for: Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content. 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 Non-Web UI was tested for: Non-text items have a contrast ratio of at least 3:1 The Web UI 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 Non-Web UI was tested for: The product does not have content implemented using markup languages that support editing the text style properties in this criteria. The Web UI was tested for: The product does not have content implemented using markup languages that support editing the text style properties in this criteria. 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 Non-Web UI was tested for: There is no content that appears on hover or focus The Web UI 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: 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.
2.1.1 Keyboard(Level A)	Supports	The Non-Web UI was tested for: ability to perform functions from the keyboard only logical movement of focus through the controls proper operation of unique keystrokes, including those listed in the product documentation The Web UI was tested for: ability to perform functions from the keyboard only logical movement of focus through the controls proper operation of unique keystrokes, including those listed in the product documentation The Documentation 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
2.1.2 No Keyboard Trap (Level A)	Supports	The Non-Web UI 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 Web UI was tested for: Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control. The Documentation was tested for: Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control.
2.1.4 Character Key Shortcuts (Level A)	Not Applicable	The Non-Web UI was tested for: There are no single character keyboard shortcuts. The Web UI 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	Time limits are not used.
2.2.2 Pause, Stop, Hide (Level A)	Supports	The Non-Web UI was tested for: Moving, blinking, or scrolling content that is pure decoration can be stopped or hidden The Web UI was tested for: Moving, blinking, or scrolling content that is pure decoration can be stopped or hidden The Documentation was tested for: Moving, blinking, or scrolling content that is pure decoration can be stopped or hidden
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	The Non-Web UI was tested for: No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz The Web UI 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)	Supports	The Non-Web UI 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 is always automatically met. The Web UI was tested for: Web UI does not repeat any content across multiple pages. 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 Non-Web UI was tested for: The name of the software application is meaningful. The Web UI was tested for: Pages have a meaningful title specified in the TITLE element The Documentation was tested for: Pages have a meaningful title specified in the TITLE element
2.4.3 Focus Order(Level A)	Supports	The Non-Web UI was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence. Note: Toolbar buttons are not directly keyboard navigable, but their functionality is replicated using shortcut keys or menu entries. This is standard Windows behavior. The Web UI was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence. 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 Non-Web UI 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 Web UI 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)	Supports	The Non-Web UI 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 is always automatically met. The Web UI was tested for: Page contains controls that enable reaching all pages The Documentation was tested for: Page contains controls that enable reaching all pages
2.4.6 Headings and Labels(Level AA)	Supports	The Non-Web UI was tested for: Headers describe the topic or purpose of the content below them Labels describe the purpose of the associated field The Web UI was tested for: Headers describe the topic or purpose of the content below them Labels describe the purpose of the associated field The Documentation was tested for: Headers describe the topic or purpose of the content below them Labels describe the purpose of the associated field
2.4.7 Focus Visible(Level AA)	Supports	The Non-Web UI was tested for: Visual indication of the location of the focus Note: Toolbar buttons are not directly keyboard navigable, but their functionality is replicated using shortcut keys or menu entries. This is standard Microsoft Windows behavior. The Web UI 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)	Supports	The Non-Web UI was tested for: There are no multipoint or path-based gesture actions. The Web UI 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)	Supports	The Non-Web UI was tested for: When an operation uses a single pointer, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion The Web UI was tested for: When an operation uses a single pointer, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion The Documentation was tested for: When an operation uses a single pointer, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion
2.5.3 Label in Name (Level A)	Supports	The Non-Web UI 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 Web UI 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 does not contain motion actuation.
3.1.1 Language of Page(Level A)	Supports	The Non-Web UI was tested for: Properly set locale/language The Web UI was tested for: Properly set lang attribute for each page The Documentation was tested for: Properly set lang attribute for each page
3.1.2 Language of Parts(Level AA)	Supports	The non-Web UI was tested for: Properly set locale/language for text passages that are in a different language than that of the software The Web UI was tested for: Properly set locale/language for text passages that are in a different language than that of the software. The Documentation was tested for: 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 Non-Web UI 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 Web UI 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 Non-Web UI was tested for: Changes in the value of user interface components does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window The Web UI was tested for: Changes in the value of user interface components does not result in a substantial change to the user interface of the software, an additional change of keyboard focus, or the spawning of a new window The Documentation was tested for: 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 non-Web UI 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 is always automatically met. The Web UI was tested for: Web UI pages do not span multiple pages. The Documentation was tested for: Pages that are grouped together into sets with a common navigation mechanism utilize that navigation mechanism in the same fashion, with navigation elements appearing in the same relative order each time
3.2.4 Consistent Identification(Level AA)	Supports	The Non-Web UI was tested for: Images and controls are used and identified consistently throughout the product The Web UI was tested for: Images and controls are used and identified consistently throughout the product The Documentation was tested for: Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification(Level A)	Supports	The Non-Web UI 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 Web UI 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 has no input fields, except for the search field.
3.3.2 Labels or Instructions (Level A)	Supports	The Non-Web UI was tested for: Labels or instructions are provided when the product requires user input. The Web UI was tested for: Labels or instructions are provided when the product requires user input. The Documentation was tested for: Labels or instructions are provided when the product requires user input.
3.3.3 Error Suggestion (Level AA)	Supports	The Non-Web UI was tested for: Where suggestions for fixing an input error are known, they are provided to the user. The Web UI was tested for: Where suggestions for fixing an input error are known, they are provided to the user. The Documentation was tested for: The documentation has no input fields, except for the search field.
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)	Supports	The Non-Web UI was tested for: Data is checked for input errors with an opportunity for the user to correct them The Web UI was tested for: Data is checked for input errors with an opportunity for the user to correct them The Documentation was tested for: The documentation does not allow for changes to data.
4.1.1 Parsing(Level A)	Supports	The Non-Web UI was tested for: This Success Criterion is always satisfied. The Web UI was tested for: This criterion is always satisfied for any content using HTML or XML. The Documentation was tested for: This criterion is always satisfied for any content using HTML or XML.
4.1.2 Name, Role, Value (Level A)	Supports	The Non-Web UI was tested for: User interface components have a programmatically associated name and role State information, properties, and values are programmatically exposed for user interface components The Web UI 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’. The Documentation was tested for: HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
4.1.3 Status Messages (Level AA)	Supports	The Non-Web UI was tested for: Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus. The Web UI was tested for: There are no status messages. 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 Non-Web UI 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	Supports	The Non-Web UI was tested for: Responds to platform settings for color, contrast, font type, font size, and focus cursor
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	Supports	The Non-Web UI was tested for: File conversions preserve accessibility information The Web UI was tested for: File conversions preserve accessibility information
504.2.2 PDF Export	Not Applicable	Product does not use or create PDF content
504.3 Prompts	Not Supported	The product does not prompt authors to create content that conforms to WCAG 2.0 AA
504.4 Templates	Not Applicable	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 refer to the Accessibility in Oracle Forms Applications White Paper at https://www.oracle.com/a/ocom/docs/corporate/forms-applications-accessibility.pdf
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.