Skip to content
Penn State University Libraries

Marion MacKinnon Adaptive Technology and Services

Penn State University Libraries' Web Accessibility Plan

Phase 1 Summary

December, 2011. Rev 7, 4.12.12

Mission:

Creating and maintaining an accessible web site is an ongoing Libraries priority and responsibility. Our goal is:

  • To provide effortless access for all students; faculty; staff; visitors; and the general public to the University Libraries’ online resources.
  • To foster ownership of accessibility across the Libraries web community to ensure that accessibility is designed into the Library web site, rather than addressed in a reactive manner for individualized accommodations.

The goal of Phase 1 of the Libraries’ Accessibility Plan is to have the Libraries’ web site (all pages, documents and media within the www.libraries.psu.edu domain, approximately 4,500 pages) and LionSearch meet WCAG 2.0 AA guidelines by the October 15, 2012 deadline as stated in the NFB Agreement.



Determining Accessibility Issues

Audit:

The original audit was conducted centrally by AIT committee members using HiSoftware’s Compliance Sheriff. The audit was done on the top 250 pages of the Libraries web site.

Automated Checking:

The Libraries are using two tools for automated accessibility checking of our web pages (both template and content). The SiteImprove/SiteCheck service has been in place since remediation began in August 2011. In February, 2012, when the University purchased the license to HiSoftware Compliance Sheriff, the Libraries began using the University-wide validation tool to be consistent with the remainder of the University’s Budget Executive units. HiSoftware’s Compliance Sheriff will check Web sites for WCAG 2.0 AA compliance, as well as accessibility of content such as PDF’s and Microsoft office files.

Manual Checking - Assistive Technology:

In addition to our automated checking, we employ an Assistive Technology Expert, who does regular, manual reviews of our pages and content using JAWs. Based on Google Analytics, the most visited pages and assets are checked first.

Top


Libraries Web Accessibility Team

  • Web Liaison/Project Manager
  • Web Accessibility and Content Specialist
  • Web Accessibility and Content Assistants (part-time)
  • Assistive Technology Specialist
  • CMS Development Team
  • Author Expert Team (AET)
  • Technology Trainer
Top


Remediation Plan

Code:

The CMS Development Team will correct any accessibility issues that occur in the web site templates or components that authors use to add content to their pages. Content authors need to be concerned only with making sure the content they create is accessible. Where code causing accessibility issues is written by Adobe CQ and cannot be accessed by the developers, the Development Team will work with Adobe to correct these issues.

Content:

The Web Accessibility team will perform most of the content remediation. After author accessibility training begins in April, trained authors will take over page remediation on those pages for which they are responsible.

Assets:

The Libraries web pages include a number of assets including word, pdf, excel, powerpoint and video files. All of the assets will be made accessible or will be made available in alternate format by request.

Top


LionSearch

The Libraries is working closely with Serials Solutions to determine accessibility concerns of LionSearch (Summon). Summon is on a 2-week development cycle, and the Libraries will work with the Assistive Technology Expert and provide feedback to Serials Solutions to ensure this product meets the WCAG 2.0 AA guidelines.


Timeline

September, 2011

  • Implement SiteCheck
  • Full site inventory

October, 2011

  • Communication -Web Steering, Administration, Libraries at large

November, 2011

  • First round accessibility issues to Summon

January, 2012

  • Hire Web Accessibility and Content Specialist
  • Develop step by step review and remediation process - page groups
  • Meet with AET on template, code updates testing plan
  • Determine reasonable accommodation policy, guidelines and workflow
  • Determine exceptions policy and workflow

February, 2012

  • Second Round accessibility issues to Summon
  • Finalize Libraries Training Plan
  • Draft author/publisher policy (CMS Team)
  • Captioning and transcription plan for audio, video. Flash
  • Communication to CMS Authors on plan, reports, new accessibility guidelines, training

March

  • Third round accessibility issues to Summon
  • Develop Asset Remediation Plan
  • Implement Captioning and transcription plan for audio, video. Flash

April, 2012

  • Begin Training
  • Implement Asset remediation plan

June, 2012

  • All pages compliant (goal)

July, 2012

  • Implement revised author /publisher policy

