Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

PeopleSoft Enterprise PeopleTools 8.61

Product Description:

PeopleTools provides the underlying technology for PeopleSoft applications providing both a development as well as runtime platform. PeopleSoft applications, such as Human Capital Management, Financials and Supply Chain Management, Customer Relationship Management and Enterprise Learning Management are built, deployed, and maintained using PeopleTools. PeopleTools and PeopleSoft Applications can be deployed either on-premise or in the cloud.

PeopleTools 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 Enterprise PeopleTools version 8.61.

Date:

03-Jan-2024

Contact Information:

accessible_ww@oracle.com

Notes:

This ACR does not cover the following product areas:

The Administrative functions of PeopleSoft including but not limited to the Application Designer, Data Mover, Change Assistant, PeopleTools Test Framework (PTF), Change Impact Analyzer, and administrative SQR reports delivered with PeopleTools such as the Cross Reference reports.
The PeopleTools online product – PeopleSoft Update Manager.
The Reporting tools delivered with PeopleTools, such as Oracle Analytic Publisher, SQR or nVision, are capable of generating code that meets the applicable provisions of WCAG 2.0 when used in accordance with their written documentation. 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. To create accessible reports, manually create an RTF layout following the guidance in the "Designing Accessible Reports" section of the Oracle Analytic Publisher Guide. HTML and PDF are the supported output types for consuming accessible reports.
Recent Search and Saved Search functionality.
Insights using OpenSearch Dashboards and tiles for OpenSearch Dashboards.
Product Documentation in PDF format.

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 user 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 Preferences' and then selects 'General Settings.' The next step is to set the Accessibility Layout Option to 'Screen reader mode on'. 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 user preference for Screen Reader Mode is saved in 'My Personalizations' and will persist for subsequent logins.

There is a section in the Peoplebooks- PeopleSoft Accessibility Guide titled "Setting Up PeopleSoft Accessibility Layout 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/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 was tested for: Meaningful icon/image/object identification. Meaningful images have alternative text. Grids have a table summary. PIA pages have meaningful page titles. If an SQR is developed with the appropriate commands to embed tags to identify content such as Table, List, Paragraph, heading, Alternate text etc, a tagged PDF output can be generated in a manner in which a screen reader can be utilized to read the content. The product does not utilize the following: Time-based media. CAPTCHA. Tests that contain non-textual content.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Not Applicable	The product has no multimedia.
1.2.4 Captions (Live) (Level AA)	Not Applicable	The product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)	Not Applicable	The product has no multimedia.
1.3.1 Info and Relationships (Level A)	Supports	The product was tested for: User interface component labels are associated with the fields they are labeling Column and row headers on data tables. Data tables specify SUMMARY Tables (Grids and Group Boxes) used for presentation are marked up correctly for layout purposes No information is solely conveyed through the style sheet. Headings are encoded with HTML heading tags List markup is used for marking up lists Groups of components are marked up with their description
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: Information conveyed by color is available in alternative formats, such as shape, text, font weight.
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	This product was tested for: This product does not use color as the only means of providing information. Information conveyed by color has a contrast ratio of at least 3:1
1.4.2 Audio Control(Level A)	Not Applicable	The product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)	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. An Application release is tied to a specific PeopleTool's stylesheet. The stylesheets for "Fluid" and "Classic Plus" have been tested to conform to the Large text and contrast requirements.
1.4.4 Resize text(Level AA)	Partially Supports	The product was tested for : Text can be resized up to 200% without loss of content or functionality. Exceptions to the above are as follows: Special Characters popup and Top row not fully seen on Accessibility Help page when Browser zoom is 200%. Bug 35774560.
1.4.5 Images of Text(Level AA)	Supports	The product was tested for: Images of text are not used in place of actual 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)	Partially Supports	The product was tested for: Graphic content and user components have a 3:1 contrast ratio with their background and/or adjacent content. Exceptions to the above are as follows : Rich Text Editor Toolbar button state and button hover state don't pass color contrast on pages enabled with Rich Text Editor fields. Bug 35073861.
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 : Text Spacing will not work for constructs that have fixed dimensions or maximum dimensions set such as homepages, dashboards, menus and side panels. Bug 32550507.
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)	Partially Supports	The product was tested for: Logical tab order through the product controls and selectable elements. Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys. Hotkeys/keyboard shortcuts available to skip elements. Proper and consistent use of keyboard keys to perform selection and action. Exceptions to the above are as follows : ALT+0 shortcut key does not bring up Rich Text Editor Toolbar on pages enabled with Rich Text Editor fields. Bug 34907223
2.1.2 No Keyboard Trap (Level A)	Supports	The product was tested for : Movement of focus to a control on the page 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: Inactivity timeout length is configurable by the Administrator. 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. Time limit configured for dismissing process scheduler pop-up notifications is correctly handled.
2.2.2 Pause, Stop, Hide (Level A)	Supports	This 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: Skip repetitive navigation links. Removal of duplicate links on pages to allow for easier navigation. Headers for page titles, group boxes, and scroll areas. Skip navigation functionality. WAI-ARIA Landmark to identify regions of a page.
2.4.2 Page Titled(Level A)	Supports	The product was tested for: Has meaningful page titles 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. Exceptions to the above are as follows: Tab Order set conditionally through application business logic is lost on pages enabled with Rich Text Editor fields. Bug 35073834 and Bug 35776682. Focus is lost after Spell Check Modal Window is closed when spell check is on pages enabled with Rich Text Editor fields. Bug 35073907.
2.4.4 Link Purpose (In Context)(Level A)	Supports	The product was tested for: The purpose of delivered links can be understood, its labels are meaningful and that labels are not vaguely worded.
2.4.5 Multiple Ways(Level AA)	Supports	The product provides multiple ways to navigate to a page including: Drop down menu. Navigation Menu or Navigation Bar( NavBar) Related Actions. Links on a page. Tiles(buttons) on a homepage. Button bars (radio buttons). Global Search feature to find a page. Favorites.
2.4.6 Headings and Labels(Level AA)	Partially 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. Exceptions to the above are as follows: Label of a Rich Text Edit field on a page is always "Rich Text Editor" - this label is not getting generated dynamically and is missing the context of the field. Bug 35073849.
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)	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 : There are no single pointer operations
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 Web pages.
3.1.2 Language of Parts(Level AA)	Supports	The product was tested for: There are no passages or phrases that are different from the language 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. If the application does program substantial changes to the page, PeopleTools provides the ability to issue warnings first.
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.
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 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: PeopleTools error messages allow the ability to provide instruction with the error on how a user can resolve the issue.
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)	Supports	This product was tested for: Elements in 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.
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. Exceptions to the above are as follows: Status messages are not automatically announced for row counts on pages with grids. Bug 32651775.

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria	Conformance Level	Remarks and Explanations
302.1 Without Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited Vision	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of Color	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited Hearing	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without Speech	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited Manipulation	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and Strength	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning Abilities	Not Applicable	The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

