Digital Accessibility
Digital accessibility ensures that digital content can be used by everyone, including people with disabilities. This includes websites, PDFs, Word documents, presentations, videos, forms, and other online resources. Accessible content is designed so users can perceive, understand, navigate, and interact with information regardless of their abilities or the technologies they use, such as screen readers, keyboard navigation, captions, or other assistive tools. At UWM, digital accessibility is a shared responsibility for anyone who creates, publishes, or manages digital content.
This page provides staff with the guidance, resources, and best practices needed to create accessible digital content. Whether you are developing a website, sharing a document, creating a presentation, or publishing multimedia content, the information below will help you understand accessibility expectations, implement accessibility standards, and improve the usability of your content for all audiences. You’ll find practical guidance, accessibility principles, document-specific resources, and links to relevant university policies and requirements to help ensure your content is accessible from the start.
General Digital Accessibility Guidelines
General accessibility guidelines apply across websites, documents, videos, and communications because they ensure content can be perceived, understood, and used by people with a wide range of abilities. Following these guidelines—such as using clear structure, alternative text, captions, good contrast, and plain language—makes information more usable and inclusive for everyone, not just people with disabilities.
Accessible Document Format Decision Tree
The Accessible Document Format Decision Tree helps content creators select the most appropriate format for their content before it is created and shared. Because each format has different accessibility strengths, limitations, and use cases, choosing the right format at the beginning can improve usability, reduce remediation efforts, and help ensure content is accessible to all users. By guiding users through a series of questions about the purpose, audience, and intended use of their content, the decision tree recommends the format best suited for the situation. As a general rule of thumb, if HTML will work, choose HTML first, as web pages are typically the most accessible, flexible, and broadly supported format. Other formats such as PDFs, Word documents, Excel spreadsheets, and PowerPoint presentations should be used only when they best support the content’s purpose and can be made fully accessible.
Start here: What is the primary purpose of the content?
- ✅ Yes Use HTML (Web page)
- Most accessible to all users and flexible format
- Works well with screen readers, keyboards, mobile devices, and zoom
- Best for policies, instructions, announcements, and reference content
- ❌ No Go to next question
- ✅ Yes Use PDF
- Use only if layout must be fixed
- Must be properly tagged, have headings, alt text, readable order, and good contrast
- Avoid scanned PDFs unless processed with OCR and fully accessible
- ❌ No Go to next question
- ✅ Yes Use Word document
- Good for drafts, reports, and shared editing
- Use built‑in styles, headings, lists, and accessibility checker
- ❌ No Go to next question
- ✅ Yes Use Excel
- Best for structured data and analysis
- Use clear headers, simple tables, no merged cells, and accessible charts
- ❌ No Go to next question
- ✅ Yes Use PowerPoint
- Use for presentations and training
- Ensure slide titles, logical reading order, alt text, captions, and sufficient contrast
- ❌ No Go to next question
- ✅ Yes Choose carefully
- Ensure accessibility support (keyboard access, captions, labels)
- Provide an accessible alternative (often HTML or Word)
How Do I Make an Accessible Word Document?
Create Microsoft Word documents that are accessible to people with disabilities, compatible with assistive technologies like screen readers, and easier for everyone to use. The following checklist highlights those items that will make your Word documents accessible. The resource section at the bottom has links to more detailed information about the items listed here.
How Do I Create an Accessible Presentation?
How Do I Create an Accessible Spreadsheet?
Data is critical to the work we do at the University and is often shared through spreadsheets. However, some spreadsheets can create accessibility barriers:
- Ribbon-style menus (such as those in Excel) can be difficult for screen reader users to navigate.
- Charts and graphs without alternative text (alt text) prevent screen reader users from understanding the data.
- Large data sets without clear structure or definitions can be inaccessible to blind users, users with low vision, and users with cognitive disabilities.
How Do I Create an Accessible PDF?
Microsoft Word
Follow the instructions above to create an accessible Word document. Once the document is accessible, export by navigating to File > Export > Create PDF/XPS Document. Click Options, and ensure Document structure tags for accessibility is checked before saving.
Microsoft PowerPoint
Follow the instructions below to create an accessible PowerPoint document. Once the document is accessible, export by navigating to File > Export > Create PDF/XPS Document. Before publishing, click Options and ensure Document properties and Document structure tags for accessibility are checked.
Microsoft Excel
Follow the instructions above to below an accessible Excel document. Once the document is accessible, navigate to File > Save As > select PDF from the file type drop-down. Click Options and make sure Document structure tags for accessibility is checked.
Note: Always use the Accessibility Checker within Word, Excel, or PowerPoint (found under the Review tab) to identify and fix any lingering errors before saving your file.
Adobe InDesign PDFs
How Do I Make My Communications Accessible?
When creating emails, make sure they are accessible to people with disabilities, including visual, motor, cognitive, and hearing disabilities. Emails should follow the same general accessibility guidelines used for documents, with a few additional considerations specific to email.
Digital Accessibility Tools
The Tools section provides quick access to accessibility testing, remediation, and content creation tools that can help identify and resolve accessibility issues before content is published. These tools support the creation of accessible documents, websites, presentations, and other digital resources, making it easier for faculty and staff to evaluate content, improve usability, and meet accessibility requirements.
- Alt Text Decision Tree – Great tool for determining the type of alt text to use for an image
- Image Alt Text Creator from Arizona State University
- Color Contrast Checker from WebAIM or download the free Colour Contrast Analyser (CCA) application which has an eye dropper so you can select the color directly from your documents.
- PAC (PDF Accessibility Checker) – Free and robust tool for checking PDFs for accessibility against the WCAG standards required by law.
UWM Accessibility Resources
The UWM Resources section provides links to university-supported tools, services, training, templates, and reference materials that can help you create and maintain accessible digital content. These resources are intended to supplement the guidance on this page by offering additional assistance, detailed instructions, and campus-specific support to help faculty and staff meet accessibility requirements and create a more inclusive experience for all users.
- Digital Accessibility Website
- Accessible Documents and PDFs
- Check Microsoft Office Documents for Accessibility
- Accessibility and Universal Design Checklist – UWM Center for Advancing Student Learning (CASL)
- Training
Web Content Accessibility Guidelines (WCAG) Principles
The WCAG principles and guidelines are included on this page to help content creators understand the foundation behind accessibility best practices. Concepts such as alternative text, heading structure, color contrast, captions, keyboard navigation, and accessible documents all stem from the four WCAG principles: content must be Perceivable, Operable, Understandable, and Robust (POUR). By understanding these principles, UWM staff can make more informed decisions when creating digital content and better ensure their materials are accessible, usable, and compliant with university accessibility standards.
The WCAG principles state that digital content must be Perceivable, Operable, Understandable, and Robust (POUR), meaning users must be able to sense the information, interact with it, comprehend it, and access it reliably across different technologies. Together, these principles ensure content is accessible to people with diverse abilities and assistive tools.
Make sure users can recognize and understand your content using the senses available to them:
- Provide text alternatives (alt text) for images and other non‑text content.
- Provide transcripts for audio and video, and captions for all video content.
- Ensure content is logically structured so it can be read and navigated by a screen reader; this also helps when stylesheets don’t load.
- Use proper HTML markup—for example, correct tags for forms, headings, and data tables—so relationships between content are clear.
- Do not rely on color alone to explain or distinguish information.
- Use high‑contrast text colors that are easy to see against the background.
- Ensure all features work when users increase text size by 200%, and that content reflows into a single column at 400%.
- Avoid using images of text.
- Make your content responsive so it adapts to different devices, page orientations, and user‑selected font sizes.
- Ensure your content works well with assistive technologies, including marking important messages so screen readers recognize them.
Make sure users can find, navigate, and use your content, no matter how they access it:
- Make sure all functionality works for keyboard‑only users.
- Allow users to play, pause, and stop any moving, rotating, or updating content.
- Avoid blinking or flashing elements, and allow users to turn off animations.
- Provide a “skip to content” link or equivalent so users can bypass repeated navigation.
- Use clear, descriptive titles for pages and frames.
- Ensure users can move through the content in a logical and predictable order.
- Use descriptive link text so users understand where a link leads or what a downloadable item contains.
- Use meaningful headings and labels, and make sure accessible labels match or closely match the visible labels in the interface.
- Make it easy for keyboard users to see which element is currently focused (visible focus indicator).
- Avoid relying on mouse events or gesture-based interactions unless necessary, or provide alternative ways to use the interface.
- Allow users to change or disable shortcut keys to prevent accidental activation.
Make sure people can easily understand your content and how to use it:
- Clearly identify the language of the content, and indicate if the language changes within a page.
- Ensure features and interactions are consistent and predictable, so users know what to expect.
- Provide visible, clear, and meaningful labels for all form fields, and make sure they use proper markup so assistive technologies can read them correctly.
- Help users identify, understand, and correct errors in forms, such as by giving helpful error messages and clear instructions.
Make sure your content can be reliably interpreted by a wide range of technologies — including older, current, and future browsers and assistive tools:
- Use well‑structured HTML so browsers and assistive technologies can correctly interpret and process your content.
- Ensure your code provides assistive technologies with accurate information about each user interface component — including what it is, what state it’s in, and when that state changes.
- Mark up important status messages, alerts, and modal dialogs so users are notified of them and can interact with them using their assistive technology.
Accessibility Laws
Accessibility Laws that Apply to U.S. Universities
If the university is public (state or local government):
- ADA Title II requires all programs, services, and activities to be accessible, including:
- Websites
- PDFs and electronic documents
- Learning management systems (Canvas, Blackboard, etc.)
- Mobile apps and online forms
- In April 2024, the U.S. Department of Justice issued a final rule requiring WCAG 2.1 Level AA compliance for web content and mobile apps, with compliance deadlines beginning 2026–2027, depending on institution size. [ada.gov]
Official source:
New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments [ada.gov]
Most universities do receive federal funding (student financial aid, grants, research funding), which triggers Section 504.
- Section 504 prohibits disability discrimination in any program receiving federal funds
- Applies to:
- Course materials
- PDFs and digital handouts
- Online learning platforms
- Administrative systems
- Digital accessibility is required even if content is created by faculty or third‑party vendors [w3.org]
Official source:
Section 504 of the Rehabilitation Act of 1973 [w3.org]
Section 508 directly applies if the university:
- Is a federal institution, or
- Develops, maintains, or procures digital content for a federal agency, or
- Is contractually required to meet Section 508 standards
Section 508 requires:
- WCAG 2.0 Level AA–aligned accessibility
- Accessible PDFs, websites, software, and digital tools [section508.gov]
Official Section 508 site:
https://www.section508.gov [section508.gov]
WCAG itself is not a law, but it is the technical standard used to measure compliance with:
- ADA
- Section 504
- Section 508
For universities:
- WCAG 2.1 Level AA is the current expectation for web content and PDFs
- Used by DOJ, OCR, courts, and settlement agreements [w3.org]
WCAG official site:
https://www.w3.org/WAI/standards-guidelines/wcag/ [w3.org]
- Universities of Wisconsin
- University of Wisconsin – Milwaukee
- UWM Digital Accessibility Policy
- Digital Accessibility at UWM