Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Fusion Service Request Management Cloud Service 11.13.22.01.0

Product Description:

This VPAT covers the service request management functionality available in Oracle Fusion Sales and B2B Service. The product supports the ability to create, edit, assign, respond to and resolve service requests. Service Requests can be associated to accounts, contacts, partner accounts, activities, and assets that are shared between the sales and service applications.  The user interface for the product is based on the Fusion Simplified User Experience. Service Requests can also be created and updated through REST APIs and file-based import.

Date:

15-Dec-2021

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

  • Access to the data through REST or SOAP web services
  • PDF and ePub files

Accessibility mode can be activated by the user using the Accessibility preferences page available from the global UI header across the top of every page.  The user can access this page through one of two paths - either by selecting the accessibility mode icon in the global UI header or by selecting the user menu in the top right corner of the global UI header and then choosing  Personalization > Set Preferences > Accessibility.

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/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.1Level A - Yes
Level AA - Yes
Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018Yes

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 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
  • Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)
  • Titles for Objects and Applets are provided
  • Controls have an associated name
  • Text summary or alternative is provided for time-based media
  • Client-side image maps specify the ALT attribute on each AREA element.
  • CAPTCHAs are not used
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Not Applicable

The product was tested for

  • No Pre-recorded audio-only or video-only content is being used
1.2.2 Captions (Prerecorded) (Level A)Supports

The product was tested for

  • Pre-recorded video includes captions embedded in the media (potentially as a second version of the media)
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Supports

The product was tested for:

  • Pre-recorded video includes an alternative to the video
1.2.4 Captions (Live) (Level AA)Not Applicable

The product was tested for:

  • No live audio content in video is being used.
1.2.5 Audio Description (Prerecorded) (Level AA)Not Supported

The product was tested for:

  • Pre-recorded video includes a second audio track with audio descriptions
  • Pre-recorded video includes a second version (or the only version) of the video that has audio descriptions built into it on the main audio track

Known accessibility defects include:
Bug 26554336 - Prerecorded videos do not include audio description

1.3.1 Info and Relationships (Level A)Partially Supports

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 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

Known accessibility defects include:

Bug #26598140 -  When using a screen reader, if a user opens the right hand panel on the Service Request detail page and uses the Manage SmartText icon to view a SmartText, the content of the SmartText is read twice.
Bug #29593899 -  When using a screen reader, the label for the service request problem description field is read twice.
Bug #31926455 -  In the dialog to apply an action plan action to a service request, the table structure is not found by the screen reader when no actions are currently selected.
Bug #31854227 -  After applying an action plan action to a service request, a screen reader does not read the name of the Actions and Plans subtab that appears.
Bug #31253265 -  In Setup and Maintenance, the following setup tasks do not provide a label for every form element: Manage Service Product Group Usage for Business Unit, Manage HR Help Desk Product Group Usage for Business Unit, Manage Service Categories for Business Unit, Manage Communication Channels for Business Unit, Manage Service Milestone Configuration for Business Unit.
Bug #33112949 - In the Create Service Request form, the category field does not have an associated label.
Bug #33208449 - On the Manage Email Profile Options setup page, a screen reader does not read the values for user name, group name, description or the search result/Save/Cancel popups.
Bug #33431547  - On the Action Plans subtab, the Start button on the Action Plan list does not provide additional details that explain the purpose of the button.
Bug #33431268  - On the Action Plans subtab, clicking on the link for an action plan does not indicate a message for loading complete and no message is given if the user refreshes the subtab
Bug #33431036 - On the Action Plans subtab, a screen reader does not focus and read the labels in the table for the Actions, Refresh and Delete actions
Bug #33430331 - On the Action Plans subtab, a screen reader does not read the table columns for SR Reference number, Status, Title and Last updated date.
Bug #32904444  - On the Manage Collaboration Actions setup page, a screen reader reads extra detail which may make it difficult for a user to understand.

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 which refer to graphics included a reference to the text alternative of the graphic
1.3.4 Orientation (Level AA)Partially Supports

