Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

PeopleSoft Enterprise PeopleTools (September 2017 revision) 8.56

Product Description:

This VPAT applies to the end-user content generated by the PeopleSoft Internet Architecture (PIA) for PeopleTools 8.56 while in Accessible mode.

Date:

01-Mar-2018

Archive Note:

This VPAT applies to only September 2017 revision of version 8.56. It does not apply to any versions of PeopleSoft Enterprise PeopleTools after this. This VPAT has been superseded by PeopleSoft Enterprise PeopleTools 8.60.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT 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, are not accessible products.
The PeopleTools online product – PeopleSoft Update Manager - is not accessible.
The PeopleTools online product - Health Center - is currently not accessible. The bug tracking all of the accessibility issues with this product is 21977268.
The reporting tools delivered with PeopleTools, such as BI 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 BI Publisher Report Designer's Guide. HTML is the supported output type for consuming accessible reports. Further, PDF Files generated using BI Publisher tools are not accessible. The BI Publisher VPAT has been linked to this VPAT.
Oracle Help Center, Library Version
Product Documentation in PDF format.

Accessible 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 accessibility mode. The first method is at sign-on, where the user can select a checkbox directly on the sign-on page to enable accessible 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 accessible user mode. The UI mode is set via the user preferences in PeopleTools Personalizations. To set accessible 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 Accessible Layout'.

There is a section in the Peoplebooks- PeopleSoft Accessibility Guide titled "Setting Up PeopleSoft Accessibility Features" that further explains the steps to configure 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.0, at https://www.w3.org/TR/2008/REC-WCAG20-20081211/	Level A - Yes Level AA - Yes Level AAA - No
Section 508 as published in 2017, at https://www.Section508.gov	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.
Supports with Exceptions: 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.0 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.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content (Level A)	Supports with Exceptions	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. PDF reports that are generated using the appropriate SQR commands to support Table, List, Paragraph, Heading, etc conform to this requirement. 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. There are exceptions in the following areas: Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with them. Bug 18414506 is tracking this issue.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)	Not Applicable	The product does not utilize audio-only or prerecorded video-only media.
1.2.2 Captions (Prerecorded) (Level A)	Not Applicable	The product does not utilize prerecorded audio content.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)	Not Applicable	The product does not utilize video synchronized media.
1.2.4 Captions (Live) (Level AA)	Not Applicable	The product does not utilize live audio content.
1.2.5 Audio Description (Prerecorded) (Level AA)	Not Applicable	The product does not utilize prerecorded video content.
1.3.1 Info and Relationships (Level A)	Supports with Exceptions	The product was tested for: Column and Row headers on data tables. No information is solely conveyed through the style sheet. Tables (Grids and Group Boxes) used for presentation are marked up correctly for layout purposes 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 Layout tables use appropriate markup Groups of components are marked up with their description There are exceptions in the following areas: Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with it. Bug 18414506. 27372226 Issues with personalization page feature in screen reader mode
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	This product does not use color or shapes as the only means of providing information or guidance to the user.
1.4.1 Use of Color(Level A)	Supports	This product does not use color as the only means of providing information.
1.4.2 Audio Control(Level A)	Not Applicable	The product has no feature that automatically plays audio.
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 "Tangerine" , Tangerine Fluid" and "Classic Plus" have been tested to conform to the Large text and contrast requirements. Some areas of the older stylesheets do not meet high contrast mode or color contrast mode. The settings in these stylesheets can be changed and overridden by user, browser system or operating system.
1.4.4 Resize text(Level AA)	Supports with Exceptions	The product was tested for : Text can be resized up to 200% without loss of content or functionality. The exception to this is with Fluid pages on Apple iOS where Pinch zoom is disabled. Bug 18907564.
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.
2.1.1 Keyboard(Level A)	Supports with Exceptions	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. Proper and Consistent use of keyboard keys to perform selection and action. Hotkeys/keyboard shortcuts available to skip elements Known Exceptions: Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with them. Bug 18414506. Issues with personalization page feature in screen reader mode. Bug 2737226.
2.1.2 No Keyboard Trap (Level A)	Supports	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.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.
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. Table headers for widgets such as grids and group boxes. Headers for page titles and scroll areas. Skip Nav functionality.
2.4.2 Page Titled(Level A)	Supports	The product has meaningful page titles specified in the TITLE element.
2.4.3 Focus Order(Level A)	Supports	The default tab order is controlled by the order of the fields in the HTML. However applications can alter this order when they deem necessary. 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. Hotkeys/keyboard shortcuts available to skip elements.
2.4.4 Link Purpose (In Context)(Level A)	Supports with Exceptions	The product was tested to ensure that the purpose of delivered links can be understood, its labels are meaningful and that labels are not vaguely worded. There is one known Exception Issues with personalization page feature in screen reader mode.Bug 27372226.
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 "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)	Supports	The product was tested for: Structure and hierarchy is conveyed using meaningful text in header elements on PIA and Fluid pages. Column and Row headers on data tables. Labels describe the purpose of the associated field.
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. Visual indication of the location of the focus.
3.1.1 Language of Page(Level A)	Supports	The product was tested for: Properly set lang attribute for each Web page.
3.1.2 Language of Parts(Level AA)	Supports	The product does not support multiple languages on the same page.
3.2.1 On Focus(Level A)	Supports	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	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 each time.
3.2.4 Consistent Identification(Level AA)	Supports	This product has been tested to ensure a consistent UI. PeopleTools has some inconsistencies between its classic UI compared to the new Fluid UI available from 8.54 onwards. The entire user experience is different with Fluid pages. A user can navigate between classic PIA and Fluid which can results in an inconsistent UI. However the Fluid Header and NavBar are available in both classic and Fluid to to help with a consistent UI.
3.3.1 Error Identification(Level A)	Supports	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	This product was tested for meaningful Labels and ALT text.
3.3.3 Error Suggestion (Level AA)	Supports	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	PeopleTools allow applications the ability to display Error messages. Confirmation pages where necessary. Undo functionality. PeopleTools provides the flexibility to the application to show these pages when the situation requires it.
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. There are exceptions in the following areas: Homepages, work center with multiple pagelets, grouplets and grids show Duplicate ID's when tested with Accessibility Tools. Bug's 24322172. The product itself has been tested for Accessibility and there is no accessibility impact.
4.1.2 Name, Role, Value (Level A)	Supports with Exceptions	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. There is one noted exception as follows: Fluid contains some widgets such as, the landing page drop down, that are incorrectly marked up as buttons and do not have the correct keyboard operations associated with them. Bug 18414506.

