What Your InDesign Paragraph Styles Are Actually Doing
And why they can make or break accessible PDFs
If you’ve read our guide to designing print materials everyone can read, you already know the basics:
Readable fonts
Strong contrast
Clear language
Generous white space
But if you work in Adobe InDesign, there’s another layer of accessibility that lives beneath the surface, one that most designers never see and almost never set up intentionally. It’s the connection between your paragraph styles and the PDF tags that tell assistive technology what your document actually means.
This post is for print designers who use InDesign and want to understand how the software creates structure, not just appearance, and how to use that structure to produce PDFs that work for more readers.
The invisible architecture of a PDF
When you export a document from InDesign as a tagged PDF, something happens that has nothing to do with how the file looks. InDesign writes a set of invisible labels, called tags, into the PDF file.
These tags describe the role of different pieces of content: this is a heading, this is a paragraph, this is a list item, this is an image.
Screen readers, document navigation tools, and assistive technologies rely on those tags to interpret and read the document in a logical order. A sighted reader sees a beautifully laid-out page. A screen reader sees a sequence of tagged content or, if the tags are missing or wrong, a confusing jumble of text with no clear structure.
For text, many of those tags come from your paragraph styles.
How the chain works
Here’s the relationship, step by step:
InDesign paragraph style → Export Tag → PDF structure tag → assistive technology interpretation
Every paragraph style in InDesign has a setting many designers never touch: Export Tagging. You’ll find it by double-clicking any paragraph style and scrolling to the Export Tagging section.
This is where you tell InDesign: “When this style goes into a tagged PDF, treat it as a heading, paragraph, list item, or other structural element.”
If you leave Export Tagging set to Automatic, InDesign will make its best guess. Sometimes it guesses well. Often it needs help, especially in complex documents with multiple heading levels, callout boxes, captions, sidebars, or non-linear layouts.
The fix is straightforward: set Export Tags intentionally for the paragraph styles that define your document structure; then check the exported PDF in Acrobat.
A practical tagging reference
This is how common InDesign styles often map to PDF tags:
| Your Paragraph Style | Export Tag to Use | Notes |
|---|---|---|
| Document Title | h1 | Usually one per document |
| Heading 1 (major sections) | h2 | H1 is reserved for the document title, so to maintain hierarchy, you’re “leveling down.” |
| Heading 2 (subsections) | h3 | Maintain the hierarchy — don’t skip levels |
| Heading 3 | h4 | Keep stepping down, keep the outline logical |
| Body text | p | Standard paragraph |
| Captions | p | Keep meaningful captions in the reading order |
| Pull quotes / callouts | blockquote | Use BlockQuote only if it truly functions as a quotation or aside |
| Bulleted list items | li | Use real InDesign list formatting |
| Numbered list items | li | Use real InDesign list formatting |
The most important rule here: heading levels must be sequential. If you go from H2 to H4, screen readers may flag that gap as a structural error, and users navigating by headings can lose their place.
Think of heading levels as an outline. Every sub-point needs a parent.
Also, don’t confuse the document’s visible title with the PDF’s metadata title. Your main document heading may be tagged as H1, but the PDF also needs a document title set in its file properties. Those are related, but they are not the same thing.
The Mistake That Breaks Everything
Here’s the trap almost every designer falls into: using heading styles for visual effect rather than document structure.
It goes like this. You have a callout sentence, something you want to stand out visually. You apply Heading 2 because it has the right size and weight. It looks great on the printed page.
But you’ve just told the screen reader that this callout is a major section heading. A person navigating your document by headings, which is a common accessibility technique, may jump to it expecting a new section and find a sentence that goes nowhere.
The document’s logical structure is broken.
The solution isn’t to avoid making things look big, bold or prominent. The solution is to build your paragraph styles so visual hierarchy and document hierarchy align. Your Heading 2 style should look the way it looks because it marks a major section, not the other way around.
If you need something to look bold or prominent without being a heading, create a dedicated style for it: Callout Text, Pull Quote or Feature Text. Tag it appropriately as a paragraph or block quote. Style it however you like. Just don’t repurpose a heading level.
Reading order: the problem multi-column layouts create
Tags tell a screen reader what things are. Reading order tells it what sequence to follow. These are two separate things, and multi-column layouts can break them apart quickly.
Imagine a two-column newsletter. The visual reading order may be obvious to a sighted reader: read the left column top to bottom, then move to the right column. But an exported PDF may follow object order rather than the way a person visually understands the page. The result can sound like gibberish.
The tool that helps fix this is the Articles panel.
The Articles panel lets you define reading order explicitly by dragging text frames and image frames into a sequence that makes logical sense. In the Articles panel menu, choose Use for Tagging Order in Tagged PDF. Without that setting, simply placing items in the panel may not control the exported tag order the way you expect.
This can be tedious. Most designers skip it. But if you produce multi-column documents, newsletters, or annual reports for organizations that serve people with disabilities, it is the difference between a document that actually works and one that only looks like it does.
Images: the alt text gap
Every meaningful image you place in an InDesign document needs a text description, called alt text, that a screen reader can announce in place of the image.
To add alt text in InDesign, select the image frame, then go to Object → Object Export Options → Alt Text. You can type a description directly or pull it from the image’s XMP metadata if you’ve added it in Bridge or Photoshop.
A few guidelines for writing useful alt text:
Describe what the image communicates, not just what it shows. “Bar graph showing a 40% increase in program participants from 2022 to 2024” is more useful than “bar graph.”
Keep it concise. Short is usually better, but complex charts, maps or diagrams may need longer descriptions elsewhere in the document.
If the image is purely decorative, such as a divider, background texture or redundant visual element, mark it as an Artifact in the Object Export Options. This tells screen readers to skip it, which reduces noise for the user.
Don’t start with “image of” or “photo of.” Screen readers already announce that it is an image.
The export settings that actually matter
When you’re ready to export, the settings you choose in the export dialog have a direct impact on accessibility.
Go to File → Export, then choose Adobe PDF (Print) or Adobe PDF (Interactive), depending on your use case.
In the Export dialog, look for these settings:
Create Tagged PDF. This is the master switch. If this is off, your structure will not export as a tagged PDF.
Use Structure for Tab Order. This is especially important for interactive PDFs and forms. It helps keyboard navigation follow the document structure rather than an arbitrary visual order.
If you’re exporting a form with fillable fields, also check Include Hyperlinks and make sure field tab order is set correctly before you export.
After export: check your work
Even a carefully prepared InDesign file can produce a tagged PDF with problems. Always verify the exported file in Adobe Acrobat Pro.
Run Acrobat’s accessibility check, then review the document manually. Automated checkers can catch many common problems, but they cannot confirm whether the reading order makes sense, whether alt text is meaningful, or whether the document actually works for a screen reader user.
Pay special attention to:
Document title and language
Heading structure
Reading order
Meaningful alt text
List and table structure
Form-field labels and tab order
Color contrast
Some problems are quick fixes in Acrobat. Others, especially reading order and tagging problems, are usually better fixed in InDesign and re-exported so the source file stays clean.
The bottom line
A beautifully laid-out PDF that falls apart for a screen reader user is not an accessible document. The gap between visual design and structural accessibility is exactly where most well-intentioned print design fails.
The good news: InDesign has the tools to close that gap. They are just not the tools most designers think about first.
Set your Export Tags intentionally.
Build a logical heading hierarchy.
Use the Articles panel for complex layouts.
Write meaningful alt text for every image.
Check your work in Acrobat before you consider a document done.
Accessible design is not a layer you add at the end. It is a discipline you build into the process. And when you do, your documents are better for every reader, not just the ones using assistive technology.
