Build Accessibility Into Every Document: A Self‑Paced Guide for Faculty, Editors, and Teams

Two colleagues sit at a table in a bright office, reviewing a printed document next to an open laptop; a pink mug and notebooks are on the table, with plants and a window in the background.

Why Document Accessibility?

Digital documents are used and shared across every context at U-M. Course syllabi, meeting minutes, hiring materials, and much more. Document accessibility means using best practices, tools, and workflows, so that you can easily create accessible documents each and every time. And that means your docs can be used by everyone without barriers, including people with disabilities, and people who rely on assistive technology. 

Learn on Your own

Explore tools and step-by-step guidance on how to improve your documents at your own pace.

Make Progress

Make small changes to improve document accessibility as you go. Begin anywhere and build on the momentum. Do one (or more) of the following this month:

For Faculty and Instructors

  • Check your syllabus for accessibility, with Grackle or Microsoft Word, and make improvements.
  • Add alt text to instructional images.
  • Use templates to create consistent, accessible materials.

For Content Editors and Communicators

  • Use accessible templates for reports, newsletters, and materials.
  • Write descriptive link text (avoid “click here”).
  • Ensure proper heading structure for readability.
  • Build accessibility into your content workflows.

For Developers and Technical Teams

  • Ensure document outputs from systems are accessible by default.
  • Provide accessible templates for teams and users.
  • Support tools like Grackle Docs across units.
  • Test document accessibility in workflows and integrations.
  • Partner with content creators to reduce accessibility gaps.

Focus on the documents you create most often to build accessibility into your workflows now and moving forward.