The product was tested for:

  • Text is displayed in both device orientations without loss of functionality or visibility of the text.

Known accessibility defects include:
Bug #31294453 -  In the audit subtab of a service request, columns on the right side of the table cannot be accessed using the horizontal scrollbar when the browser is in portrait orientation.
Bug #31243223 -  In portrait orientation, the rightmost columns of the service request list does not appear because a horizontal scrollbar is not displayed.
Bug #31254202 -  In portrait orientation, the rightmost columns of the HR service request list does not appear because a horizontal scrollbar is not displayed.

1.3.5 Identify Input Purpose (Level AA)Not Applicable

The product was tested for:

  • There are no text fields that collect information about the user.
1.4.1 Use of Color(Level A)Supports

The product was tested for:

  • Information conveyed by color is available in alternative formats, such as shape, text, font weight
  • Information conveyed by color has a contrast ratio of at least 3:1
1.4.2 Audio Control(Level A)Not Applicable

The product was tested for:

  • No automatically playing audio is used
1.4.3 Contrast (Minimum) (Level AA)Supports

The product was tested for:

  • Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
  • All other text and images of text have a contrast ratio of at least 4.5:1
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)Not Applicable

The product was tested for:

  • Images of text are not used
1.4.10 Reflow (Level AA)Not Supported

The product was tested for:

  • Text information reflows so that only one direction of scrolling is required while at 400% zoom.
  • An alternative mobile user interface is available and is accessed from the main application.
  • Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.

Known accessibility defects include:

Bug #31089292 -  When UIs are zoomed to 400%, subtabs are not visible, need both scroll bars to view/navigate the complete UI
Bug #33113116 - When UIs are zoomed to 400% and the user is editing the field on a Service Request, tthe choice lists for Account, Contact, Product, Queue, Category and Assign to do not completely display the content and scrollbars are missing.
Bug #31294453 -  In the audit subtab of a service request, columns on the right side of the table cannot be accessed using the horizontal scrollbar when the browser is in portrait orientation.
Bug #31243223 -  In portrait orientation, the rightmost columns of the service request list does not appear because a horizontal scrollbar is not displayed.
Bug #31254202 -  In portrait orientation, the rightmost columns of the HR service request list does not appear because a horizontal scrollbar is not displayed.

1.4.11 Non-text Contrast (Level AA)Supports

The product was tested for:

  • Non-text items have a contrast ratio of at least 3:1.
1.4.12 Text Spacing (Level AA)Partially Supports

The product was tested for:

  • When the following attributes and no others are modified there is no loss in functionality or content:
    • Line height (line spacing) to at least 1.5 times the font size
    • Spacing following paragraphs to at least 2 times the font size
    • Letter spacing (tracking) to at least 0.12 times the font size
    • Word spacing to at least 0.16 times the font size

Known accessibility defects include:

Bug #31253857 -  When text spacing has been increased, the header for HR Service Requests list page is not displayed completely.

1.4.13 Content on Hover or Focus (Level AA)Partially Supports

The product was tested for:

  • Dismissable -The content can be dismissed without moving the pointer or keyboard focus
  • Hoverable - When pointer hover triggers additional content, the pointer can be moved over the additional content without the additional content disappearing
  • Persistent - The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.

Known accessibility defects include:
Bug #31305319 -   In the Contacts subtab and Team subtab of the service request page, the help pop-ups for the search fields are not dismissable using the keyboard.

2.1.1 Keyboard(Level A)Partially Supports

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

