Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

PeopleSoft HCM Applications (May 2023 revision) 9.2x

Product Description:

PeopleSoft HCM Applications are a suite of web-based enterprise software business products that provide comprehensive, core, and strategic HR features. The suite of products are designed to accommodate large businesses with complex business requirements and can be deployed either on-premise or in the cloud. PeopleSoft HCM includes both a Classic/Classic Plus UI which is non-responsive and Fluid UI which is based on responsive as well as adaptive design. This ACR covers both the Classic/Classic Plus and Fluid forms of the UI. This ACR summarizes the PeopleSoft Human Capital Management Applications version 9.2x and is dependent on the PeopleSoft Enterprise PeopleTools ACR.

Date:

02-May-2023

Archive Note:

This VPAT applies to only version 9.2x May 2023 revision. It does not apply to any versions of PeopleSoft HCM Applications after this. This VPAT has been superseded by PeopleSoft HCM Applications (January 2024 revision) 9.2x.

Contact Information:

accessible_ww@oracle.com

Notes:

This ACR does not cover the following product areas:

Recruiting Solutions Open Integration Framework. Integrations with this framework are not delivered or supported by Oracle.
BI Publisher (XMLP) reports are intended for printing purposes only.
Delivered application SQR reports are considered to be samples. The majority of these reports are intended for printing purposes only and therefore are not considered accessible. The content within these sample reports may be obtained and viewed through alternate accessible means such as an online page or query.
PDF Version of Pay Checks, Pay Cheques, and Payslips.
PDF Version of Benefits Statement and Total Rewards Summary.
PDF Version of Tax Withholding forms for the US and Canada.
PDF Version of Affordable Care Act forms.
Fluid Time Reporting Location.
Pay Check Modeler.
Fluid Workforce Availability.
Global Payroll WorkCenter.
Global Payroll Element Browser.
Review Absence Calendar (Monitor Absence).
File Integration Framework.
Chatbot Assistants and Chatbot Integration Framework.
Forms and Approvals Builder.
Product Documentation in PDF format.
De-supported Classic/Classic Plus and Fluid Features as indicated in the Lifetime Support Policy for PeopleSoft Features found in the Application Support Notes on My Oracle Support.

Screen Reader Mode is configured in PeopleSoft products on a per user basis. With PeopleTools, there are a variety of methods which can be used to enable Screen Reader Mode. The first method is at sign-on, where the user can select a checkbox directly on the sign-on page to enable Screen Reader Mode. The second method allows each individual user to configure the User Interface (UI) mode in which they operate, whether it is Standard User Mode or Screen Reader Mode. The UI mode is set via the user preferences in PeopleTools Personalizations. To set Screen Reader Mode user preferences, the user navigates to 'My Personalizations' and then selects 'Personalize General Options.' The next step is to set the Accessibility Features Personalization Option to 'Use Screen Reader Mode'. The third method allows a user to activate Screen Reader Mode via the 'Actions' menu on the homepage on a one-time basis or a recurring basis. If a recurring basis is selected, the the user preference for Screen Reader Mode is saved in 'My Personalizations' and will persist for subsequent logins.

