Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle Profitability and Cost Management Cloud Service 22-06

Alternate Titles:

Oracle Enterprise Profitability and Cost Management Cloud

Product Description:

This ACR applies to

Oracle Profitability and Cost Management Cloud 22-06

Profitability and Cost Management Cloud (PCM) is a cloud based offering that allows financial analysts and business analysts to perform allocation and other transformations on their financial data to support multi dimensional profit analysis and cost contribution analysis. The PCM offering will include the data storage, rules definition, calculation management as well as profit and cost related dashboards, reports, and population (eg customer) performance visualizations.

PCM may be used with the original Profitability and Cost Management (PCM) user interface or with the new Enterprise Profitability and Cost Management (EPCM) user interface introduced in 22.06. Both interfaces provide similar data modeling capabilities. EPCM provides an updated interfaces for model management, dashboards, data forms, and reporting.

Date:

05-May-2022

Contact Information:

accessible_ww@oracle.com

Notes:

This ACR does not cover the following product areas:

Trace Allocations screens - Equivalent information is available in text oriented reports
EPM Automate Command Line Utility

An Accessibility button is provided on the home screen with options for accessibility mode.

Accessibility options for High Contrast and Screen Reader mode are available on the Accessibility settings dialog.

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 and documentation, for both the PCM and EPCM user interfaces, 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 AREA elements. CAPTCHAs are not used
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Not Applicable	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: There is no prerecorded Audio-only or Video-only content.
1.2.2 Captions (Prerecorded) (Level A)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: Pre-recorded video includes closed captions Pre-recorded video is an alternative for text and labelled as such
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: Pre-recorded video includes an alternative to the video
1.2.4 Captions (Live) (Level AA)	Not Applicable	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: This product has no live media content.
1.2.5 Audio Description (Prerecorded) (Level AA)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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
1.3.1 Info and Relationships (Level A)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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
1.3.2 Meaningful Sequence(Level A)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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 and documentation, for both the PCM and EPCM user interfaces, 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)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: Text is displayed in both device orientations without loss of functionality or visibility of the text.
1.3.5 Identify Input Purpose (Level AA)	Not Applicable	The product and documentation, for both the PCM and EPCM user interfaces, 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 and documentation, for both the PCM and EPCM user interfaces, was tested for: When color is used it is not the only visual means of conveying the information. Other text based means are employed also.
1.4.2 Audio Control(Level A)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: Audio that plays automatically for more than 3 seconds can be paused or stopped Audio that plays automatically for more than 3 seconds has a mechanism to control the audio volume independently from the overall system volume level
1.4.3 Contrast (Minimum) (Level AA)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: Text is displayed using the 4.5:1 contrast ratio.
1.4.4 Resize text(Level AA)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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 and documentation, for both the PCM and EPCM user interfaces, was tested for: Images of text are not used in the product.
1.4.10 Reflow (Level AA)	Partially Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: 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. Exceptions With browser zoom set to 400% the product layout, text, and graphics do not adjust to require only vertical scrolling. Bug ID 31241391
1.4.11 Non-text Contrast (Level AA)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: Non-text items have a contrast ratio of at least 3:1
1.4.12 Text Spacing (Level AA)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: When the following attributes and no others are modified there is no loss in functionality or content: Line height (line spacing) to at least 1.5 times the font size. Spacing following paragraphs to at least 2 times the font size. Letter spacing (tracking) to at least 0.12 times the font size. Word spacing to at least 0.16 times the font size.
1.4.13 Content on Hover or Focus (Level AA)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: 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)	Partially Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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 Exceptions: PCM 30771015 Table data in Job Library and Rules screens are not read by a screen reader
2.1.2 No Keyboard Trap (Level A)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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 and documentation, for both the PCM and EPCM user interfaces, was tested for: There are no single character keyboard shortcuts.
2.2.1 Timing Adjustable(Level A)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: The only time limit is the interface is for logoff due to inactivity. The user is given more than 20 seconds to extend.
2.2.2 Pause, Stop, Hide (Level A)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: Product does not use moving, blinking or scrolling information. Auto updating information is required to update to provide accurate information about current state of job status.
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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 and documentation, for both the PCM and EPCM user interfaces, 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 and documentation, for both the PCM and EPCM user interfaces, was tested for: Pages have a meaningful title specified in the TITLE element
2.4.3 Focus Order(Level A)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence
2.4.4 Link Purpose (In Context)(Level A)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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 and documentation, for both the PCM and EPCM user interfaces, was tested for: Page contains controls that enable reaching all pages
2.4.6 Headings and Labels(Level AA)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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 and documentation, for both the PCM and EPCM user interfaces, was tested for: Visual indication of the location of the focus
2.5.1 Pointer Gestures (Level A)	Not Applicable	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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
2.5.3 Label in Name (Level A)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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 and documentation, for both the PCM and EPCM user interfaces, was tested for: Functionality that is operated by device motion or user motion can also be operated by user interface components Responding to the motion can be disabled, except when the motion is used to operate functionality through an accessibility supported interface OR the motion is essential for the function.
3.1.1 Language of Page(Level A)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: Properly set lang attribute for each page
3.1.2 Language of Parts(Level AA)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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 and documentation, for both the PCM and EPCM user interfaces, was tested for: When an element receives focus, it does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window
3.2.2 On Input(Level A)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window In circumstances where changing the value of the components causes a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window, warning is given prior to the user interacting with those user-interface components
3.2.3 Consistent Navigation(Level AA)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: Pages that are grouped together into sets with a common navigation mechanism utilize that navigation mechanism in the same fashion, with navigation elements appearing in the same relative order each time
3.2.4 Consistent Identification(Level AA)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification(Level A)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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)	Partially Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: Labels or instructions are provided when the product requires user input Exceptions: PCM 30771042 - Find and Replace options in the Bulk Editng screen are not read by a screen reader.
3.3.3 Error Suggestion (Level AA)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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 and documentation, for both the PCM and EPCM user interfaces, 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)	Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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 and documentation, for both the PCM and EPCM user interfaces, 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 programatically exposed name Frames have a meaningful title specified in the title attribute
4.1.3 Status Messages (Level AA)	Partially Supports	The product and documentation, for both the PCM and EPCM user interfaces, was tested for: Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus. Exceptions: PCM 30770992 - Status message on the Manage POV screen is not read by screen reader

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	Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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 Controls	Supports	The product and documentation, for both the PCM and EPCM user interfaces, 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	Not Applicable	The product is not an authoring tool.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	The product is not an authoring tool.
504.2.2 PDF Export	Not Applicable	The product is not an authoring tool.
504.3 Prompts	Not Applicable	The product is not an authoring tool.
504.4 Templates	Not Applicable	The product is not an authoring tool.

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	Accessibility-related documentation can be found at: https://docs.oracle.com/en/cloud/saas/profit-cost-cloud/asspm/toc.htm The product documentation describes: Accessibility modes at runtime Special keystrokes needed to operate controls
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.