This procedure supports Michigan Technological University's Accessible Information and Communication Technology (ICT) Policy 1.15. It applies to electronic documents made available on public facing University webpages within the mtu.edu domain and associated subdomains, and includes web-based documents from third-party services purchased for core business and academic activities. Examples of common document file formats covered in these procedures include PDF (.pdf), Word (.docx), and PowerPoint (.pptx).
Michigan Tech has adopted the Web Content Accessibility Guidelines (WCAG) 2.0 AA conformance level to measure, coordinate and implement compliance with the University Accessible ICT policy. Electronic documents should comply with WCAG 2.0 guidelines and success criteria as applied to non-web ICT content. Consult the World Wide Web Consortium (W3C) Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies Working Group Note September 5, 2013 for further information.
Michigan Tech has assigned web accessibility coordinator responsibilities including the coordination, implementation of, and compliance with the University Accessible ICT policy to the ICT Accessibility Coordinator, IT Communication and Accessibility Manager, and their respective designees.
Document accessibility training is required for any faculty, staff, administrators, and student employees who are responsible for the creation and/or distribution of electronic documents housed in official University websites or third party sites used in core academic and business activities. The training will provide information on how to create accessible documents or remediate existing documents to make them accessible.
Identifying Issues via Audits
Web accessibility audits will be conducted on a periodic basis. These audits will measure online content against the technical standard adopted in these document accessibility procedures. Inaccessible electronic documents housed in official University websites will be documented.
This procedure explicitly grants the ICT Accessibility Coordinator, IT Communication and Accessibility Manager, or their designees, the authority to take corrective actions.
In-House Created Content
Inaccessible documents created by Michigan Tech personnel must be remediated (where feasible), replaced with accessible versions, or removed.
- An initial notice of policy violation will be submitted to the web liaison or responsible party by the ICT Accessibility Coordinator, IT Communication and Accessibility Manager or designated individual, including a due date for correction not sooner than 30 days from the date of notice.
- If not corrected by the notice due date, a second notice of policy violation will be submitted to the web liaison or responsible party and their supervisor, including a due date for correction not sooner than 30 days from the date of the second notice.
- If not corrected by the second notice due date, a third notice of policy violation will be submitted to the web liaison or responsible party and their supervisor, with notice of the date when corrective action must be taken not sooner than 30 days from the date of third notice.
- If a corrective action is not taken during this outlined timeline, removal of the electronic documents in question or unpublishing of the page or website on which they reside may occur.
Formal appeals must be submitted using the Accessible Information and Communication Technology (ICT) Correction Appeal Form. Upon receipt, the correction process will be put on hold while the appeal is evaluated. The Accessible Technology Coordinator and IT Communication and Accessibility Manager will manage the appeal process with final authority residing with Equal Opportunity Compliance. All appeal decisions will be made within 30 days.
A recommended checklist is offered below for web liaison or responsible parties of inaccessible documents to help determine appropriate action:
- Determine if it’s necessary to continue posting the document on the website. You may discover that a document’s useful life has ended. If so, remove it. A document’s access history can be provided to help with this determination.
- Determine whether to remediate the existing document or create a new accessible version. Remediation may be appropriate if you have access to the source document (Word, Google Doc, etc.) versus the PDF version on the web. While it is possible to remediate PDF files for accessibility, it can be a time-consuming process depending on document complexity.
- If document remediation is not elected, creating a new, accessible version of the document is usually the more efficient recommended option.