Known accessibility defects include:
Bug #25668485 -  When a user tries to edit the product field on a Service Request, the user must use the Alt+down keystroke to expand the field and the Shift+Tab keystroke to search the rows in the hierarchy.  However, the user is not able to use the keyboard to select one of the items in the hierarchy.   As a workaround, the user must tab into the search box and search on the text of the desired item specifically.
Bug # 32772308 - When a user navigates into the product field on a Service Request and uses the search option within the menu, the user can select a product row using the up and down arrow keys, however using Tab will not move the user to the OK button, so the user needs to use Shift+Tab to traverse to the OK button and apply the selection.
Bug #32772258 - When a user navigates into the category field on a Service Request and uses the search option within the menu, the user can select a category row using the up and down arrow keys, however using Tab will not move the user to the OK button, so the user needs to use Shift+Tab to select the OK button and apply the selection.
Bug #32772187 - When a user navigates into the Account field on a Service Request and uses the search option within the choice list, the user can select an Account row using the up and down keys, however using Tab will not move the user to the OK button, so the user needs to use Shift+Tab to select the OK button and apply the selection.
Bug #26595324 -  When composing a Service Request message, after a value is selected in the From field, the cursor can lose focus intermittently if Command+E is used to navigate to the message content area.   As a workaround, the user can instead use the Tab key to navigate to the message content area.
Bug #26595266 -  When composing a Service Request message, the Insert Knowledge button does not perform any action when invoked using a screen reader tool.
Bug #27802803 -  The click-to-edit feature for in-line editing in tables is not available to keyboard users. Keyboard users can edit the data in each row through the drill down link.

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.1.4 Character Key Shortcuts (Level A)Not Applicable

The product was tested for:

  • There are no single character keyboard shortcuts.
2.2.1 Timing Adjustable(Level A)Supports

The product was tested for:

  • When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
2.2.2 Pause, Stop, Hide (Level A)Supports

The product was tested for:

  • There is no moving, blinking or scrolling content that starts automatically.
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

The product was tested for:

  • Structure and hierarchy is marked up with Header elements outside of repetitive navigation links
2.4.2 Page Titled(Level A)Supports

The product was tested for:

  • Pages have a meaningful title specified in the TITLE element
2.4.3 Focus Order(Level A)Partially Supports

The product was tested for:

  • Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence

Exceptions

  • BUG 33176243 - When using a keyboard to interact with the Assigned To field, when the user first uses the up and down keys to move up and down the list, then selects the Tab key, the focus is shifted to a browser tab rather than the OK button.
  • BUG 32773515 - When using a keyboard to perform the Resolve action on a Service Request, after filling in the resolution information, the focus leaves the popup and returns to the main page, forcing the user to iterate through the whole page to return to the popup.
  • BUG 32771986 - On the Advanced Search panel on the service request list page, after selecting the Reorder button Tab key does not advance to the options, so the user must use the Up and Down arrow keys to select a value within the popup.
  • Bug #32772031 - When a user navigates into the Contact field on a Service Request, after using the up and down arrow to select the desired Contact row, using Tab moves the cursor focus out of popup before focusing on the OK button, so the user needs to use Shift+Tab to traverse the other direction to select the OK button.
  • Bug #32771931 - When multiple dynamic tabs are opened from the Service Request list page, the user is not able to use the keyboard to focus on the X icon on the dynamic tab to close it, so the user must use the Tab key to traverse to the Cancel button to close the dynamic tab.
2.4.4 Link Purpose (In Context)(Level A)Partially Supports

The product was tested for:

  • The text of links and their surrounding paragraph, list, table cell (with marked up table headers), is sufficient to describe their purpose

Exceptions

Bug #33431473  - On the Action Plans subtab, a screen reader does not provide helpful information about the purpose of the Reference Number field in the table.

2.4.5 Multiple Ways(Level AA)Supports

The product was tested for:

  • Pages can be found using the provided "search" function
  • Pages are in a site table of contents
  • Pages are fully inter-linked to each other
  • Page contains controls that enable reaching all pages
2.4.6 Headings and Labels(Level AA)Supports

The product was tested for:

  • Headers describe the topic or purpose of the content below them
  • Labels describe the purpose of the associated field
2.4.7 Focus Visible(Level AA)Supports

The product was tested for:

  • Visual indication of the location of the focus
2.5.1 Pointer Gestures (Level A)Not Applicable

The product was tested for:

  • There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)Not Applicable

The product was tested for:

  • There are no single pointer operations
2.5.3 Label in Name (Level A)Supports

The product has been 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)Not Applicable

The product was tested for:

  • There are no functions that require motion of the device.
3.1.1 Language of Page(Level A)Supports

