Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

PeopleSoft Campus Solutions Applications (February 2018 revision) 9.2x

Product Description:

This VPAT summarizes:

  • PeopleSoft Campus Solutions Applications version 9.2x which is dependent on the PeopleSoft Enterprise Tools VPAT.
  • PeopleSoft Campus Mobile, a native application for the iOS and Android operating systems, which is dependent on the Mobile Application Framework VPAT.

Date:

03-Apr-2018

Archive Note:

This VPAT applies to only version February 2018. It does not apply to any versions of PeopleSoft Campus Solutions Applications 9.2x after this. This VPAT has been superseded by PeopleSoft Campus Solutions Applications (December 2019 revision) 9.2x.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

  • This VPAT only applies to pages within the Campus 9.2x products which are either self service, for example Student Center, or high visibility administration pages, for example Build Program.
  • BI Publisher (XMLP) reports are delivered as sample reports.  The usage of these sample reports are intended for printing purposes only and therefore are not considered accessible.  The content contained within these sample reports may be obtained and viewed through alternate accessible means such as an online page or query.
  • Delivered application SQR reports are considered to be samples.  The majority of these reports are intended for printing purposes only and therefore are not considered accessible.  The content within these sample reports may be obtained and viewed through alternate accessible mean such as an online page or query.
  • Oracle Help Center, Library Version and Product Documentation in PDF format are not covered by this VPAT.
  • Third-party products often configured with PeopleSoft Campus Solutions are not covered by this VPAT.

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 document "Enterprise PeopleTools 8.56 PeopleBook: PeopleSoft Accessibility Guide" titled "Setting Up PeopleSoft Accessibility Features" that further explains the steps to configure Screen Reader mode in the application.

Dependent Products


This product interacts with or is built with the other Oracle products listedin this section. Click below to view information about the accessibility ofthese dependent products. Products listed are the versions available at thetime of publication of this document; newer documents may be available that supersedethese versions.

Evaluation Methods Used:

Oracle's policy is to design, develop and test both products and documentation to be accessible. The recommended styles of testing for accessibility include: (i) algorithmic automated tests, (ii) human judgement tests such as tool-assisted tests, visual inspection and manual operation, and (iii) testing with assistive technology by people with and without disabilities. Additional information about Oracle's accessibility program is available on http://www.oracle.com/corporate/accessibility/index.html

Accessibility Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guideline:

Standard/GuidelineIncluded 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.govYes

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

Exceptions to the above are as follows:

  • Two pages were identified where decorative images, used for visual purposes only, had a label.  Bug 21920193.
  • Eight pages were identified where the "ALT text" was not provided for images in a page.  Bug 21920396.
  • Two pages were identified where images were not noted as such.  Bug 21920415.
  • One page was identified where when the pictures (images) were turned OFF, the "ALT Text" was not shown instead of the image.  Bug 21924771.
  • One page was identified where when the user tabs to a radio button with multiple radio buttons, the screen reader did not read the number of radio buttons.  Bug 21924829.
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 layout purposes.

Exceptions to the above are as follows:

  • Six pages were identified where not all form fields had a label in the left column. Bug 21924875.
  • Three pages were identified where grids had their borders and controls hidden and were not visually a table in standard mode, yet they were identified as a table in accessibility mode.  Bug 21924938.
  • Twenty-one pages were identified with improper tables (grids).  Bug 21924987.
  • Twelve pages were identified where the labels in the table summary and column headers to did not make sense in accessible mode.  Bug 21925011.
  • Two pages were identified where the tables identified by the Table Inspector did not appear as a table visually in standard mode.  Bug 21925047. 
  • Seven pages were identified where there were objects that did not look like a heading but were noted as a heading, yet there was no error.  Bug 21925072. 
  • Four pages were identified where there were objects that looked like a heading but did not get noted as a heading, yet there was no error.  Bug 21925103. 
  • Eleven pages were identified using a screen reader where grid column headings were not available for Add, Delete, Row Number or Row Selection Indicator Columns in a grid.  Bug 21925163. 
1.3.2 Meaningful Sequence(Level A)Supports with Exceptions

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

Exceptions to the above are as follows:

  • Two pages were identified where items did not appear in a logical order in the flow of the page.  Bug 21925219.
1.3.3 Sensory Characteristics(Level A)Supports with Exceptions

The product does not use color, shape, size or sound as the only means of conveying content or guidance to the user.  This product was tested for sensory characteristics of components such as  visual location and orientation.

Exceptions to the above are as follows:

  • One page was identified where directional text was used and did not provide specific instructions on what the user needed to do.  E.g., Instead of text stating "Press the below button" it should state "Press the Continue, Back, Save button below".  Bug 21925247. 
  • Two pages were identified where labels were not close in proximity to the entry field/ field or were they were not on the left of the combo box.  Pages were identified where labels were not to the right of a check box for a consistent look and feel.  Bug 21925346.
1.4.1 Use of Color(Level A)Supports

