Conduct Accessibility Documentation Reviews

This page describes the Digital Accessibility and Content (DAC) team’s role in completing accessibility documentation reviews as a part of the IT solution and service contract review process.

Assigning the Request

When the PMO creates a subtask to an existing IT solution and service contract review ticket in the IT Service Desk and assigns it to the “OIT Digital Accessibility and Content” service desk team:

1. The Digital Accessibility Support Specialist or Digital Accessibility and Content Graduate Administrative Assistant will add an “Accessibility” label to the subtask.

2. The Digital Accessibility Support Specialist or Digital Accessibility and Content Graduate Administrative Assistant will assign themselves to the subtask and determine whether sufficient accessibility documentation is available for review via the parent ticket.

   • Accessibility documentation may include but is not limited to an IT Risk and Accessibility Review (ITRAR), and/or WCAG-specific Accessibility Conformance Report (ACR) using the Voluntary Product Accessibility Template (VPAT). Note that some WCAG-specific accessibility documentation is necessary for any informed accessibility analysis or risk assessment to occur.

Processing the Request

The DAC team will review accessibility-related responses to the ITRAR and any WCAG-specific accessibility documentation as follows, with the intent to inform and advise clients regarding any digital accessibility risk:

1. Make a copy of the Accessibility Documentation Review Template and save to the Accessibility Documentation Reviews folder the OIT-DAC Shared Drive.

2. Rename the document according to the following template: ITSD-[Ticket#] ACR Review for [Technology].

3. Evaluate all metadata and responses and/or commentary regarding specific WCAG success criteria.

   • Pay particular attention to Published Report Date, Applied Standards, Date of Evaluation, Identified Evaluators, and Evaluation Methods.

   • Note WCAG success criteria exceptions, including Significant Accessibility Barriers (Partially/Does Not Support), Other Not Supported Criteria (Does Not Support), Other Partially Supported Criteria, (Partially Supports), and Users with Disabilities Affected.

     • Reference the Understanding WCAG 2.2 web page to note Users with Disabilities Affected.

4. Summarize relevant metadata and the top three to five Significant Accessibility Barriers using a modified version of the Sample Client Response in the Accessibility Documentation Review Template.

Closing the Request

The DAC team will share their risk assessment with the client as follows, via the parent ticket, and subsequently close the subtask. Clients may ask follow-up questions via the parent ticket.

1. Send the drafted client response via the parent ticket.

2. Using an Internal Comment, paste a copy of the initial response in the subtask. 

3. Add all relevant data to the EEAAP Completion Tracking spreadsheet.

4. Resolve the subtask.