Accessibility

AHG 2017 Conference: University of Colorado’s session about making PeopleSoft accessible

By Hendrix Bodden • August 6, 2017

The 2017 Accessing Higher Ground conference focuses on the implementation and benefits of:

  • Accessible media, Universal Design and Assistive Technology in the university, business and public sectors;
  • Legal and policy issues, including ADA and Section 508 compliance;
  • Creation of accessible media and information resources, including web pages and library resources.

Our customer – University of Colorado – will present their GreyHeller accessibility project at the conference – Implementing GreyHeller PeopleMobile in PeopleSoft Campus Solutions: Lessons Learned.

Summary

Learn about University of Colorado’s implementation of accessibility improvements for PeopleSoft Campus Solutions student self-service, using the GreyHeller PeopleMobile product.

Abstract

Over the past three years, the University of Colorado has focused on remediation and improvement of accessibility problems for PeopleSoft applications, with specific attention on PeopleSoft Campus Solutions self-service functionality. Campus Solutions 9.0, particularly student self-service, does not provide a useable experience for those using assistive technology such as screen readers. At the University of Colorado our goal is to provide an accessible and useable systems that follows WCAG 2.0 AA guidelines.

Stay Updated

Accessibility

University of Minnesota made PeopleSoft truly accessible. Here’s how.

By Hendrix Bodden • August 6, 2017

Leveraging GreyHeller’s PeopleUX technology platform, our customer – University of Minnesota – made its Student Self-Service, Faculty, Job Applicant components accessible and Section 508/WCAG 2.0 compliant.

The University set the PeopleSoft Accessibility bar at providing parity of access for its visually impaired students. It therefore needed to satisfy these critical requirements:
• All functionality had to be available if the keyboard was the only means of interaction
• All functionality had to be easy to use – versus merely render-able – on accessibility devices
• Functionality could not be disabled because rendering on accessibility devices was problematic.

Semantic HTML
The structure of the PeopleSoft HTML was transformed into proper semantic structure for use with accessibility devices.

Navigation and Taxonomy
To assist with end-user navigation through the dozens of elements on a PeopleSoft page and between the hundreds of pages a user may have access to, attributes were set and HTML was transformed using PeopleMobile®.
End-User Interaction
As an end-user reads and updates information in PeopleSoft, form and AJAX processing cause screen readers to lose track of where an end-user is in the page, causing significant productivity and usability issues. PeopleMobile® addressed this in the following ways.

• Highlighting focused content– content currently being updated

• Remembering scroll position after returning from prompts, AJAX updates, or
other processing

• Remembering the end-user’s focus on page load

Project Approach
The University prioritized the self-service functions into a list of 71 Use Cases and divided them up into 5 phases. Only users registered as Accessibility users have access to the PeopleMobile® product, so the focus of the implementation was to provide a screen reader user experience. The University deployed 10 Use Cases at a time – introducing functionality in phases rather than waiting until all Use Cases had been approved. Each month UMN went live with a new group of Use Cases, and each go live was accompanied by communications to the user group.

White Paper
To get a copy of our University of Minnesota White Paper, email us at info@devappsian.wpengine.com

Stay Updated