The product does not use colors as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

1.4.2 Audio Control(Level A)Not Applicable

The product does not utilize audio based media.

1.4.3 Contrast (Minimum) (Level AA)Supports with Exceptions

The product was tested for visual presentation of text to ensure that  a contrast ratio of at least 4.5:1 is applicable.   Images of text are not utilized in the product.

The visual presentation of the product is delivered using a specific PeopleTool's style sheet, "Tangerine" 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.

Exceptions to the above are as follows:

  • Twelve pages were identified where the color contrast analyzer identified issues.  Bug 21925384.
1.4.4 Resize text(Level AA)Supports

The product was tested for browser zoom up to 200%.

1.4.5 Images of Text(Level AA)Not Applicable

The product does not utilize images of text.

2.1.1 Keyboard(Level A)Supports

The product does not disrupt the features related to accessibility on the end users platform.   Hotkeys/keyboard shortcuts are available for certain functions of the product.

The product was tested for:

  • Consistent use of keyboard keys to perform selection and action.
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 options to continue or exit.
  • Inactivity timeout length is configurable by the Administrator.
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 to ensure that elements do not flash or blink outside of the required thresholds.

2.4.1 Bypass Blocks(Level A)Supports

The product provides 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 with Exceptions

The product was tested for meaningful titles that describe the topic or purpose of the web page.

Exceptions to the above are as follows:

  • Twenty-eight pages were identified where the title was not considered meaningful.  Bug 21925406.
2.4.3 Focus Order(Level A)Supports with Exceptions

The product  was tested for:

  • Logical tab order through the product controls and selectable elements.
  • Consistent use of keyboard keys to perform selection and action.


Exceptions to the above are as follows:

  • One page was identified where the tab order in accessibility mode was not the same as in standard mode.  Bug 21925424.
  • Three pages were identified where the tab order was not in a logical form (e.g., top down or left to right and in sequence).  Bug 21925466.
  • Two pages were identified where page objects were not ordered by tab order.  Bug 21925466.
2.4.4 Link Purpose (In Context)(Level A)Supports with Exceptions

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.

Exceptions to the above are as follows:

  • Three pages were identified where the mouse over text for a button did not convey a consistent meaning.  Bug 21925513.
  • Three pages were identified where the mouse over text for links and images did not convey a consistent meaning.  Bug 21925604.
  • Three pages were identified where the label did not appropriately describe the purpose for a link.  Bug 21925619.
2.4.5 Multiple Ways(Level AA)Supports

The product provides multiple methods to navigate to a page including:

  • Drop down menu.
  • Related Actions.
  • Links on a page.
  • Search feature to find a page.
2.4.6 Headings and Labels(Level AA)Supports with Exceptions

The product was tested for:

  • Structure and hierarchy conveys meaningful text in header elements on pages.
  • Column and Row headers on data tables.

Exceptions to the above are as follows:

  • Seven pages were identified where the label was not appropriate for the control/field.  Bug 21925934.
  • Ten pages were identified where the page lists were not tagged with the appropriate list titles.  Bug 21925965.
  • Ten pages were identified without the appropriate header information.  Bug 21926013.
  • Two pages were identified where the row headers did not uniquely identify the row.  Bug 21926112.
  • Four pages were identified where grid columns did not have labels.  Bug 21926214.
  • Eight pages were identified where grid boxes and grids did not have titles.  Bug 21926258.
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.
  • AT product successfully tracks cursor focus.
3.1.1 Language of Page(Level A)Supports

The product was tested to ensure the language of the page can be determined.

3.1.2 Language of Parts(Level AA)Supports

The product was tested to ensure the language of the page can be determined.

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.

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 with Exceptions

The product has been tested to ensure a consistent User Interface.

Exceptions to the above are as follows:

  • One page was identified where objects within the page did not operate consistently.  Bug  21926281.
3.3.1 Error Identification(Level A)Supports

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 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 with Exceptions

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)Supports with Exceptions

The application was tested for:

  • Duplicate IDs in the HTML.
  • Elements in the HTML have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs.
  • Pages validate to the HTML specification.

Exceptions to the above are as follows:

  • Four pages were identified where form fields do not have a unique label.  Bug 21926330.
4.1.2 Name, Role, Value (Level A)Supports

The product was tested in accessible mode 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.

back to top

2017 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 EditingSupports

See WCAG 2.0 Section.

504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot Applicable

The product does not include authoring tools that provide format conversions or saving content in multiple formats.

504.2.2 PDF ExportNot Applicable

The product does not provide export of PDF files.

504.3 PromptsNot Supported

The product does not prompt authors to create accessible content.   Bug 27596409.

504.4 TemplatesNot Applicable

The product does not provide templates.

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 describes:

  • Screen Reader mode user preferences and runtime.
  • Special keystrokes needed to operate controls.
  • Workarounds.

Accessibility-related documentation can be found in the Enterprise PeopleTools 8.56 PeopleBook: 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 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.