October, 2012

  • Final compliance of Phase 1 achieved.
  • Begin Phase 2

TBD

  • Implement CQ5.5
Top


Web Accessibility Training Plan

Libraries Training for CQ5 Authors and Publishers

Author Training including:

  1. Top 6 blockers
  2. Multimedia Training
  3. Best Practices
  4. Formats: In-class training, Tech tips, Author emails, Interview (Libraries Newsletter)
  5. Publisher Training (Certification) -Integrated with University-wide training


Accessibility Training University-wide

Libraries faculty and staff are encouraged to participate in numerous trainings being provided to the University community on web accessibility, creation of accessible information; captioning, and plans for strategies to meet the Policy AD-69.

Top


Communications Plan

  • Administration:
    Monthly reporting to ITCC (joint proposal between I-Tech and Web Steer), Library Managament Council and Library Faculty Organization
  • Web Steering Committee (sponsor of accessibility plan):
    Bi-weekly reports (at each meeting - add to minutes).
  • CMS Authors/Publishers:
    Monthly updates for authors at Author forums and bi-weekly email updates.
  • Libraries:
    Monthy report via Interview newsletter, monthly Tech updates, Weekly Accessibility Tech Tips via Libraries’ newsletter.
  • University:
    Monthly reports atWeb Liaison meetings, bi-weekly AIT meetings and weekly Web Conference meetings.
Top


Collaborative Efforts:

Adobe

The Penn State University Libraries is working closely with the Adobe CQ5 development team on a number of development issues surrounding accessibility. (see Adobe Success Story )

  1. Components - forcing accessibility of components (force alt tags, required fields for tables, etc)
  2. Workflow - incorporate accessibility into workflow. All pages must be accessible before they can be activated
  3. Compliance Check - integrate HiSoftware’s API into Adobe CQ workflow for integrated compliance checking on a page by page basis.
Serials Solutions Summon

Summon is on a 2-week development cycle. After each bi-weekly release, the The Penn State University Libraries team reviews the Summon interface and does automated and manual checks on the search interface. The results are sent to the Summon developers to incorporate into their next development cycle.

SiteImprove/SiteCheck

The Penn State University Libraries worked closely with Site Improve on their beta release of the WCAG 2.0 Web Governance Suite, including testing and feedback.

(see Press Release )

HiSoftware Compliance Sheriff

The University Libraries is working to coordinate a collaboration between HiSoftware and Adobe to incorporate the HiSoftware API into the Adobe CQ5 procut workflow for in-page accessibility checking at the content author level.

Top


Libraries Innovation Microgrant

In October, 2011, three web developers in I-Tech received a Libraries Innovation Microgrant for a “Screen Reader’s Guide to Navigating Online Library Resources”. The purpose of this project is to create a more welcoming online environment for our users with disabilities. We will produce context appropriate tip sheets for navigating and using key resources with screen readers. These guides will be discoverable by screen readers on entry points to key resources. Creating a Screen Reader’s Guide will allow users to independently and more easily navigate the Libraries’ web site as well as our third party tools such as database aggregators, e-journals, library software applications, etc. Prototyping of database guides was done through a Bednar internship in 2004. This project will continue that work and bring it into production. At the conclusion of the project, we’d like to collaborate and benchmark with other universities on this initiative.

Top


Libraries’ Accessibility Activities:

  • Host Monthly Web Liaisons, broadcast to campuses
  • Host bi-weekly AIT Committee Meetings
  • Accessibility updates at monthly Libraries-wide tech updates - (University Park and broadcast to all campuses)
  • Accessibility updates at monthly author forums - (University Park and broadcast to all campuses)
  • Board and attendees of Penn State Web Conference 2011
  • Board and attendees of Penn State Web Conference 2012
  • Hosted Online Accessibility Summit for university-wide audience - September, 2011
  • Senate Committee on Libraries, Information Systems, and Technology - January, 2012
  • Serving Deaf Patrons in the Library (Webinar) - February, 2012
  • Making the Libraries’ Web Site More Accessible, Presentation - April, 2012
  • Serving Blind and Visually Impaired Patrons at the Library, Webinar - June, 2012
Top