Overview
The University of Maryland (University) is committed to ensuring that people with disabilities have equitable access to the University’s programs, services, activities, information, and opportunities. This commitment includes the electronic documents used in teaching, research, service, and administration, such as Word documents, PDFs, presentations, and spreadsheets. Accessible documents enable students, employees, visitors, and the broader public, including individuals who use assistive technologies, to access information and participate fully in all areas of the University’s mission.
These guidelines are intended to help University administrative, academic, and programmatic units incorporate accessibility into document creation, procurement, distribution, and maintenance.
The University of Maryland Electronic Information, Communication, and Technology (EICT) Accessibility Policy establishes accessibility requirements for University web-based information, including electronic documents. These guidelines support implementation of the policy’s applicable requirements, including conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Levels A and AA, subject to the policy’s provisions and exceptions.
An accessible document allows people with disabilities, including those who use assistive technologies such as screen readers, screen magnifiers, and text-to-speech tools, to access the same information with substantially equivalent ease of use. Accessibility is most effectively incorporated from the beginning of document creation and maintained as the document is updated and shared.
Top
Document formats and accessibility
Choosing an appropriate format is an important first step in creating accessible documents. Consider how people will access, navigate, and use the content, as well as whether they need to edit, download, or print it. Each format below can support accessibility when content is properly structured and reviewed.
HTML
HTML provides the structure for web pages and supports accessibility through features such as headings, lists, descriptive links, and text alternatives for images. It can also be used to create offline, stand-alone documents.
For content intended primarily to be read online, HTML is often preferable to PDF because it can adapt more readily to different screen sizes and user preferences. Accessible HTML requires meaningful structure, logical reading order, appropriate alternative text, and other accessibility practices. Longer documents can also work well in HTML when organized with clear headings and navigation. When a fixed print layout is necessary, an accessible PDF may be appropriate.
Microsoft Word
When content needs to be drafted, edited, or shared as a downloadable document, Microsoft Word offers tools for creating accessible content. When creating documents with accessibility in mind—ensuring correct use of heading levels, alt-text descriptions and correctly formatted lists and tables—Microsoft Word is generally accessible. A well-structured Word document also provides a stronger foundation for conversion to other formats, although the converted file must be checked separately.
The built-in Accessibility Checker helps identify potential barriers, but it does not detect every issue. Combine it with a manual review of the document’s structure and content. Follow these practices when creating accessible Word documents:
- Use properly formatted headings in a logical hierarchy.
- Create tables using Word’s table creation tool and identify header rows.
- Don’t use tables for layout.
- Include meaningful alt text for informative images and mark purely decorative images as decorative.
- Create lists using Word’s built-in bulleted or numbered list tools.
- Use the Microsoft Accessibility Checker to review and fix potential accessibility issues.
Google Docs
For collaborative document creation, Google Docs is another option that supports assistive technologies and provides accessibility settings. As with Word, accessibility depends on using headings, lists, tables, links, and alternative text appropriately.
The Grackle Workspace extension can help identify and address accessibility issues in Google Docs. Review its findings alongside a manual check of the document. When exporting to another format, check the exported file to confirm that its accessibility features have been preserved.
EPUB 3
When readers need a portable publication with flexible reading options, EPUB may be useful. EPUB is an electronic file that can be read on a variety of devices, such as mobile phones, tablets, and eReaders. It is widely used by the publishing industry for textbooks and other larger files, but EPUB can also be offered as an alternative format for smaller documents.
Reflowable EPUB content can adapt to readers’ screen sizes and text preferences. Accessibility depends on both the publication’s design and the reading application. EPUB Accessibility 1.1 provides accessibility requirements for EPUB publications, including their relationship to WCAG.
PDF
When preserving a fixed visual layout is necessary, PDF (Portable Document Format) may be appropriate. PDFs maintain a consistent appearance across devices and in print, but accessibility requires more than visual consistency.
An accessible PDF needs searchable text, appropriate document tags, logical reading order, meaningful alternative text, and other accessibility features. Tags identify elements such as headings, paragraphs, lists, and tables so that assistive technologies can interpret the document’s structure. Tagging alone does not guarantee accessibility.
Remediating PDFs for accessibility can be a complex process. Documents made in other formats (Word, PowerPoint, etc.) may not retain their accessibility features once converted to PDF. Whenever possible, correct accessibility issues in the original document before exporting, and then review the resulting PDF.
Before sharing or posting a PDF:
- Run an accessibility check in Adobe Acrobat Pro and manually review items that require human judgment, including reading order and the quality of alternative text.
- Ensure that the PDF is not an image of text. For scanned documents, use optical character recognition (OCR), verify the recognized text, and add the necessary document structure.
- Make certain the PDF is properly tagged and that the reading order is logical.
- Ensure that fillable form fields have accessible labels and a logical tab order, and test the form using a keyboard.
Use tools such as Adobe Acrobat Pro and Equidox to support PDF accessibility review and remediation. For instructions on remediating documents in Equidox, consult the Equidox user guide. After remediation, review the final PDF to confirm that the content and accessibility features work as intended.
Top
Basic steps for document accessibility
After choosing a document format, build accessibility into the content from the start. The following practices apply across formats, although the tools used to implement them may differ. Begin with the 6 Essential Steps for Digital Accessibility:
- Use headings. Apply built-in heading styles to organize content into a logical hierarchy. Avoid skipping levels when moving to a subsection—for example, use Heading 2 under Heading 1, followed by Heading 3 for a subsection. Use built-in list tools to create bulleted and numbered lists.
- Use descriptive links. Write link text that identifies the destination or purpose, so readers can understand it without relying on surrounding text. Avoid using text such as “click here” or “read more” on its own.
- Ensure appropriate color and contrast. Use sufficient color contrast between text and its background, and avoid using color alone to convey meaning. Add labels to charts and graphs. Check color combinations with the Contrast Checker.
- Add alternative text to images. Provide meaningful alt text that communicates the purpose or information conveyed by pictures, illustrations, and charts. Mark purely decorative images as decorative when the application supports it. For complex visuals, include a longer explanation in the surrounding text.
- Use tables correctly. Identify column and/or row headers and maintain a logical reading order. Use tables for data rather than page layout.
- Provide alternatives for media linked to or embedded in documents. Add captions to your videos, review and correct automated captions, and provide a transcript for audio files. Ensure that essential visual information in videos is also available through audio description or an equivalent accessible alternative.
In addition to these six steps, attend to the document’s formatting, properties, and final delivery:
- Use paragraph and line-spacing settings instead of repeated blank paragraphs, spaces, or tabs to position content. In spreadsheets, avoid inserting blank rows or columns solely for visual spacing within a data table, because they can make navigation more difficult.
- Set the document’s primary language using the application’s language settings. Where supported, identify passages written in another language.
- Give the document a descriptive title and filename. Add the title to the document properties when the format supports it.
- Preserve accessibility when converting files. Follow the application’s export guidance, such as Microsoft’s instructions for creating accessible PDFs, and check the exported file before sharing it.
- Include a brief accessibility statement near the beginning of the document with contact information for requesting assistance or an alternative format. This statement supports access but does not replace the need to make the document accessible.
Top
Best practices for creating accessible documents, presentations, and spreadsheets
The basic steps above provide a foundation. The following tips explain how to apply them in commonly used applications and address issues specific to each format. Use accessibility checkers alongside manual review, since automated tools cannot identify every barrier.
Google Docs and Microsoft Word
Begin with a clearly structured document, then review its accessibility before sharing or converting it.
- Follow the Six Essential Steps when creating a document. Use heading styles, properly formatted lists, descriptive links, and meaningful alt text throughout.
- For Google Docs, follow Google’s accessibility guidance when formatting and organizing content. Use Grackle Workspace to identify potential accessibility issues and guide corrections.
- For Word, use the built-in Accessibility Checker and review Microsoft’s guidance on making Word documents accessible for instructions on headings, tables, images, and other document elements.
- Review the document manually to confirm that headings are organized logically, links make sense, and image descriptions convey the intended information. Check any color combinations that the automated checker does not evaluate.
Google slides and PowerPoint presentations
Presentations require the same attention to structure and content, with additional care for slide layouts and reading order.
- Follow the Six Essential Steps when creating slides.
- Keep slides uncluttered. Use readable text sizes and sufficient white space, and divide dense content across multiple slides.
- Give every slide a unique and descriptive title.
- Use built-in slide layouts and content placeholders whenever possible. If you add text boxes or other objects, check their position in the reading order.
- Ensure that assistive technologies encounter slide elements in a meaningful sequence. In PowerPoint, follow Microsoft’s presentation accessibility guidance to review reading order and address accessibility issues. Outline View can help review titles and some text, but it does not show all slide content or verify reading order.
- Keep essential information on the slides or in an accessible companion document. Speaker notes may not be included when a presentation is exported to PDF or another format.
- Run PowerPoint’s Accessibility Checker or use Grackle Workspace for Google Slides, and address the issues identified.
- For Google Slides, consider sharing an additional link to the HTML view of the presentation. This displays the slides on a single scrollable page, which may be easier for some screen reader users to navigate.
PDFs
When distributing a document or presentation as a PDF, check the exported file separately. An accessible source file provides a strong starting point, but conversion may not preserve every accessibility feature.
- Start with an accessible document (e.g., Word or PowerPoint, Google Docs or Slides) before converting to PDF. Use an export option that preserves document structure and tags, following Microsoft’s guidance for creating accessible PDFs or Grackle’s guidance for exporting to PDF.
- Review the PDF’s tags, reading order, headings, links, alternative text, and document language. Use Adobe Acrobat Pro’s accessibility features or Equidox to support remediation. The Equidox user guide provides instructions for working with documents in Equidox.
- Scanned images of text are not accessible on their own. If a scanned document is necessary, use a clear, complete scan without clipped text or binding shadows. Apply optical character recognition (OCR), verify the resulting text, and add appropriate tags and reading order. A clear scan alone does not make a PDF accessible.
- For fillable PDFs, provide accessible field labels and a logical tab order. Test that users can navigate and complete the form with a keyboard.
- After making corrections, run another accessibility check and manually review the final file before sharing it.
Excel and Google Sheets
Spreadsheets require particular attention to table structure and navigation so that readers can understand how the data is organized.
- Whenever possible, keep the layout of the table simple. Use clear headers, and avoid blank rows or columns within a data table.
- Each sheet in the file must have a unique, meaningful name based on the information it contains.
- Use only one header row when possible. Make each column heading descriptive, and identify row headings where needed.
- Do not merge cells within data tables, because merged cells can make navigation and interpretation more difficult.
- Ensure your cells are formatted to properly represent your data, including text, numbers, dates, and percentages.
- Use descriptive names for important data ranges where helpful. Named ranges can make specific information easier to locate and formulas easier to understand.
- Add meaningful alt text to informative images, charts, and graphs. For complex visuals, provide a brief text alternative and a fuller explanation or accessible data table in the spreadsheet.
- Use labels or other text cues alongside color to explain trends, categories, or status.
- For Excel, follow Microsoft’s accessibility best practices for spreadsheets and run the Accessibility Checker. For Google Sheets, apply Google’s accessibility guidance and review the file with Grackle Workspace. In both applications, manually check that the data and its organization are understandable.
Top
Document conversion tools
Document conversion tools change files into alternative formats, such as audio, HTML, EPUB, and digital Braille, to support different access needs and reading preferences. The following tools support document conversion:
- Ally in ELMS-Canvas helps instructors identify and fix accessibility issues in course documents. Students and instructors can also download course documents in alternative formats, including HTML, audio, EPUB, and electronic Braille, depending on the original file type.
- SensusAccess Document Conversion converts documents into formats such as Word, HTML, audio, EPUB, and digital Braille. It is available to UMD students, instructors, and staff with a valid umd.edu email address.
- Mathpix converts PDFs and images containing text, equations, tables, and handwritten notes into editable formats such as Word, HTML, and LaTeX. It can be especially useful for math and science documents. Review converted handwriting, equations, and symbols carefully for accuracy.
Conversion quality depends on the original document. Clear text, properly formatted headings, and a logical reading order improve results. Poor scans and complex content, such as infographics, equations, and tables, may not convert accurately. After conversion, use the evaluation process below to confirm that the content remains complete, accurate, and accessible.
Top
Accessibility evaluation
Evaluate all documents and forms for accessibility before sharing or publishing them. Combine automated accessibility checks with manual review and, where appropriate, testing with assistive technologies such as screen readers. Automated tools can identify many common issues, but they cannot confirm that a document is fully accessible.
Begin with the checker available for the document’s format, such as the Microsoft Office Accessibility Checker, Adobe Acrobat Pro’s accessibility tools, or Grackle Workspace for Google. Address identified issues and review any items flagged for manual inspection.
Next, review the document’s content, structure, and visual presentation. Automated checks may not fully assess readability, color contrast, the accuracy of alternative text, or whether the reading order makes sense. Before sharing the document, confirm that:
- Text is readable. Font style and size support comfortable reading, and content remains usable when enlarged.
- Color is used appropriately. Color is not the only means of communicating meaning; labels or other text cues provide the same information.
- Text and background colors have sufficient contrast. Use the Contrast Checker to evaluate combinations that require manual review.
- Alternative text is meaningful. Descriptions communicate the purpose or information conveyed by images. Decorative images are marked appropriately, and complex visuals have fuller explanations where needed.
- Headings provide structure. Heading styles or tags identify sections and follow a logical hierarchy appropriate to the document.
- Lists are properly formatted. Bulleted and numbered lists use the application’s list tools.
- Hyperlink text is meaningful. Readers can understand each link’s purpose or destination.
- Data tables are accessible. Tables have a simple structure, clearly identified headers, and a logical reading order.
- Content follows a logical reading order. Text, images, tables, and other elements are encountered in a sequence that preserves meaning.
- Text boxes and visual objects are accessible. In Word, place images in line with text where practical. If floating objects or text boxes are used, verify that their content is available to assistive technologies and appears in the correct reading order.
- Document properties are set. The document has a descriptive title and the correct primary language.
- Forms are usable. Fields have meaningful accessible labels, instructions are clear, and users can navigate and complete the form with a keyboard.
For forms and documents with complex layouts or interactive elements, use screen reader testing to help verify that content, field labels, and instructions are announced meaningfully. Check the final version in the format readers will receive, and repeat relevant checks after making corrections or converting the file.
Top
Support
Top
Revision history
Version 1 - Published on 9/282026