19/month · 7-day free trial

Twelve structural passes on your InDesign‑exported PDFs.

The tag‑tree grunt work you’d otherwise do by hand in Acrobat — automated. You still own the accessibility decisions; we just clear the boilerplate.

Reader with an open page under a warm sun A hand-drawn editorial illustration: a figure attends to an open page of ruled text, while a warm orange sun hovers in the upper-right corner. The line work is continuous and expressive in the Picasso tradition.

How it works

Three steps, one upload.

  1. Export from InDesign

    Export your document as a tagged PDF via File › Export › Adobe PDF with “Create Tagged PDF” on.

  2. Review the pre-flight audit

    We open your file read-only and show which PDF/UA checks already pass, which the pipeline will fix for you, and which need a decision from you — language, document title, and per-table header scoping where relevant. Nothing is modified until you confirm.

  3. Download and validate

    Download the processed PDF. Validate with PAC 2024, Acrobat’s accessibility checker, or axe for PDF, and fix anything that remains manually.

What you get

The structural work, not the accessibility judgment.

What this tool does

  • Merges multi-line paragraph MCIDs. Every word-wrapped paragraph in an InDesign-exported PDF ships as a separate marked-content block per visual line. Validators like PAC 2024 don’t flag it — it’s technically valid PDF/UA — but certain screen readers, including Acrobat’s built-in Read Out Loud, treat each line as its own unit, chopping the reading rhythm across a paragraph that should flow as one. Fixing by hand means re-parenting every stray leaf in Acrobat’s Tags tree by mouse — an hour of fiddly work per medium document. We finish it in under a second.
  • Tag-tree cleanup. InDesign’s export routinely ships structural litter — empty tags, whitespace-only paragraphs, duplicate and dead references, untagged orphan content — each one a line a remediator would delete by hand in Acrobat’s Tags tree. The pipeline clears all of it in one pass: prunes the empty elements, trims trailing whitespace, dedupes references, drops dead annotation pointers, and artifact-wraps orphans so they render but don’t clutter the accessibility tree.
  • Consolidates redundant <Span> tags. InDesign wraps every character-style run in a <Span>, even when there’s no accessibility payload on it. Acrobat’s Tags tree ends up two or three times deeper than it should be, and the extra depth confuses some assistive tech. We flatten the unnecessary ones and preserve the Spans that carry real metadata (/Alt, /ActualText, /E) so the tree reads as the author intended.
  • Sets the document language and PDF/UA-1 metadata (/Lang, DisplayDocTitle, MarkInfo/Marked, XMP pdfuaid:part).
  • Wraps untagged decorative artwork — including paths inside referenced Form XObjects — as artifacts so screen readers skip them.
  • Adds Row, Column, or Both scope to table header cells — you pick, per table, based on previews.
  • Unwraps <Table> tags that InDesign nested inside <P>.
  • Sets /Placement /Block on inline-by-default tags so they render as blocks in the tag tree.
  • Generates PDF bookmarks from your heading structure, with full ToUnicode support for non-ASCII languages.
  • Reconciles /Form struct-tree order with widget position so tab order matches the visual reading order.
  • Sets /Tabs=/S on every page with annotations — links, form fields, sticky notes — so the Tab key walks them in reading-order per PDF/UA. InDesign handles this for form pages but routinely omits it on link-only pages, which PAC flags.
  • Preserves every form field, widget, and JavaScript action in your document.

What this tool does not do

  • Does not guarantee PDF/UA-1, WCAG 2.1 AA, Section 508, or AODA compliance. You still validate the output.
  • Does not work on untagged PDFs — your InDesign export must have “Create Tagged PDF” turned on.
  • Does not repair a wrong reading order. Fix the Articles panel in InDesign first.
  • Does not add alt text to images. Set those in InDesign’s Object Export Options before you export.
  • Does not OCR scanned pages. The PDF must already contain real text.
  • Does not fix colour-contrast problems in your content.
  • Does not rewrite link text, form labels, or button names.
  • Does not decide the correct semantic tag for anything — that is your choice in InDesign, before export.

Your responsibility as the author

  • Tag your document correctly in InDesign before exporting (paragraph and character styles mapped to PDF tags; Articles panel set; Object Export Options reviewed).
  • Provide alt text for every meaningful image in InDesign’s Object Export Options.
  • Set a correct reading order via the Articles panel.
  • Ensure colour contrast meets WCAG 2.1 AA (4.5:1 for normal text, 3:1 for large text and UI).
  • Write meaningful, plain-language content.
  • Validate the processed file yourself using PAC 2024, Acrobat’s built-in accessibility checker, axe for PDF, or equivalent.
  • Test with assistive technology (a screen reader like NVDA, JAWS, or VoiceOver).
  • Manually fix anything the tool cannot address.

Pricing

One plan. Try it free for seven days.

19 / month

Billed monthly. Cancel any time.

  • No file retention — uploads live only for the duration of one request
  • Seven-day free trial, no charge if you cancel before it ends
  • Self-serve cancellation via the Stripe Customer Portal

Questions

Frequently asked

Will this make my PDF fully accessible?

No. Accessibility is a judgment about the whole document: correct semantic tags, meaningful alt text, a logical reading order, sufficient colour contrast, and plain language. Those are decisions only you can make, and most of them have to happen in InDesign before you export. What we do is automate the repetitive structural cleanup that would otherwise eat hours of your time in Acrobat’s Tags tree.

What if my PDF is from Word, Pages, or LaTeX?

It may work, but it is not tested, supported, or guaranteed. This tool is built around the specific tag structures InDesign produces. If your upload’s /Producer field does not include “Adobe InDesign” we show a warning on the upload page, but we do not refuse the file.

Do you store my files?

No. Uploaded PDFs live in /tmp/<uuid>/ only long enough to audit, process, and deliver. As soon as you choose Download, Email, or Download and Email on the result page, we record a tombstone row for the delivery, stream the file to your chosen destination, and delete the working directory. No file content ever touches our database or long-term disk.

How do I cancel?

Sign in and click Manage subscription in the top nav. You will land in Stripe’s Customer Portal where you can cancel immediately or at the end of the current period. No email exchange required.

Why “twelve passes”?

The underlying pipeline runs twelve discrete structural transformations against your tagged PDF: catalog metadata, XMP metadata, untagged-path artifact wrapping, redundant <Span> consolidation, tag-tree cleanup, paragraph MCID merging, parent-tree reconciliation, table-header scoping, <Table> unwrapping, placement fixes, form-widget struct-tree reordering, bookmark generation, and structure-based /Tabs /S on every annotation-bearing page. The full list is under “What this tool does” above.

Can I opt out of specific passes?

Yes. The configure screen renders an “Apply this fix” checkbox next to each automatic pass — default checked. Uncheck any you’d prefer to handle yourself or whose output you want to preserve as-is: redundant <Span> consolidation, multi-line MCID merging, tag-tree cleanup, bookmark generation, or structure-based /Tabs /S. The rest of the pipeline still runs, and the result page lists anything you opted out of so you know what PAC will continue to flag. The mandatory PDF/UA baseline (language, XMP metadata, parent-tree integrity) always runs.

Who built this?

ACHECKS — the same team that runs the ACHECKS accessibility evaluation platform. This tool is a standalone product, separate from the ACHECKS account system and billed independently.