Guide

How to export an accessible PDF from PowerPoint

Slide decks fail differently: reading order comes from the selection pane, every slide needs a title, and SmartArt is a trap.

About 10 minutes · moderate

Why decks fail differently

A Word document has one reading order that follows the text. A slide is a canvas of floating objects, and nothing about their position determines the order they are read in.

That single fact causes most PowerPoint accessibility failures, and it is not intuitive: reading order is the Selection Pane’s stacking order, read from the bottom up.

Fix the reading order in the Selection Pane

Home → Arrange → Selection Pane, or Alt+F10.

The pane lists every object on the slide. The object at the bottom of the list is read first. The object at the top is read last. This is the reverse of what most people assume, and it is the reverse of the z-order intuition from design tools.

To fix a slide:

1. Open the Selection Pane.
2. Click each object in turn — it highlights on the slide, which is the only reliable way to know which entry is which.
3. Drag them so the bottom-to-top order of the list is the order you want them read.
4. Rename them while you are there. “Rectangle 47” tells you nothing; “Q3 revenue chart” does, and the names carry into the structure tree.

For a deck of any size, do this as you build rather than afterwards. Retrofitting forty slides is an hour; doing it as you go is nothing.

Every slide needs a title

The slide title is what a screen reader announces when a user arrives on a slide, and it is the whole of a deck’s navigation.

Use a real title placeholder, from a layout — not a text box that happens to be at the top. View → Outline View shows you the answer instantly: any slide whose title is blank in the outline has no title placeholder.

For a slide whose design genuinely has no visible title — a full-bleed image, a section break — put a title in the placeholder and move the placeholder off the slide canvas. It stays in the structure and in the outline, and it does not render. This is a legitimate technique rather than a workaround; the alternative is a slide a user cannot identify.

Duplicate titles are nearly as bad as missing ones. Four slides called “Results” leave a user unable to tell them apart. “Results — Northern district”, “Results — Southern district”.

Alt text, and the SmartArt problem

Every image, chart, icon and shape that carries information needs alt text: right-click → View Alt Text. Decorative shapes get Mark as decorative, which exports as an artifact rather than an empty figure.

Charts need the finding, not the description. “Bar chart” is useless; “Revenue rose from 4.2 to 6.8 million between 2021 and 2025, with the largest jump in 2023” is the content. See writing alt text.

SmartArt is the trap. It exports as a grouped graphic whose text becomes separate runs in an order nobody controls, so a process diagram becomes a scatter of disconnected phrases. Treat the whole thing as one image: select the outer group, give it alt text stating what the diagram communicates, and put the same information somewhere linear — a following slide, or the notes if you are exporting them.

Grouped shapes behave the same way. If a group is one idea, give the group alt text and leave the members alone. If the members are separate ideas, ungroup them and order them in the Selection Pane.

Tables

PowerPoint tables export with structure, and with one limitation worth knowing: PowerPoint emits a header row if you have ticked Header Row in Table Design, and it emits nothing else. No column scope, no Headers/ID references.

For a simple grid that is sufficient. For anything with merged cells or two header rows, plan on fixing it in Acrobat afterwards — or, better, reconsider whether a complex table belongs on a slide at all. It usually belongs in the document the slide refers to.

Contrast and text size

Decks are projected, which makes contrast failures worse than on screen. WCAG 1.4.3 asks for 4.5:1 for body text and 3:1 for large text, and a projector in a lit room delivers materially less than your monitor shows you.

Two things specific to slides:

Text over images. The most common contrast failure in decks. A caption over a photograph passes over the dark part and fails over the light part. Put a solid or semi-opaque panel behind the text rather than trusting the image.

Colour as the only signal. A legend that distinguishes series by colour alone fails 1.4.1. Add a pattern, a direct label, or different markers.

Export

File → Save As → PDF → Options, and tick:

• ☑ Document structure tags for accessibility
• ☐ PDF/A compliant — off

Or File → Export → Create PDF/XPS, same options.

Not File → Print → PDF. As with Word, the print pipeline discards all structure. The output looks identical and is untagged.

Run Review → Check Accessibility first and clear it. PowerPoint’s checker is good at exactly the things that matter here — missing slide titles, missing alt text, reading order it considers suspicious.

After the export

Two things still need Acrobat:

The document title and its display flag. File → Properties → Description → Title, then Initial View → Window Options → Show: Document Title. PowerPoint sets neither usefully — it writes the filename. See the title guide.

Heading structure. PowerPoint exports slide titles as H1 and everything else as P. A fifty-slide deck becomes fifty H1s with no hierarchy. This is acceptable for a deck — each slide genuinely is a top-level unit — but if your deck has sections, consider whether section-break slides should be H1 and content slides H2. It is a judgement about the document, and worth making deliberately.

Then check it: select all, copy, paste, and read the order. Slides are where reading order goes wrong most often, and it is the failure that two keystrokes find.

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.
• 09-001 Tags are not in logical reading order The order of elements in the structure tree does not match the order a human would read the page. This is the single most common substantive defect in tagged PDFs and the one Acrobat's own tooling handles worst.
• 13-001 Graphics objects are not tagged with a Figure tag An image or vector drawing that carries meaning is not inside a Figure element. Either it is untagged, or it has been swept into a paragraph.
• 14-001 Headings are not tagged Text that is visually a heading — larger, bolder, isolated — is tagged as a paragraph. The document has no navigable outline.

Last updated 2026-09-10 .