Guide

How to export an accessible PDF from Google Docs

Google Docs exports tagged PDFs and has done since 2022. What comes out right, the three things it cannot do, and what to fix afterwards.

About 8 minutes · quick

Export the right way

File → Download → PDF Document (.pdf).

That path emits a tagged PDF. There are no options to set, which is both the good news and the bad news — nothing to get wrong, and nothing to tune.

Not File → Print → Save as PDF. The browser print path produces an untagged file, exactly as it does from Word. The output looks identical and has no structure at all.

What comes out right

• Headings. Heading 1…Heading 6 from the styles menu become H1…H6, at the right levels.
• Lists. The list buttons produce proper L / LI / LBody.
• Links. Real /Link structure elements, not bare annotations — better than several commercial tools manage.
• Tables. Table / TR / TD, with a header row if you have set one.
• Alt text. Right-click an image → Alt text carries through to /Alt.
• Document language. The document’s language setting becomes /Lang.

For a report, a policy document or a letter, that is most of the way there.

The three gaps

Language of parts

Google Docs has one language setting for the whole document. There is no way to mark a passage as being in a different language, so nothing exports per-run /Lang.

For a monolingual document this does not matter. For a bilingual one it matters a great deal: a Hebrew document with an English abstract will read the abstract with a Hebrew voice, or the reverse. WCAG 3.1.2 Language of Parts is a Level AA criterion and this is the failure mode — see TG-RTL-002.

The fix is after export, in Acrobat’s Tags panel: select the element, Properties → Tag → Language. Or in Taggart, which detects the runs by script and proposes the language for each.

The display-title flag

The document’s name becomes the PDF’s /Title, which is right. What Docs cannot set is /DisplayDocTitle, so a reader ignores that title and announces the filename anyway.

Two switches, both required — see the title guide. This one has to be set after export, in Acrobat or with a two-line script.

Name the document properly before you export, though. “Untitled document” and “Copy of Annual Report v3 FINAL” both become the title.

Complex tables

You get a header row and nothing else — no /Scope on header cells, no Headers/ID references. Adequate for a simple grid, insufficient for anything with merged cells or two header rows. See the table guide.

Before you export

The same discipline as any other authoring tool, and it is what decides the outcome:

Real heading styles, in order, no skipped levels. The Format → Paragraph styles menu, not bold 16pt text.

Real lists, from the list buttons.

A header row on every data table: select the row → Format → Table → Pin header row. Google’s terminology differs from Word’s; “pin header row” is what becomes THead.

Alt text on every image: right-click → Alt text, or Ctrl+Alt+Y. Google Docs has no “mark as decorative” option, which is a real limitation: a decorative image has to be dealt with after export, by changing its Figure to an artifact.

Name the document. It becomes the title.

Set the language: File → Language.

Google’s own accessibility checker

Tools → Accessibility → Accessibility settings turns on screen-reader support and braille support, which affects editing rather than export.

There is no equivalent of Word’s Check Accessibility — Docs will not tell you that an image lacks alt text or that a heading level is skipped. That absence is worth planning around: check the exported PDF rather than expecting the editor to warn you.

After you export

Three things, in about five minutes:

1. The display-title flag. Acrobat: File → Properties → Initial View → Window Options → Show: Document Title.
2. Language of parts, if the document is bilingual.
3. Decorative images — retype any Figure that carries no information to an artifact.

Then check it: two checkers and a paste test.

Related failure conditions

• 01-005 Content is neither marked as Artifact nor tagged as real content Every text-showing, image-painting and path-painting operator on a page must sit either inside a marked-content sequence that maps to the structure tree, or inside an artifact sequence. Content that is in neither is orphaned.
• 06-001 Document does not contain an XMP metadata stream The catalog has no /Metadata entry pointing at an XMP packet. PDF/UA-1 requires one — it is where the conformance claim and the document title live.
• 14-003 Numbered heading levels in descending sequence are skipped The heading hierarchy jumps a level going down — H1 straight to H3. Going back up any number of levels is fine; going down must be one level at a time.
• 11-001 Natural language for text in page content cannot be determined No /Lang is in effect for some text: neither on the catalog, nor on an enclosing structure element, nor on a marked-content sequence.
• 15-003 A TH cell does not contain a Scope attribute Header cells must declare whether they head a row, a column, or both, unless the table instead uses explicit /Headers ID references on every data cell.

Last updated 2026-09-10 .