Oracle Accessibility Conformance Report

VPAT® Version 2.5

Name of Product:

Oracle Fusion Middleware Extensions for Oracle Applications 11.13.25.04.0

Product Description:

This product extends Fusion Middleware with capabilities to help support the design and runtime of Fusion Applications.

The responses to many of the technical standards are based on functionality provided by underlying technologies; please see the ACRs listed in the Dependent Products section for more information.

Report Date:

10-Mar-2025

Contact Information:

accessible_ww@oracle.com

Notes:

Oracle Fusion Applications have several runtime modes, set via accessibility preferences, such as screen reader, and high contrast. Please consult Oracle Fusion Applications Help for detailed information on accessibility preferences.

Documentation on Fusion Applications Accessibility: http://www.oracle.com/pls/topic/lookup?ctx=cloud&id=OACPR1012002

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	Level A - Yes Level AA - Yes Level AAA - No
Web Content Accessibility Guidelines 2.1	Level A - Yes Level AA - Yes Level AAA - No
Web Content Accessibility Guidelines 2.2	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.2 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.2 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 product and documentation were 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 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)	Partially Supports	The product and documentation were 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 Exceptions: Bug 32947150 - In Setup and Maintenance, after search for a task and open the page, the screen reader does not read the page header Bug 32946971 - In Setup and Maintenance, after search for a task and open a page with required fields, if not filled in we are not raising an error when using a screen reader Bug 28952966 - Card layout will have an empty H1 header at the top Bug 36977260 - Text is getting cropped in the Card component on the Home page in screen reader mode Bug 26896847 - Visual Information Navigator breadcrumbs are not read when using a screen reader Bug 28555143 - On mobile devices, when showing partial search results, the status is misread by screen readers. Example, "1 - 25 of 36 items" the "-" is read as "minus" on Android, and not read at all on iOS Bug 28473097 - On mobile Android devices using Chrome, the first section of a page is read without stopping when using a screen reader Bug 31842513 - Infotile titles do not have heading tags Bug 26359262 - In Setup and Maintenance, Page headers are using H2 while should be H1 Bug 35712506 - Tooltips in Key Flexfields are the same as the label so they are read twice in screen reader mode Bug 33924239 - If more than 1 table in a page, Previous and Next buttons have the same name in screen reader mode Bug 35506246 - In Data Security UI, when adding a user group, there are 2 search buttons with the same name in screen reader mode Bug 33783070 - ListSearch component shows headings as level 1 in screen reader mode Bug 33765132 - ListSearch component edit box does not have a label in screen reader mode Bug 35443672 - Added Dynamic Flexfields have no label in screen reader mode Bug 29866413 - Key Flexfield column not visible in screen reader mode if table editing is Click To Edit Bug 26474832 - "Search" string in Simple Panel pattern is using headers with H1 while should be H2 on Manage Orders/Agreement pages Bug 31888593 - Tables with related Flexfield sub columns will not have the headers read in the expected order in screen reader mode Bug 37343751 - Done button is read multiple times in Responsive UI pages (HCM pages that optimize its appearance to various screen sizes) in screen reader mode Bug 36070515 - All the column headers in the attachments table on the Supplier View details page are not read in screen reader mode
1.3.2 Meaningful Sequence(Level A)	Supports	The product and documentation were tested for: The sequence of elements in the DOM matches a logical reading sequence
1.3.3 Sensory Characteristics(Level A)	Supports	The product and documentation were 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 included a reference to the text alternative of the graphic
1.3.4 Orientation (Level AA)	Supports	The product and documentation were 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)	Supports	The product and documentation were tested for: Text fields which collect information about the user contain the appropriate autocomplete content attribute
1.4.1 Use of Color(Level A)	Supports	The product and documentation were 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	The product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)	Partially Supports	The product and documentation were 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: Bug 31791528 - Contextual Action popup title (white text on yellow background) does not meet the minimum contrast ratio in My projects page Bug 35383993 - The info tile in Procurement/Negotiations does not meet the minimum contrast ratio for the Closing Next value Bug 37237949 - OK button of error popup does not meet the minimum contrast ratio for the Expense Work Area page.
1.4.4 Resize text(Level AA)	Partially Supports	The product and documentation were tested for: Text can be resized up to 200% without loss of content or functionality Exceptions: Bug 30607878 - Panel headings are overlapping other content when zoomed to 200% in the Supply Planning page
1.4.5 Images of Text(Level AA)	Supports	The product and documentation were tested for: Images of text are not used
1.4.10 Reflow (Level AA)	Not Supported	The product and documentation was tested for: Information reflows not losing information or functionality and that only one direction of scrolling is required while at 400% zoom Exceptions: Bug 31089292 - When product UIs are zoomed to 400%, you need both scroll bars to view/navigate the complete UI
1.4.11 Non-text Contrast (Level AA)	Partially Supports	The product and documentation were tested for: Non-text items have a contrast ratio of at least 3:1 Exceptions: Bug 31791528 - Warning icon (yellow triangle with white "!") does not meet the minimum contrast ratio in My projects page Bug 31826710 - Contextual Triangle Icon does not pass contrast on all pages Bug 31838285 - horizontalBarGraph when rendered as a pivot table contains a navigation control panel that does not meet the minimum contrast ratio on Billing Work Area pages
1.4.12 Text Spacing (Level AA)	Partially Supports	The product and documentation were 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 Exceptions: Bug 31614259 - If use larger text spacing, and have more than 1 line of text, the test will overlap in Visual Information Builder and Visual Information Navigator Bug 33769558 - Clipped Title text appears if just text is scaled on Billing Work Area Infotiles Bug 31680930 - When text spacing is enabled, larger text is causing Panel Headers to become truncated on all pages
1.4.13 Content on Hover or Focus (Level AA)	Supports	The product and documentation were 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
2.1.1 Keyboard(Level A)	Partially Supports	The product and documentation were 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: Bug 37133064 - A Keyboard user is not able to navigate to the Apps region when browser is shrunk down in a smaller "viewport" and Global Search is open Bug 31779438 - When using the Flexfield entry from a popup in Split Allocation in an Expenses page, changes to segment values are not saved Bug 35906638 - Unable to scroll with the keyboard for context sensitive segment Descriptive Flexfields in screen reader mode
2.1.2 No Keyboard Trap (Level A)	Supports	The product and documentation were 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)	Supports	The product and documentation were tested for: There are no single character keyboard shortcuts
2.2.1 Timing Adjustable(Level A)	Supports	The product and documentation were tested for: Time limits are not used
2.2.2 Pause, Stop, Hide (Level A)	Supports	The product and documentation were tested for: There is no moving, blinking or automatic scrolling content
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	The product and documentation were 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 product and documentation were 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
2.4.2 Page Titled(Level A)	Supports	The product and documentation were tested for: Pages have a meaningful title specified in the TITLE element
2.4.3 Focus Order(Level A)	Partially Supports	The product and documentation were tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence Exceptions: Bug 29182498 - When a page opens within Setup and Maintenance, and it is using the Simple panel component, the Page title is not updated so focus is not going to the top. Bug 26328960 - When a new tab is opened within a page that supports multiple tabs, focus is set to the top of the page instead of within the new tab in screen reader mode Bug 33207588 - When using Key Flexfield entry from a popup and then use a search LOV popup and a selection is made the 2nd time, it will result in the LOV closing and focus moving back to the base popup in screen reader mode Bug 26179573 - When using Key Flexfield entry from a popup and then use a search LOV popup and dismiss it using Cancel, the focus is moving back to the base popup in screen reader mode Bug 27439282 - Key Flexfield Reset button will move focus to the top of the page in screen reader mode Bug 29443556 - On close of search and select popup for Key Flexfield, the cursor is going to Top left corner instead of the flex field Bug 35352210 - The Format button in the secondary menu of the Toolbar component is skipped in screen reader mode
2.4.4 Link Purpose (In Context)(Level A)	Supports	The product and documentation were 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 product and documentation were tested for: Page contains controls that enable reaching other top-level pages of our product Pages can be found using the provided "search" function
2.4.6 Headings and Labels(Level AA)	Partially Supports	The product and documentation were tested for: Headers describe the topic or purpose of the content below them Labels describe the purpose of the associated field Exceptions: Bug 31870142 - When using pattern templates that contain buttons like Continue, Edit, and Save more than once on a page, they will not have unique names when using a screen reader Bug 33756439 - Links included in a List View through the panelSectionEdit component do not have unique labels on the page when using assistive technology Bug 35728321 - The simple panel commandImageLink icon which goes back to last page has an inaccurate label of "Done" in screen reader mode
2.4.7 Focus Visible(Level AA)	Supports	The product and documentation were tested for: Visual indication of the location of the focus
2.4.11 Focus Not Obscured (Level AA)	Supports	The product and documentation were tested for: The initial position of user interface components receiving keyboard focus are not hidden entirely by author-created content.
2.5.1 Pointer Gestures (Level A)	Supports	The product and documentation were tested for: There are no multipoint or path-based gesture actions
2.5.2 Pointer Cancellation (Level A)	Supports	The product and documentation were tested for: When an operation uses a single pointer, the down-event of the pointer is not used to execute any part of the function
2.5.3 Label in Name (Level A)	Supports	The product and documentation were 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
2.5.4 Motion Actuation (Level A)	Supports	The product and documentation were tested for: There are no functions that require motion of the device.
2.5.7 Dragging Movements (Level AA)	Supports	The product and documentation were tested for: There is no functionality that uses dragging movements.
2.5.8 Target Size (Minimum) (Level AA)	Partially Supports	The product and documentation were tested for: Interactive targets take up at least 24×24 CSS pixels of space, including white space around the target, and the space is not shared with another target. The function can be achieved through a different control in the same software that meets this criterion. The target is in a sentence or its size is otherwise constrained by the line-height of non-target text. A particular presentation of the target is essential or is legally required for the information being conveyed. Exceptions: Bug 37016799 - Target size is missing in the Invoice landing page approval tile Bug 36977560 - ListSearch component on the Manage Seller Negotiations page is insufficient in touch size
3.1.1 Language of Page(Level A)	Supports	The product and documentation were tested for: Properly set lang attribute for each page.
3.1.2 Language of Parts(Level AA)	Supports	The product and documentation were tested for: Proper use of lang attribute for text passages that are in a different language than that of the page When showing rows of strings for translation purposes, each row's language is identified in a language column When showing a full table of content in another language for translation purposes, the language selection is shown at the top of the page
3.2.1 On Focus(Level A)	Supports	The product and documentation were 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 and documentation were tested for: 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 and documentation were 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 and documentation were tested for: Images and controls are used and identified consistently throughout the product
3.2.6 Consistent Help (Level A)	Supports	The product and documentation were tested for: Help mechanisms (or a link to different software containing help mechanisms) occur in the same order relative to other software content.
3.3.1 Error Identification(Level A)	Supports	The product and documentation were tested for: When input errors are detected, they are described to the user in text, including identifying the item where the error occurred
3.3.2 Labels or Instructions (Level A)	Supports	The product and documentation were tested for: Labels or instructions are provided when the product requires user input
3.3.3 Error Suggestion (Level AA)	Supports	The product and documentation were tested for: Where suggestions for fixing an input error are known, they are provided to the user The documentation was tested for: Content does not require user input
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)	Supports	The product and documentation were tested for: Data can be reviewed, corrected, and confirmed by the user before they are finalized The documentation was tested for: The documentation does not require user input that modifies user controllable data
3.3.7 Redundant Entry (Level A)	Supports	The product and documentation were tested for: Information previously entered by or provided to the user that is required to be entered again in the same process is available for the user to select.
3.3.8 Accessible Authentication (Minimum) (Level AA)	Not Applicable	The product and documentation were tested for: Authentication does not rely upon a cognitive functional test.
4.1.1 Parsing(Level A)	Not Applicable	This criterion is considered as always satisfied for any content using HTML or XML.
4.1.2 Name, Role, Value (Level A)	Partially Supports	The product and documentation were 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’ Custom controls have appropriate roles specified using the role attribute Custom controls have a meaningful programmatically exposed name Exceptions: Bug 33693408 - The cardandlistlayout component List View and Paragraph View buttons are not shown in screen reader mode because the they do not have Link or Botton roles Bug 31779307 - Flexfield "View" link does not have a Link role Bug 33989314 - When panelCollectionEdit and panelSectionEdit are used in listEdit mode the expand and collapse icons should have a Link role Bug 35545460 - Right hand side menu within pages are shown and behave like buttons but have the link role Bug 37231636 - Global Search input combobox does not have all required ARIA attributes Bug 36081627 - On the Redwood Request a new position, Change position and Position details pages, Descriptive Flexfields are using unallowed ARIA attributes
4.1.3 Status Messages (Level AA)	Supports	The product and documentation were tested for: Status messages can be presented to the user by assistive technologies without receiving focus

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	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 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	Authoring portion of product does not convert information to other formats.
504.2.2 PDF Export	Not Applicable	The product does not export pdf.
504.3 Prompts	Not Applicable	The Authoring tools only create content that is already accessible. No prompt is needed.
504.4 Templates	Supports	The product and documentation were tested for: Templates are provided that allow content creation that conforms to WCAG 2.0 AA

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: special keystrokes needed to operate controls workarounds Accessibility-related documentation can be found at: https://docs.oracle.com/en/middleware/developer-tools/jet/17/develop/developing-accessible-applications.html A reference guide for keystrokes and touch gestures can be found at: http://www.oracle.com/pls/topic/lookup?ctx=jetlatest&id=OJACC
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.