Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

PeopleSoft Financials and Supply Chain Management Applications (Mar 2023 Revision) 9.2x

Product Description:

PeopleSoft Financials and Supply Chain Management (FSCM) Applications are a suite of web-based enterprise software business products that provide comprehensive core and strategic Financials and Supply Chain Management 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 FSCM 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 VPAT covers both the Classic/Classic Plus and Fluid forms of the UI.  Furthermore, this VPAT summarizes the PeopleSoft Financials and Supply Chain Applications version 9.2x and is dependent on the PeopleSoft Enterprise PeopleTools VPAT.

Date:

07-Mar-2023

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

  • Use of third-party products often configured with PeopleSoft Asset Lifecycle Management, ESA or Financials.
  • jQuery mobile solutions for Expenses and Time Entry applications.  The content delivered for mobile devices may be obtained and viewed through an alternative accessible means such as on a desktop or laptop computer.
  • Delivered application SQR and Crystal reports are considered to be samples.  These reports are intended for printing purposes only and therefore are not accessible.  The content contained within these delivered reports may be obtained and viewed through an alternative accessible means such as an online page or query.
  • Delivered BI Publisher (XMLP) reports are considered to be samples.  The majority of these reports are intended for printing purposes only and therefore are not accessible.  The content contained within these delivered reports may be obtained and viewed through an alternative accessible means such as an online page or query.
  • Supplier, Customer and Work Order Organization Chart Hierarchies.
  • Components and Pages in the eBill Payment product that display PayPal content.
  • Cash Position detail pages.
  • Customer Comprehensive View.
  • Supplier 360.
  • Financial Gateway Payment Dispatch.  
  • Collection Workbench.
  • Resource Locator.
  • Forms and Approval Builder Designer.
  • Asset Tracking sub-feature mask scanned tag.
  • Chatbot Assistants and Chatbot Integration Framework.
  • Product Documentation in PDF format.
  • Project Costing Project Activities Gantt Chart.  Alternative content can be found on the Project Activities tab.
  • De-supported Classic/Classic Plus 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'.

There is a section in the Accessibility Guide of PeopleSoft Online Help for PeopleTools 8.60 titled "Setting Up PeopleSoft Accessibility Features" that further explains the steps to configure Screen Reader (Accessibility) 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/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)Partially 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.

Exceptions to the above are as follows:

  • An issue was identified in Strategic Sourcing Public Homepage where announcements are read as a button.  Bug 30370540.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.4 Captions (Live) (Level AA)Not ApplicableThe product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)Not ApplicableThe product has no multimedia.
1.3.1 Info and Relationships (Level A)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
1.3.2 Meaningful Sequence(Level A)Supports

The product was tested to ensure that the sequence in which content is presented is in a logical tab order.

1.3.3 Sensory Characteristics(Level A)Supports

The product was tested to ensure that color, shape,  physical location, or any other sensory characteristics are not the only means of conveying content or guidance to the user.

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

The product was tested for :

  • Text fields on Fluid Employee Self Service Pages which collect information about the user contain the appropriate autocomplete content attribute. 

Some classic self-service transactions pages that do not have an equivalent fluid transaction page have not been evaluated.  Bug 35139937 has been created to keep track of those pages and address them in future image(s).

1.4.1 Use of Color(Level A)Supports

This product was tested for:

  • The product does not use color or visual presentation as the only means of conveying information to the user.
1.4.2 Audio Control(Level A)Not ApplicableThe product has no multimedia.
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.

The visual presentation of the product is delivered using a specific PeopleTools style sheet, "Redwood" which has been tested to conform to these contrast requirements.   The settings in the delivered style sheet can be overridden by the user, the browser settings, or the operating system.

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 does not utilize images of text.

1.4.10 Reflow (Level AA)Not Supported

With browser zoom set to 400%, 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)Supports

Graphic content and user components have a 3:1 contrast ratio with their background and/or adjacent content.

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.

There is one noted exception as follows :
Bug 32550507 - Text Spacing will not work for elements that have fixed dimensions or maximum dimensions set.

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

This 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

This product was tested for:

  • Movement of focus through each control can be done using only 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 does not contain animation and does not utilize auto-updating that starts automatically or auto-updating that is presented in parallel with other 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:

  • Pages provide HTML headers which enable the user to bypass blocks of content.   Headers are provided for Page Titles, Group Boxes, Scroll Areas, and Grids (Tables)
2.4.2 Page Titled(Level A)Supports

The product was tested for:

  • Pages have meaningful page titles specified in the TITLE element.
2.4.3 Focus Order(Level A)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.
2.4.4 Link Purpose (In Context)(Level A)Partially Supports

The product was tested to ensure that the purpose of each link can be understood, its label is meaningful,  and that labels are not vaguely worded.

Some tiles which display charts in accessibility mode, chart data is read as link label by screen reader in non-sequential orders, whereas only the chart title should be read as that indicates the purpose of the link which is to open a detail viewer of the chart.  Bug 35139993 has been created to track this issue.

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 (buttons) on a homepage.
  • 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 relevant pages.
2.4.6 Headings and Labels(Level AA)Supports

The product was tested for:

  • Structure and hierarchy conveys meaningful text in header elements on pages.
  • Column and Row headers on data tables.
2.4.7 Focus Visible(Level AA)Supports

The product was tested for:

  • Visual cues or feedback to the position of the cursor within the product.
  • Assistive Technology product successfully tracks cursor focus.
  • Visual indication of the location of the focus.
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)Supports

The product was tested for:

  • When an operation uses a single pointer, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion
2.5.3 Label in Name (Level A)Supports

The 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)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)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.
3.2.3 Consistent Navigation(Level AA)Supports

The product was tested for consistent navigation and order across pages.

3.2.4 Consistent Identification(Level AA)Supports

The product was tested for:

  • Images and controls are used and identified consistently throughout the product
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 the identification of the item where the error occurred.
3.3.2 Labels or Instructions (Level A)Supports

The product was tested for meaningful labels, instructions where applicable, and ALT text.

3.3.3 Error Suggestion (Level AA)Supports

The product was tested for:

  • The product provides messages for input when input errors are automatically detected.   The error messages contain information indicating what the error is and instructions on how to correct the error when known.
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)Supports

The product was tested to ensure that when legal commitments or financial transactions occur that modify or delete user-controllable data that one or more of the following is true:

  • Data that is entered by the user is validated for input errors and the user is provided an opportunity to correct the errors before submission.
  • Confirmation pages are available for reviewing, confirming, and correcting input before finalizing the submission of data.
  • Submissions are reversible or can be re-entered by the user.
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

There is one noted exceptions as follows:

Bug 24322172 Duplicate ID Violations when Tiles generated with Tile Wizard.

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.
  • Frames have a meaningful title specified in the TITLE attribute.
4.1.3 Status Messages (Level AA)Partially Supports

The product was tested for :

Status messages are conveyed to assistive technology when there is a change in context.

There is one noted exception as follows:

Bug 32651775 - Status messages are not automatically announced for grids.

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 ControlsNot ApplicableThe product has no multimedia.
503.4.2 Audio Description ControlsNot ApplicableThe product has no multimedia.
 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 includes:

  • Documentation on how to use accessibility features
  • Documentation on accessibility features that provide compatibility with assistive technology

Accessibility-related documentation can be found in the PeopleSoft Enterprise PeopleTools 8.60 Online Help 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 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.