Google Docs to accessible PDF: what the export tags now, and what you still have to check

For most of its life, Google Docs was the authoring tool whose PDFs were reliably untagged. University accessibility offices wrote whole pages about it, and the standard workaround was to download a .docx and export from Word instead. That advice is now out of date for most documents. This guide records what Google changed, how to prepare a Doc so the export has something to tag, and the checks that still matter afterwards.

What changed, and when

On December 6, 2024, the Google Workspace Updates blog announced that Google was "adding more structural and accessibility tagging in PDFs exported from Google Docs", specifically improved tagging for paragraphs, headings, hyperlinks, image alt text, and lists. The rollout to Rapid Release and Scheduled Release domains was expected to complete by mid-January 2025, and the feature was made available to all Google Workspace customers, Workspace Individual subscribers, and personal Google accounts. In March 2025 a further update added accessibility tags for tables, equations, and checkboxes in exported PDFs.

In practice this means File > Download > PDF Document (.pdf) now produces a file with a structure tree, where previously it produced a visually identical file with none. Google's announcements do not enumerate every tag or attribute the export writes, and they do not claim conformance with any standard, so treat the result as a well-tagged starting point rather than a finished accessible document.

Prepare the document before you export

1. Use real heading styles. Text made large and bold is exported as a paragraph. Apply Heading 1, Heading 2, and so on from the styles menu, in a sensible order, and use the document outline pane to confirm the hierarchy reads correctly on its own.
2. Add alt text to every meaningful image. Select the image, open its options, and enter a description under Alt text. Images that carry no information should be described as decorative in the description or removed; the export cannot guess intent.
3. Use the list tools for lists. Typed dashes and numbers are paragraphs. Bulleted and numbered lists created with the toolbar are exported as list structures.
4. Keep tables simple and give them a header row. Complex, merged, or nested tables are the least reliable structure in any export. Where a table is only being used to position content, replace it with normal paragraphs or columns.
5. Set the document title. The file name is used as the title in many viewers; make it a real title rather than "Untitled document" or "final_v3".
6. Write descriptive link text. "Click here" is exported as "Click here". Link the words that describe the destination.

Check the file after export

Open the downloaded PDF in the free PDF tag viewer. You should see a tree with H1 to H6 elements where you used headings, L and LI elements for lists, Figure elements with alternative text for images, and Table, TR, TH, and TD elements for tables. Then run the PDF accessibility checker, which reports machine-detectable problems and lists what still needs a human. The checks that most often need attention on Google Docs output are:

• Document language. Confirm the PDF declares a language. A missing language forces screen readers to guess the pronunciation rules and fails WCAG success criterion 3.1.1.
• Title metadata. Confirm the PDF's title property is set and that viewers are told to display it rather than the file name.
• Table headers. Confirm header cells are TH rather than TD, and that a table used for layout has not been exported as a data table.
• Reading order in multi-column or floated layouts. Read the tag tree top to bottom and compare it with the intended order. Text boxes and wrapped images are the usual culprits.
• Heading levels. A level skipped in Docs, such as Heading 1 followed by Heading 3, is exported as a skipped level.

When to use a different route

Two older approaches remain useful. Downloading the document as Microsoft Word (.docx) and exporting from Word gives you Word's PDF options, including bookmarks from headings and PDF/A output; the Word export guide covers the settings. Third-party add-ons for Google Workspace, such as Grackle Docs, check a document inside the editor and produce their own tagged output, and remain a reasonable choice for teams that already licence them. For documents that are updated often, the strongest option is to avoid the PDF altogether and publish accessible HTML, which is what hosted accessible HTML on DocAccessible does from an uploaded file.

Frequently asked questions

Sources

The statements above rest on the primary sources below. Where a source is a law or standard, the version and date named in the text are the ones checked on the review date. This guide is general information, not legal advice.

1. Google Workspace Updates, December 6, 2024: Adding improved accessibility tagging to PDFs exported from Google Docs
2. Google Workspace Updates, March 2025: Additional accessibility tags for Tables, Equations, and Checkboxes in PDFs exported from Google Docs
3. Google Docs Editors Help: Use Google Docs Editors with a screen reader
4. W3C WAI: PDF16, setting the default language with the /Lang entry
5. W3C WAI: PDF18, specifying the document title