Communications Toolkit

Want to help people understand the purpose and goals of the Digital Accessibility Strategic Initiative? Use our communications toolkit to raise awareness, advocate for resources, and prepare for action.

These resources are designed for use by communicators, Digital Accessibility Liaisons (DALs), leaders, and other advocates and partners.

Resources and Templates

Find materials you can reuse or adapt in the Google Drive folders linked below:

5 Key Messages

Clear and consistent communication is essential for fostering a culture of accessibility. Use these key messages to effectively share information about the initiative so everyone understands their role.

Shared Responsibility and Daily Integration

Everyone at U-M is responsible for digital accessibility, and everyone at U-M has the right to equitable digital access. We achieve this by embedding digital accessibility into everyday work practices across roles.

Compliance and Equitable Access

The University of Michigan is committed to complying with WCAG 2.1 AA standards by April 2026 to ensure that digital resources can be used equitably by everyone including people who rely on assistive technologies or have disabilities.

Leading by Example

U-M aims to be a leader in digital accessibility, serving as a model for other institutions and ensuring that all U-M teaching, research, and programs are accessible to our entire audience.

Roles and Resources

Key people, including instructors, IT staff, technology buyers, content creators, and leaders, have specific roles and need specialized resources to support digital accessibility. The Strategic Initiative develops tools, knowledge, and support for many different people to more effectively do their part.

Policy and Efficiency

We continually incorporate accessible design practices in order to meet U-M Policy (SPG 601.20) and legal requirements, and to avoid barriers and resource-intensive retroactive fixes in the future.

More Details and Documentation

Need more information? Explore the documentation below.