There is a section in the document "PeopleSoft Enterprise PeopleTools 8.60 Online Help: Accessibility Guide" titled "Setting Up PeopleSoft Accessibility Features" that further explains the steps to configure Screen Reader mode in the application.

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.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 product does not utilize the following: Time-based media. CAPTCHA. Tests that contain non-textual content. The product was tested for: Non-text content that is presented to the user has a text alternative. Controls that accept user input have meaningful labels and describes its purpose. Non-text content that is for presentation purposes only is implemented in a way that it can be ignored by an AT. Images that convey information have meaningful alternative text using ALT.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Not Applicable	The product was tested for: There is no pre-recorded audio only or video only content.
1.2.2 Captions (Prerecorded) (Level A)	Partially Supports	The product was tested for: Prerecorded video includes closed captions. Exceptions to the above are as follows: Closed captions are not provided for prerecorded audio content for the demonstration video for Activity Guide Composer. Bug 27584068.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Supports	The Activity Guide Composer feature provides the ability to include a video step in an activity guide. Customers are responsible for ensuring that any video added meet the criteria. The product was tested for: Prerecorded video includes a full text alternative to the video including any interaction.
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)	Partially Supports	The Activity Guide Composer feature provides the ability to include a video step in an activity guide. Customers are responsible for ensuring that any video added meet the criteria. The product was tested for: 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. Exceptions to the above are as follows: Demonstration video in Activity Guide Composer does not include audio description built into the main audio track. Bug 27581148.
1.3.1 Info and Relationships (Level A)	Partially Supports	The product was tested for: Column and Row headers on data tables. No information is solely conveyed through the style sheet. Layout tables use appropriate markup 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 Data tables specify SUMMARY or CAPTION Exceptions to the above are as follows: Questionnaires in Recruiting Solutions Candidate Gateway, are presented as a list but not marked up in the HTML as a list. Bug 19632823. Error messages which contain a list of error conditions or instructions are not marked up in the HTML as lists. Bug 19705029. Configurabe header in Fluid Self Service displays the employee name that is not marked up in the HTML as a header. Bug 33567495. View Calendar Details has a layout table not marked up in the HTML correctly. Bug 33868821. Setup Team Calendar table does not have row headings marked up in the HTML. Bug 33868821. Team Time has a layout table not marked up in the HTML correctly. Bug 35014787. W-2 Filing Instructions have headings not marked up in the HTML correctly. Bug 35266405. Approvals Status Monitor has approval and routing relationships not conveyed through markup in the HTML. Bug 33567561. Heading labels are duplicated in the Classic WorkCenter framework. Bug 28797894. My Saved Searches table has column headings missing and incorrect row headers in the My Job Openings transaction. Bug 33614883. Payroll paychecks have blank rows of data without row headers to visually separate data from the total row. Bug 35265213.
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)	Partially Supports	The product was tested for: Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound. Instructions provided which refer to graphics included a reference to the text alternative of the graphic. Exceptions to the above are as follows: Talent Acquisition Manager categorization of jobs uses color and alternative text to differentiate categories, but does not provide shading or different shapes. Bug 27476321.
1.3.4 Orientation (Level AA)	Supports	The product was tested for: Text is displayed in both device orientations without loss of functionality or visibility of the text.
1.3.5 Identify Input Purpose (Level AA)	Supports	The product was 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 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: Visual presentation of text to ensure that a contrast ratio of at least 4.5:1. Large-scale text and images of large-scale text have a contrast ratio of at least 3:1. Images of text are not utilized in the product.
1.4.4 Resize text(Level AA)	Supports	The product was tested for : Text can be resized up to 200% without loss of content or functionality.
1.4.5 Images of Text(Level AA)	Supports	The product was tested for: Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential.
1.4.10 Reflow (Level AA)	Not Supported	With browser zoom set to 400%, the user interface does not respond or adjust such that content can be presented without requiring two dimensional scrolling and without loss of functionality or meaning. Bug 30966209.
1.4.11 Non-text Contrast (Level AA)	Partially Supports	The product was tested for: Non-text items have a contrast ratio of at least 3:1. Exceptions to the above are as follows: Company Directory focus node does not have a contrast ratio of at least 3:1. Bug 34585390.
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. Exceptions to the above are as follows: Fields and nodes in Company Directory have text obscured with increased text spacing. Bug 35085777. Fluid Approvals side panel has text truncated with increased text spacing. Bug 33567561.
1.4.13 Content on Hover or Focus (Level AA)	Supports	The product was tested for: Dismissable -The content can be dismissed without moving the pointer or keyboard focus. Hoverable - When pointer hover triggers additional content, the pointer can be moved over the additional content without the additional content disappearing. Persistent - The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
2.1.1 Keyboard(Level A)	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. The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms.
2.1.2 No Keyboard Trap (Level A)	Supports	The product was tested for: Movement of focus through controls 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 was tested for: There are no single character keyboard shortcuts.
2.2.1 Timing Adjustable(Level A)	Supports	The product was tested for: Time limits in the product can be turned off before they are encountered. Time limits in the product can be adjusted to at last 10 times longer than encountered. Time limits in the product can be extended with at least 20 seconds warning up to 10 times. Time limits are longer than 20 hours. Time limits used are part of a real-time event, or a essential activity.
2.2.2 Pause, Stop, Hide (Level A)	Not Applicable	The product was tested for: There is no moving, blinking, or scrolling content.
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	The product was tested for: No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz.
2.4.1 Bypass Blocks(Level A)	Supports	The product was tested for: A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page. Structure and hierarchy is marked up with Header elements outside of repetitive navigation links. WAI-ARIA Landmark elements are used outside of repetitive navigation links.
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 tab order through the product controls and selectable elements. Consistent use of keyboard keys to perform selection and action. Exceptions to the above are as follows: Candidate Gateway focusable components do not receive focus in a meaningful sequence that preserves and operability. Bug 31794669. Company Directory tree node hierarchy tab order skips around and does not following a meaningful sequence. Bug 34585325 and Bug 34585321. Making selections in the Talent Profile side panel causes an unexpected change in focus order. Bug 34586363. Selecting Show Peers in Company DIrectory causes an unexpected change in focus order. Bug 34585369.
2.4.4 Link Purpose (In Context)(Level A)	Supports	The product was tested for: The text of links and their surrounding paragraph, list, or table cell (with marked up table headers), is sufficient to describe their purpose.
2.4.5 Multiple Ways(Level AA)	Supports	The product provides multiple methods to navigate to a page including: Drop down menu. Navigation menu ("NavBar"). Related Actions. Links on a page. Tiles (links) on a homepage or dashboard. Tabs on a page. Button bars (radio buttons). Global search feature to find a page. The product was tested for: Pages are contained in a "site map". Pages can be found using the provided "search" function. Page contains controls that enable reaching other 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)	Partially Supports	The product was tested for: Visual cues or feedback to the position of the cursor within the product. AT product successfully tracks cursor focus. Visual indication of the location of the focus. Exceptions to the above are as follows: Focus not visible after View Legend link on Time Summary transaction. Bug 35086566.
2.5.1 Pointer Gestures (Level A)	Supports	The product was tested for: There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)	Partially Supports	The product was 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. 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. When an operation uses a single pointer, the up-event reverses any outcome of the preceding down-event. Exceptions to the above are as follows: Row selector chevron is executed on the down-event and cannot be cancelled by moving focus away before the up-event. Bug 33567574.
2.5.3 Label in Name (Level A)	Supports	The product was tested for: User interface components that include text or images of text and have a label, have a name that contains the text that is presented visually.
2.5.4 Motion Actuation (Level A)	Supports	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. Exceptions to the above are as follows: Changing values of View Type drop down in Fluid Approvals causes an immediate change to substantial content on the page. Bug 33567574.
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. Exceptions to the above are as follows: UI for administrative functions versus self service is inherently different since the frequency of use varies. Administrators are trained users whereas self service users are typically infrequent and untrained users. As such, the UI for self service functions is different and much simpler than the UI administrator web pages which results in an inconsistency of the UI across these functions of the product. UI for different product families (e.g. payroll versus recruiting) have some differences in terminology. The application is tailored for a particular set of business processes, concepts, and roles which in some cases do not span across product families which results in an inconsistency of the UI. UI for Classic/Classic Plus versus Fluid transactions is different since Fluid transactions are a replacement for the legacy Classic/Classic Plus transactions.
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 can be reversed by the user. 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)	Partially Supports	The product was tested for: Elements in the HTML have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs. Pages validate to the HTML specification. Exceptions to the above are as follows: Duplicate IDs in the HTML were identified in the Fluid Attachments page. Bug 30281149. Duplicate IDs in the HTML were identifed in the Fluid Manage Absence page. Bug 35082484.
4.1.2 Name, Role, Value (Level A)	Partially 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. Frames have a meaningful title specified in the TITLE attribute. Exceptions to the above are as follows: The state of collapsible sections are visually shown in WorkCenters but are not marked up in the HTML such that the state of the section is announced using the AT. Bug 34409558.
4.1.3 Status Messages (Level AA)	Partially Supports	The product was tested for: Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus. Exceptions to the above are as follows: Overlapping group members message in Business Partner definition not read when error occurs. Bug 30232413.

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	Partially Supports	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. Exceptions to the above are as follows: Caption Controls are not provided for a demonstration video in Activity Guide Composer. Bug 27488962.
503.4.2 Audio Description Controls	Supports	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 Tools	Heading cell - no response required	Heading cell - no response required
504.2 Content Creation or Editing	Supports	See WCAG 2.0 Section.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	The product does not include authoring tools that provide format conversions or saving content in multiple formats.
504.2.2 PDF Export	Not Applicable	The product does not provide export of PDF files.
504.3 Prompts	Not Supported	The product does not prompt authors to create accessible content. Bug 27488962.
504.4 Templates	Not Applicable	The 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	The product documentation describes: Screen Reader mode user preferences and runtime. Special keystrokes needed to operate controls. Workarounds. Accessibility-related documentation can be found in PeopleSoft Enterprise PeopleTools 8.60 Online Help: PeopleSoft Accessibility Guide which describes screen reader mode and common accessibility related issues and how to prevent them when authoring content.
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.