The product was tested for:

  • Properly set 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)Partially 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

Known accessibility defects include:
Bug #31692978 -  After applying an action plan action to a service request, the user is automatically navigated to the Actions and Plans subtab and a screen reader does not read the name of the tab to help orient the user to the change of context.

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)Partially Supports

The product was tested for:

  • Images and controls are used and identified consistently throughout the product

Known accessibility defects include:
Bug #31423865 - When creating a service request from the account details page, the title of the Create Service Request dialog is not fully displayed.

3.3.1 Error Identification(Level A)Supports

The product was tested for:

  • When input errors are detected, they are described to the user in text, including identifying the item where the error occurred
3.3.2 Labels or Instructions (Level A)Supports

The product was tested for:

  • Labels or instructions are provided when the product requires user input
3.3.3 Error Suggestion (Level AA)Supports

The product was tested for:

  • Where suggestions for fixing an input error are known, they are provided to the user
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)Supports

The product was tested for:

  • Submissions are reversible
  • Data is checked for input errors with an opportunity for the user to correct them
  • Data can be reviewed, corrected, and confirmed by the user before they are finalized
4.1.1 Parsing(Level A)Supports

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
  • Pages validate to the HTML specification
4.1.2 Name, Role, Value (Level A)Supports

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’.
  • 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 programmatically exposed name
  • Frames have a meaningful title specified in the title attribute
4.1.3 Status Messages (Level AA)Not Applicable

The product was tested for:

  • There are no status messages.

back to top

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria
Conformance Level
Remarks and Explanations
302.1 Without VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of ColorNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without SpeechNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited ManipulationNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and StrengthNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning AbilitiesNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

back to top

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 AASupportsSee the responses in the WCAG 2.0 section of this report.
 502 Interoperability with Assistive TechnologyHeading cell - no response requiredHeading cell - no response required
502.2.1 User Control of Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility FeaturesNot ApplicableThe product is designed to be isolated from the underlying platform.
 502.3 Accessibility ServicesHeading cell - no response requiredHeading cell - no response required
502.3.1 Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and HeadersNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.4 ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.6 Label RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.8 TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.10 List of ActionsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on ObjectsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.14 Event NotificationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
 503 ApplicationsHeading cell - no response requiredHeading cell - no response required
503.2 User PreferencesNot ApplicableThe product is designed to be isolated from the underlying platform.
503.3 Alternative User InterfacesNot ApplicableThe product does not have assistive technology features.
 503.4 User Controls for Captions and Audio DescriptionHeading cell - no response requiredHeading cell - no response required
503.4.1 Caption ControlsSupports

The product was tested for:

  • user controls for the selection of captions are provided at the same menu level as the user controls for volume or program selection.
503.4.2 Audio Description ControlsSupports

The product was tested for:

  • user controls for the selection of audio description are provided at the same menu level as the user controls for volume or program selection.
 504 Authoring ToolsHeading cell - no response requiredHeading cell - no response required
504.2 Content Creation or EditingNot ApplicableThe product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot ApplicableThe product is not an authoring tool.
504.2.2 PDF ExportNot ApplicableThe product is not an authoring tool.
504.3 PromptsNot ApplicableThe product is not an authoring tool.
504.4 TemplatesNot ApplicableThe product is not an authoring tool.

back to top

Chapter 6: Support Documentation and Services

Criteria
Conformance Level
Remarks and Explanations
 602 Support DocumentationHeading cell - no response requiredHeading cell - no response required
602.2 Accessibility and Compatibility FeaturesSupports The product documentation describes:
  • accessibility modes, either at installation or runtime
  • special keystrokes needed to operate controls
  • workarounds
Accessibility-related documentation can be found at: Oracle Applications Cloud Using Common Features, Chapter 13 Accessibility
602.3 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support DocumentationNot Applicable

Product documentation is in electronic format.

 603 Support ServicesHeading cell - no response requiredHeading cell - no response required
603.2 Information on Accessibility and Compatibility FeaturesSupportsOracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication NeedsSupportsOracle 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.

back to top

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.