A beautiful layout is not an accessible one
InDesign gives you total control over how a page looks, and almost none of that work creates the structure an accessible PDF needs. Accessibility in InDesign is a separate, deliberate layer: tagging, reading order and alt text that you build alongside the visual design, not something the export does for you.
This guide is part of our wider document accessibility guide. Because InDesign output is almost always finished in Acrobat, read it alongside the Acrobat accessibility guide. Creative and marketing teams may also want our accessible graphic design and desktop publishing services.
1. Why a print mindset breaks online
InDesign was built for print, and print thinking runs deep in how it is used. You compose a page by placing frames wherever they look right, lining up columns by eye, and treating type as a visual element. For a printed brochure that is exactly the right approach, because the only output is ink on paper and the only reader is a sighted one.
The moment that page becomes an online PDF, the rules change. A screen reader ignores the visual layout entirely and reads the document's tag structure in sequence. If the frames were placed for looks, the reading order will be wherever the frames happened to be created. If a heading is just larger type, it is not a heading. If an image has no alt text, it is silence. The export looks identical to the printed page and is, to assistive technology, a picture of a document.
The shift: treat accessibility as a structural layer you author in InDesign, the same way you author the visual layer. Mapped styles, a defined reading order and alt text are not optional extras, they are what turn a layout into a readable document.
This is the principle behind accessibility isn't a button or an add-on: structure has to be built in, not bolted on after export.
2. Common InDesign pitfalls to look for
- Exporting an untagged PDF, or using Print PDF without the Create Tagged PDF option, producing a file with no structure at all.
- Paragraph styles not mapped to tags, so headings and lists export as generic paragraphs.
- No reading order defined, leaving the Articles panel empty and the export following frame creation order.
- Headings faked with size and weight instead of real, mapped heading styles.
- Missing alt text on placed images and graphics.
- Decorative elements not marked as artifacts, so rules, flourishes and background images get read aloud.
- Tables drawn with lines and tabs rather than built as real tables.
- Text set as outlines or living inside images, which removes it from the text flow entirely.
- Document title and language not set, so the PDF metadata is wrong from the start.
- Assuming the export is finished, when InDesign output almost always needs completion in Acrobat.
3. Paragraph styles and export tags
Structure in an InDesign PDF comes from mapping your paragraph styles to PDF tags. This is what tells the export which text is a heading, which is a list, and which is body copy. The underlying criterion is 1.3.1 Info and Relationships.
- Use paragraph styles consistently for everything. Avoid local overrides that bypass the style.
- Open each style and set Export Tagging (Paragraph Style Options > Export Tagging) to map it to the right PDF tag: H1, H2, H3, P and so on.
- Keep one H1 for the document title and a logical heading hierarchy below it.
- Map list styles so bulleted and numbered content exports as real lists.
4. Reading order and the Articles panel
The Articles panel (Window > Articles) is how you define the order a screen reader will read the page. This is essential because InDesign otherwise exports content in the order frames were created. The criteria are 1.3.2 Meaningful Sequence and 2.4.3 Focus Order.
- Create an article and drag page items into it in the exact order they should be read.
- Tick Use for Reading Order in Tagged PDF in the panel menu, or the order will be ignored on export.
- Leave decorative items out of the article so they can be treated as artifacts.
- For multi-column and multi-spread layouts, check the order carefully; this is where reading order most often goes wrong.
5. Alt text and anchored objects
Placed images need alternative text, and the way an image is anchored affects whether it lands in the right place in the reading order. The criterion is 1.1.1 Non-text Content.
- Set alt text per object via Object > Object Export Options > Alt Text. You can pull it from the image's XMP metadata or type it directly.
- Use the Tagged PDF tab in Object Export Options to mark decorative images as artifacts.
- Anchor images into the text flow where it helps keep them in the correct reading position.
- For charts and infographics, give a concise alt text and provide the underlying data as real text or a table.
6. Tables, lists and language
- Tables: build them with InDesign's table tool, not with tabs or drawn lines. Define header rows (Table > Convert Rows > To Header). Note that header cells usually still need confirming in Acrobat.
- Lists: use real bulleted and numbered lists driven by paragraph styles, mapped to list tags on export.
- Language: set the document language with the type, and confirm it in the exported PDF. See 3.1.1 Language of Page.
- Title and metadata: set the document title under File > File Info so the PDF announces a real title.
7. Exporting a tagged PDF
Export settings make or break everything you set up above.
- Use File > Export and choose Adobe PDF (Print) with the Create Tagged PDF option enabled, or Adobe PDF (Interactive) for forms and rich media. For most documents, tagged Print PDF is the reliable choice.
- Confirm Create Tagged PDF is ticked. Without it, none of your style mapping or reading order is written into the file.
- Set the document title to display from the document title, not the file name, in the export options.
- Do not flatten transparency or rasterise text, which destroys the text layer.
8. Finishing in Acrobat
InDesign gets you most of the way. Acrobat Pro is where you complete and validate the work.
- Verify the tag tree matches the content and the reading order is correct.
- Set table header cells and scope, which InDesign cannot do reliably.
- Confirm alt text, document title, language and bookmarks.
- Run the Accessibility Check, and PAC for PDF/UA conformance, then read the document with a screen reader.
The full Acrobat workflow is in our Acrobat accessibility guide. For an independent check on the finished file, see audit and compliance.
9. Common questions about InDesign accessibility
Can InDesign produce an accessible PDF on its own?
It can get most of the way with mapped styles, the Articles panel and Object Export Options, but it almost always needs finishing in Acrobat for table headers, reading-order checks and PDF/UA validation.
What does the Articles panel actually do?
It defines the reading order of the tagged PDF. You drag items into it in the order they should be read and tick Use for Reading Order in Tagged PDF. Without it, content exports in the order frames were created.
Why does my exported PDF read in the wrong order?
Almost always because no reading order was defined in the Articles panel, so InDesign fell back to frame creation order. Define the order in Articles, re-export, then confirm in Acrobat.
Do I need Acrobat Pro as well as InDesign?
For accessible PDFs, yes. Acrobat Pro is where you set table headers, verify reading order and confirm conformance. See the Acrobat guide.