Document Accessibility
You can contribute directly to accessibility efforts by learning several easy core skills that will generally improve the experience of people using assistive technology, people with invisible disabilities, AND the general population—in essence, improving both accessibility and usability.
It is also important to consider accessibility when designing web pages, documents and selecting multimedia. Consider accessibility when adopting new classroom technologies. Each individual is unique and incorporating accessible design increases the likelihood that your content will be accessible to all people, including those with disabilities.
Build in Accessibility From the Start
Follow these basic principles of accessibility to create accessible documents, web pages, and applications.
- Structure content with built-in heading styles (Heading 1, 2, 3). Using proper heading styles creates a navigable outline of your document, allowing assistive technology users to quickly understand the page layout and skip to the section they need.
- Use formatted bulleted or numbered lists. When you use the built-in list formatting tools, assistive technology announces that it's a list and how many items it contains.
- Add descriptive alt text to all meaningful images and charts. Alternative text (alt text) is a short description that's read aloud by screen readers, allowing users who can't see an image to understand its meaning and purpose.
- Use link text that describes the destination. Screen reader users often navigate by pulling up a list of all links on a page.
- Use properly structured tables with defined headers for data. Tables should only be used for displaying data, not for visual page layout. Defining column and row headers allows a screen reader to announce the context for each cell, so a user understands what the data represents.
- Use plain language and run a spell checker. Approximately 10% of the U.S. population has cognitive disabilities that can make complicated texts inaccessible, and screen readers can struggle with texts that have misspellings or are not clearly organized.
- Avoid using color alone to convey information. Relying only on color excludes people with color blindness. Instead, use labels, patterns, or icons to communicate the meaning.
- Ensure sufficient contrast between text and background. Use a tool like the TPGI Colour Contrast Analyser to check your color combinations.
- Include basic document properties (metadata). Adding a clear Title and Author in the document's file properties and setting the language (if needed) help all users identify, find, and organize their files more effectively.
Best Practices for Document Formats
Document formats may cause problems for students using mobile devices and assistive technology. Please review the following accessibility best practices for Google Docs, Microsoft Word, Google Slides, PowerPoint, and PDFs.
- Select familiar and simple fonts such as Arial, Calibri, or Times New Roman, and choose a legible font size (default settings are typically acceptable.)
- Avoid using all capital letters and excessive italics or underlines.
- Use a table of contents.
- Use the column tool instead of a table.
- If a table is the best way to present the material, add a header row.
- Avoid split and merged cells in tables. Screen readers cannot read them.
- Avoid using decorative text boxes. Screen readers cannot read the text that is inside.
- Make your Google document, presentation, and sheets more accessible
- Grackle Workspace Accessibility Add-On for Google
- Make your Word documents accessible
- Use the Microsoft Office Accessibility Checker
- Avoid animations and transitions.
- Use built-in slide layouts.
- Make sure slide content will be read in a logical order. The assistive technology will read the elements on your slide from the first object placed on the slide to the last.
- Make your Google document, presentation, and sheets more accessible
- Grackle Workspace Accessibility Add-On for Google
- Make your PowerPoint presentations accessible
Is PDF your best delivery format?
PDF files are not typically created in Acrobat. They are usually created in another program and then converted to PDF. For example, many documents are created in a word processing application, such as Microsoft Word, and then exported as PDF documents.
Optimally, document accessibility begins in the native document format. Dozens or probably hundreds of programs can create PDF files, but very few of them produce "tagged" PDF files.
Consider why you are using a PDF to distribute your information. Is it meant to take the place of information on a web page? Is it made available so users can print the information?
PDF is great for distributing documents that need to be printed. But no matter how tempting it might be, you should never use PDF for content that you expect users to read online.
Ask yourself the following questions when considering PDF:
- Is the information meant to be read online? If so, rendering that information as a web page is always preferable. Consider the following advantages of HTML:
- Customized to device
- Contains navigation and easy access to other site content
- Standard interface
- Easy to search
- Easy to share by link
- Linked to data repositories
- Is the PDF a form that can be created and managed online? Ask us about Google Forms! This form tool is easy to use and 100% accessible!
- Can the information be printed just as easily from a web page? Even when considering the print factor, you should keep in mind that web pages can also be printed, especially when using a good print style sheet.
- Will the document need to be remediated on a regular basis? If so, this could be time-consuming and costly.
Creating “Friendly” Documents for PDF
If a PDF is necessary, create the document using accessible practices in your chosen software, then export or save it as a PDF.
Make sure that the elements you choose are done so purposefully. Can the reader understand the information without the use of those elements? If the answer is "yes," then you are probably better off not using them.
The core steps needed for accessibility are the same regardless of whether your document is in HTML, Microsoft Word, Adobe PDF, or another document format:
- Use headings
- Use lists
- Add alternate text to images
- Identify document title and language (metadata)
- Use tables wisely and simply
- Run built-in accessibility checkers
- Understand how to export from one format to another
Other characteristics of a fully accessible PDF include logical reading order and structure, valid Unicode assignments for all characters, and management of all interactive features to ensure their maximum usability. Complete these steps in software such as Prep or Adobe Acrobat.
Creating Accessible PDF Documents In Adobe Acrobat
FAQ
What is Tagging?
Tagging is just one of the many things that must be done in native document applications to support accessibility. Tags express the structure of the document, including the logical text-flow or reading order, and the presence of significant elements such as figures, lists, tables, and so on. Even seemingly small errors in document structure can easily render a file completely incomprehensible by readers with disabilities. In fact, you might consider using your computer with the screen turned off to get some idea of how important logical text-flow is to anyone who needs a screen-reader!
If my document was designed for print, do I need to change it for the web?
It depends. If the PDF represents a document that is also used in hardcopy form (e.g., a printed brochure), it may not be suitable for online reading. For example, it may contain multi-page spreads that are challenging to navigate on small screens, or text that is upside down or irrelevant (e.g., a panel for postal mail.)
Creating a separate, simpler version for downloading and reading offline will remove elements that create accessibility barriers. Eliminating unnecessary elements can make your job of remediation easier and less costly.
Avoid photocopying or scanning to PDF. When a printed page is scanned to PDF, it creates a file that contains no actual, recognizable text, but instead just an image of text. Text-to-speech tools will have difficulty interpreting the page.
Scans that are crooked, faded, sideways, or covered with handwritten notations are even more difficult to interpret. If you can locate higher quality digital originals, your PDF documents stand a much better chance of being accessible.
TIP: If you can't select or search for any text in a document, it is probably an image-only PDF, and you will need to perform text recognition.
Text Recognition
Text Recognition is often referred to by the more technical term OCR (Optical Character Recognition). Both terms refer to the same process of converting images of text to readable text. Some modern scanners can perform OCR, but usually the text will need to be remediated.
Text Recognition Resources
The following tools can perform OCR. Results depend on the quality of the scanned document.
Alternative Text (Alt text) is a textual alternative (non-visual) way to describe the meaning of an image. Please provide a brief one or two sentence description of all images.
Alternative text provides several services:
- Screen readers cannot analyze an image and determine what the image represents. Alternative text conveys the meaning of the image to the user.
- In cases where an image is not loaded into a web page, the alternate text is displayed instead. Some users choose not to display any images in the web browser and prefer to read the alternative text.
- Search engines use alternative text to assist in search results.
Best Practices
- Ensure that alternative text is descriptive. The file name alone is not sufficient.
- The subject matter expert should assist in determining the educational purpose of all images.
- The accepted practice for images varies depending on the use of the image. If an image is included in Canvas for educational purposes, a description of the image is required.
- Charts and graphs require a detailed explanation so that all users can gain knowledge. Another example would be a photo of a painting for an Art History course. In addition, longer text descriptions should be provided as a caption for these images or included in the text.
- If an image does not meaningfully contribute to the document's content, then it can be more generally described or marked as a decorative image.
- Avoid using "image of" or "picture of" within the alternate text. A screen reader will automatically state "graphic" before reading the alt text.
- For images that also act as links, avoid using "click here" or "link to" in the alternative text. The screen reader will automatically state "link" before reading the description.
Using Generative AI to Compose Alternative Text
Generative AI tools have improved their ability to recognize and describe images. In addition to tools like ChatGPT and Gemini, word processing and design programs may include automatic alt text generators that can give you a starting point.
Best Practices for AI-Generated Alt Text
- Default to the Reasoning (pro) model for whatever AI tool you're using.
- For best results, write a specific prompt and request more than one output to choose from:
Using the provided photo, create three simple alt text descriptions.
Using the provided chart, create three simple alt text descriptions to summarize the results. - Improve results by adding extra descriptors, such as "write 100 words or less" or "include details of composition, color, and artistic techniques for this painting"
- Choose alt-text based on the best matches for the context and purpose of the image.
Resources for Alt Text
Color is an important asset in document design, enhancing its aesthetic appeal, usability, and accessibility. However, some people have difficulty perceiving color. In addition, people using text-only, limited-color, or monochrome displays and browsers cannot access information presented only in color.
Best Practices
- Avoid communicating information with color alone.
- Use high levels of color contrast.
- The most accessible colors against a white background include:
- Black (or white text on a black background)
- Burnt Orange
- Very Dark Gray
- Medium to dark blue for links/hyperlinks
- Users with partial vision benefit from text attributes such as size, color, bold, italics, and underlining to draw the attention of the content.
- Use headings to delineate the hierarchy and importance of the text. Avoid using formatting styles such as bold, italics, and underline alone as ways to delineate structure.
Forms are commonly used to provide interaction on websites and in web applications. Accessible forms are easy to understand, complete, and submit. Instructions, cues, required form fields, and field formatting requirements must be clearly identified to users. Ensure that the reading and navigation order is logical and intuitive.
Best Practices
- Ensure forms are logical and easy to use
- Ensure forms are keyboard accessible
- Provide instructions for the form (i.e., “* = required form field”).
PDF or Webform?
PDF forms must be remediated to be accessible. Because of the interactivity of form fields, they usually require that additional tags be added in Acrobat Pro. They can not be made fully accessible in authoring tools (such as Microsoft Office) at this time.
If you can use a webform instead (Qualtrics, Google Forms, etc), that’s always preferable. Another option is to make the static text portion accessible and then use Docusign to add accessible form fields.
Resources for Accessible Forms
Headings provide structure to your documents. When these document structures are in place, word processing documents (such as Word or Google Docs), web documents (such as HTML pages), and other formats (such as PDF) are all more usable and navigable by assistive technology tools.
Best Practice
- Do not use font size or formatting to create headings visually. Instead, apply the built-in heading styles that your software provides.
- Simpe documents should include only one Heading 1.
- Use proper formatting, styles, and headings in a logical order. Avoid skipping headings or using headings inconsistently.
- Headings will also create an outline or can assist in creating a table of contents.
Links should be descriptive of the content they're linking to, such as 'Class Schedule' rather than 'schedule.html' or 'click here' because many screen reader users use links to navigate the page, and providing links without text can be a barrier for these users.
Best Practices
Follow these guidelines when adding links to web pages and documents:
- Link text should describe the destination.
- Example: Learn more about our campuses and locations at Miami.
- Avoid duplicate links on pages. These links may have different descriptive text but take users to the same place.
- Avoid using generic descriptions such as “click here,” "online," "learn more," etc. These labels do not describe the function of a link. Users will NOT hear the link in the context of the sentence. Usually, the links are read separately.
- Don't underline text unless it is a link/hyperlink.
Examples of Descriptive Link Text
Poor Usage Examples
- Neil Danielson, in his paper "Multimodal liquid chromatography of small molecules," http://pubs.rsc.org/en/Content/ArticleLanding/2013/AY/c3ay40302e#!divAbstract, says multimodal chromatography is a family of...
- Click here to access this week’s reading assignment.
- Read more about biochemistry research at Miami online.
Good Usage Examples
- Neil Danielson, in his paper "Multimodal liquid chromatography of small molecules," says multimodal chromatography is a family of...
- Access this week's reading assignment.
- Read more about biochemistry research at Miami.
Ordered and unordered lists group together related items. If your content includes lists, make sure they are made using styles or markup language.
Best Practices
- Unordered lists are for content having no order of sequence or importance.
- Ordered lists suggest sequence, order, or ranking. List items are typically pretended with a number, letter, Roman numeral, etc.
- List structure should be used wherever a logical list is present and nowhere else. Don't merely create something that looks like a list by starting each paragraph with a bullet character.
- Don't apply list structure to elements that do not logically form a list.
Tables should be simple and structured appropriately. Tables should be used to organize and display data, not for content/page layout.
Best Practices
- Avoid merging or splitting table cells, as doing so will cause screen readers to read the table columns and rows inaccurately. Special remediation is needed to allow the content of merged cells to be read accurately by a screen reader.
- Column and row headers provide a description of the table structure for sighted and screen reader users.
- For HTML, best practices include:
- A caption tag <caption> should be at the top of the table. The caption is visible to everyone and should describe the purpose of the table.
- Scope attributes (<th scope="col"> or <th scope="row">) in headers organize and further define table data by row/column for screen reader users.
- Table headers <th> should never be empty, but table data <td> can be empty.
| Column Heading | Column Heading | Column Heading | |
|---|---|---|---|
| Row Heading | Table data | Table data | Table data |
| Row Heading | Table data | Table data | Table data |
| Row Heading | Table data | Table data | Table data |
| Table data | Table data | Table data |