Accessible documents use real structure, clear language, meaningful alternatives for visual content, and readable formatting. This guidance covers document authoring tools and PDF editors, including Microsoft Word, Google Docs, Apple Pages, Adobe Acrobat, Foxit PDF Editor, and Canva.
Overview
Digital documents include word-processing files, designed documents, and PDFs created or edited in tools such as Microsoft Word, Google Docs, Apple Pages, Adobe Acrobat, Foxit PDF Editor, and Canva. They may be shared by email, posted on websites, uploaded to eLC, or attached to course materials.
Accessibility works best when it is built into the source document. Using the authoring tool’s built-in structure and accessibility features creates a more reliable file and reduces remediation when the document is exported or converted.
Presentation software, including Microsoft PowerPoint and Google Slides, is covered on the Slides page. Spreadsheet and data guidance is available on the Data Visualizations page.
Why document accessibility matters
Common document barriers can prevent people from finding, understanding, or interacting with information. Accessible authoring removes barriers such as:
Accessible documents also support the University of Georgia’s responsibilities under ADA Title II and WCAG 2.1 AA. Building accessibility into the original file saves time and produces a more consistent experience when content is shared, published, or archived.
Core principles for every document
The tools differ by format, but these practices apply across documents, presentations, spreadsheets, and PDFs.
Describe meaningful images
Provide alternative text for images, charts, icons, SmartArt, and other informative visuals. Mark visuals as decorative when they add no information. See the Images technique.
Write meaningful link text
Use link text that describes its destination or action. Avoid “click here,” “read more,” and raw web addresses in body content. See the Links and buttons technique.
Use sufficient contrast and more than color
Body text needs at least 4.5:1 contrast against its background, and large text needs 3:1. Pair color with text, a symbol, or another visible cue. See the Color contrast and Visual characteristics techniques.
Check the document before sharing
Run the built-in accessibility checker, then manually review the heading outline, reading order, links, tables, and image descriptions. Automated checkers identify common problems but cannot confirm the full experience.
Document tools and formats
Start with the tool used to create or edit the document. Dedicated DAS guidance is linked where it is currently available, and additional guidance is being developed.
Create and edit documents
Microsoft Word
Use built-in heading styles, native lists, meaningful image descriptions, simple tables, and accessible export settings.
Creating Accessible Word DocumentsMicrosoft Word Field Guide
Google Docs
Apply paragraph styles, use native lists and tables, add alternative text, and review the document before sharing or exporting it.
Apple Pages
Use paragraph styles, native lists, image descriptions, and simple tables, then review the exported document or PDF.
Canva
Use clear hierarchy, readable typography, sufficient contrast, meaningful links, and text alternatives, then review the exported file before sharing it.
Edit and remediate PDFs
Adobe Acrobat PDFs
Review tags, reading order, document properties, alternative text, links, tables, forms, and accessibility checker results.
Foxit PDFs
Use Foxit PDF Editor’s accessibility features to review document structure, reading order, alternative text, links, and form field labels.
Getting help
Digital Accessibility Services supports UGA colleges, schools, and administrative units with consultations, training, and practical guidance. Email [email protected] for assistance.