Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

This page details the Digital Accessibility and Content (DAC) team’s response to any reported accessibility issues regarding our supported systems. This applies both to issues we are able to remediate in house and issues that must be deferred to the vendor for triage and remediation.

Replicate and Document the Issue

Attempt to validate the reported issue, determine the extent and severity of the associated accessibility barrier(s), and assign remediation and response to the appropriate responsible party.

In-House Remediation and Response

If the responsible party is the system administrator or an internal content contributor, the issue should be resolved in house. Please refer to the follow resources for guidance and consultation as necessary:

Vendor Remediation and Response

Issues that cannot be remediated in house must be escalated to the vendor for resolution. Even if the system administrator or an internal content contributor is able to craft a workaround for a reported accessibility issues, it is important to inform the vendor, such that the underlying bug is addressed as soon as possible.

  1. Prepare a vendor specific report using the Accessibility Incident Validation Template.

  2. Prepare an Equally Effective Alternative Access Plan to mitigate the impact of validated accessibility barriers until they are remediated

  3. Send a customized version of the following email template to the vendor:

 Vendor Contact Email Template

[VENDOR CONTACT],

My name is [YOUR NAME], and I am the system administrator for [SYSTEM NAME] at Portland State University (PSU). I am writing to inform you about [AN/SOME] accessibility [ISSUE/ISSUES] we’ve encountered. These validated bugs render [SYSTEM NAME] out of compliance with the World Wide Web Consortium’s Web Content Accessibility Guidelines (WCAG) and may pose substantial accessibility barriers for users with disabilities at PSU.

The accessibility of our systems to people with disabilities is required under PSU’s Digital Accessibility Policy. Please reference this [LINK TO ACCESSIBILITY INCIDENT VALIDATION SPREADSHEET] for a list of identified accessibility bugs and their corresponding WCAG Success Criteria.

At your earliest convenience, please provide an IT Accessibility Roadmap, including remediation timelines and any known workarounds that will allow equitable access until each bug is resolved.

Thanks,

[YOUR NAME]

Follow Up with Customer

Respond to the customer via the associated ticket, providing a synopsis of your accessibility incident response, including any relevant information regarding:

  1. In-House Remediation and Response

  2. Vendor Remediation and Response

 Customer Follow Up Email Template

[CUSTOMER NAME],

Thank you for reporting [THIS/THESE] accessibility [ISSUE/ISSUES]. We’ve conducted an internal assessment and consulted with the vendor, and determined that [THIS/THESE] accessibility [ISSUE/ISSUES] [MAY BE REMEDIATED IN HOUSE/MUST BE ADDRESSED BOTH INTERNALLY AND BY THE VENDOR/MUST BE ADDRESSED BY THE VENDOR].

The following [ISSUE/ISSUES] should be remediated in-house by [DATE]:

  • [Issue - Remediated/Remediation In Progress]

The following [ISSUE/ISSUES] were reported to the vendor and are expected to be remediated by [DATE]:

  • [Issue - Remediated/Remediation In Progress]

In the meantime, please reference this [LINK TO EQUALLY EFFECTIVE ALTERNATE ACCESS PLAN (EEAAP)] for workarounds. This EEAAP has been developed and shared with the Office of Human Resources and the Disability Resource Center, in consultation with the Office of Information Technology’s Digital Accessibility and Content team.

Best,

[YOUR NAME]

  • No labels