2017 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	5Heading 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	5Heading 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	5Heading 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	5Heading cell - no response required
503.4.1 Caption Controls	Not Applicable	PeopleTools software does not display any videos.
503.4.2 Audio Description Controls	Not Applicable	Peopletools does not play any Audio.
504 Authoring Tools	Heading cell - no response required	5Heading 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 with Exceptions	The product was tested for: File conversion preserves accessibility information. RTF template format creates HTML accessible file format. Exception: PDF format does not conform to WCAG 2.0 guideline. Peopletools uses Oracle Business Intelligence Publisher 12.2.1.1 and this exception has been called out in Oracle Business Intelligence Publisher Updated 12.2.1.1 (#7194) VPAT
504.2.2 PDF Export	Supports with Exceptions	PeopleTools uses Oracle Business Intelligence Publisher for PDF Export functionality. VPAT for Oracle Business Intelligence Publisher Updated 12.2.1.1 has been linked in the Dependent Products section in this report.
504.3 Prompts	Not Supported	PeopleTools does not have a authoring tool. PeopleTools uses BI Publisher and BI Publisher does not prompt for Level A and Level AA conformance. This lack of support has been called out in Oracle Business Intelligence Publisher Updated 12.2.1.1 (#7194) VPAT.
504.4 Templates	Supports	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	5Heading cell - no response required
602.2 Accessibility and Compatibility Features	Supports	The product documentation includes: Documentation on how to use accessibility features Documentation on accessibility features that provide compatibility with assistive technology
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	5Heading 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.