Chapter 4: Hardware

These criteria are all Not Applicable because the product is not Hardware

Chapter 5: Software

Criteria	Conformance Level	Remarks and Explanations
501.1 Scope - Incorporation of WCAG 2.0 AA	Supports	See the responses in the WCAG 2.0 section of this report.
502 Interoperability with Assistive Technology	Heading cell - no response required	Heading cell - no response required
502.2.1 User Control of Accessibility Features	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility Features	Not Applicable	The product is designed to be isolated from the underlying platform.
502.3 Accessibility Services	Heading cell - no response required	Heading cell - no response required
502.3.1 Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object Information	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and Headers	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.4 Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of Values	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.6 Label Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical Relationships	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.8 Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of Text	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.10 List of Actions	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on Objects	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus Cursor	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.3.14 Event Notification	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility Features	Not Applicable	The product is not a platform or does not have access to platform accessibility features.
503 Applications	Heading cell - no response required	Heading cell - no response required
503.2 User Preferences	Not Applicable	The product is designed to be isolated from the underlying platform.
503.3 Alternative User Interfaces	Not Applicable	The product does not have assistive technology features.
503.4 User Controls for Captions and Audio Description	Heading cell - no response required	Heading cell - no response required
503.4.1 Caption Controls	Not Applicable	The product has no multimedia.
503.4.2 Audio Description Controls	Not Applicable	The product has no multimedia.
504 Authoring Tools	Heading cell - no response required	Heading cell - no response required
504.2 Content Creation or Editing	Supports	See the responses in the WCAG 2.0 section of this report.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Supports	The product was tested for : File conversion preserves accessibility information. RTF template format creates HTML accessible file format. RTF template format creates PDF accessible file format.
504.2.2 PDF Export	Supports	PeopleTools uses Oracle Analytics Publisher for PDF Export functionality. ACR for Oracle Analytics Publisher 6.4 has been linked in the Dependent Products section in this report.
504.3 Prompts	Not Supported	PeopleTools uses Oracle Analytics Publisher as an authoring tool. Oracle Analytic Publisher does not prompt for Level A and Level AA conformance.
504.4 Templates	Not Supported	Peopletools delivers templates generated using Oracle Analytic Publisher. Oracle Analytic Publisher does not prompt for Level A and Level AA conformance.

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.61 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 available 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.