How Do I Export an Accessible PDF from Google Docs?

Google Docs is the go-to writing tool for many faculty members. It is free, collaborative, and lives in the browser. So when it is time to share a syllabus, assignment, or reading as a PDF, the natural instinct is to go to File → Download → PDF Document (.pdf).

That works — but the PDF you get may not be accessible. Google Docs preserves some document structure in its PDF export, including headings, lists, and alt text on images. However, compared to Microsoft Word, its PDF output is significantly weaker when it comes to accessibility tagging. Tables often lack proper header tags, heading hierarchy can be inconsistent, and reading order issues are more common.

If you are working toward WCAG 2.1 compliance or PDF/UA conformance, you need to understand what Google Docs can and cannot do — and when to reach for a different tool.

The Quick Answer

1. Structure your document properly in Google Docs (headings, alt text, lists).
2. Go to File → Download → PDF Document (.pdf).
3. Check the resulting PDF for accessibility issues.

That is the simplest path. The rest of this guide covers how to do each step well, what the limitations are, and what to do when Google Docs is not enough.

Step by Step: Preparing Your Google Doc

Before you export, the quality of your PDF depends entirely on how you structured the original document. Here is what to do.

Use Heading Styles

Select your headings and apply the built-in heading styles from the toolbar dropdown (where it says "Normal text"). Use Heading 1 for the document title, Heading 2 for major sections, and Heading 3 for subsections. Do not just make text bold and increase the font size — screen readers cannot detect that as a heading.

Add Alt Text to Images

Right-click any image, select Alt text, and write a concise description of what the image conveys. If the image is purely decorative, you can leave the description empty, though Google Docs does not have a dedicated "mark as decorative" option the way Word does.

Use Built-In Lists

Use the toolbar buttons for bulleted and numbered lists rather than typing dashes or numbers manually. Built-in lists are tagged as proper list structures in the exported PDF.

Use Simple Tables

If you must include a table, keep it simple — avoid merged cells, nested tables, or tables used purely for layout. Google Docs tables export with basic table tags, but header rows are often not properly tagged, which is a significant accessibility gap.

Add Meaningful Link Text

Instead of pasting a raw URL, highlight descriptive text and insert the link with Ctrl+K (or Cmd+K on Mac). "Read the accessibility policy" is far more useful to a screen reader user than "https://example.edu/docs/policy-2026-v3-final.pdf".

Export the PDF

Once your document is structured, go to File → Download → PDF Document (.pdf). Google Docs will generate a tagged PDF with the structure you created.

Where Google Docs Falls Short

Here is where things get frustrating. Even if you do everything right in Google Docs, the exported PDF will have limitations that do not exist when exporting from Microsoft Word.

Table header tagging. Google Docs does not reliably tag table header rows as <TH> elements. Screen readers may read table data without any context for what each column or row represents. Word handles this correctly when you designate a header row.

Heading hierarchy. Google Docs sometimes produces inconsistent heading levels in the PDF tag tree, especially in longer documents or when heading styles have been customised. Word's PDF export is more predictable.

No accessibility export options. When you save a PDF from Microsoft Word, you can check a box for "Document structure tags for accessibility." Google Docs has no equivalent — you get whatever it generates, with no control over tagging behaviour.

No built-in accessibility checker. Word has a built-in Accessibility Checker that flags issues before you export. Google Docs has no equivalent. You are flying blind until you check the exported PDF in a separate tool.

Reading order. For documents with multiple columns, text boxes, or complex layouts, Google Docs PDF exports can produce reading order issues that make the document confusing for screen reader users.

For a detailed walkthrough of the Word method, see our guide on exporting accessible PDFs from Microsoft Word.

When to Use Word Instead

Use Microsoft Word when your document includes any of the following:

• Tables with header rows — Word tags these correctly; Google Docs often does not.
• Complex layouts — multiple columns, sidebars, or text-heavy formatting.
• Anything requiring PDF/UA compliance — Google Docs cannot produce a PDF/UA-conformant file on its own.
• Documents you have already been asked to remediate — starting from Word gives you a cleaner foundation.

If your department uses Google Workspace exclusively, there is a practical workaround.

The Google Docs to Word to PDF Workaround

This two-step export path gives you the best of both tools:

1. In Google Docs, go to File → Download → Microsoft Word (.docx).
2. Open the .docx file in Microsoft Word.
3. Review and fix any formatting that shifted during conversion.
4. Run Word's Accessibility Checker (Review → Check Accessibility).
5. Go to File → Save As → PDF, and check the box for "Document structure tags for accessibility."

This produces a significantly better-tagged PDF than exporting directly from Google Docs. It adds an extra step, but for important documents — course syllabi, department policies, anything that will be posted publicly — it is worth the effort.

Checking the Result

Regardless of how you exported, always verify the accessibility of your PDF. You can use:

• Adobe Acrobat Pro — run the built-in Accessibility Check (Tools → Accessibility → Full Check).
• PAC (PDF Accessibility Checker) — a free tool that checks for PDF/UA compliance.
• Aelira's automated scanner — upload your PDF and get a detailed accessibility report in seconds.

For a full walkthrough of the verification process, see our guide on how to check PDF accessibility.

If you want to understand the full picture of what makes a PDF accessible — from tags and reading order to colour contrast and language settings — our complete guide to making PDFs accessible covers everything.

The Bottom Line

Google Docs is a fine tool for writing. It is not a great tool for producing accessible PDFs. If your documents are simple — mostly text with headings, a few images with alt text, and basic lists — exporting directly from Google Docs is acceptable. For anything more complex, export to .docx first and use Word for the final PDF conversion.

And if you are dealing with a backlog of PDFs that were already exported from Google Docs without proper structure, you do not have to fix them all by hand. Aelira can scan and remediate them automatically. Learn more about our automated PDF remediation, or try it free.