Skip to main content
Participant
Oct 22, 2026 1:17 PM UTC
Question

Best practices for creating accessibility compliant PDFs?

Hi all,

I have been using FM for five years to develop textbooks. Every six months or so, I look into this issue and come up empty, even though I have submitted bug reports and talked to user support.

Long story short, I cannot get FM to reliably create accessibility-compliant PDFs. The approaches described under “Tagged PDF output” and the accessibility items in the FM documentation do not consistently produce PDFs that meet post-2020 standards in many countries. As a result, the files are rejected by a growing number of publishers and distributors because they cannot pass basic automated tests.

This experience seems to match several other posts over the past few years, and I have not seen any recent posts or breakthroughs. I am using the most recent (Sept 2026) version, unstructured.

I am always happy to experiment with specifics, but my question is: can anyone point to a guide or best practices document? The most recent posts I can find point to using Acrobat to remediate the FM-generated PDFs, but that doesn’t scale very well.

Thanks,

Steve

    2 replies

    Jeff_Coatsworth
    Community Expert
    Community Expert
    Oct 22, 2026 1:29 PM UTC

    Got any Tracker report links for others to vote on?
    How are you creating the PDFs? The Publish and Save As PDF routes all use the new PDF generator; Printing to PDF still uses the older Adobe PDF printer instance engine. You can hijack the new Publish route to use the older engine (and a different maybe-more-compliant job options file?) by selecting the Distiller option in the Publish PDF Settings.

    Translate
    Participant
    Oct 22, 2026 2:33 PM UTC

    Hi Jeff,

    Thanks for the speedy reply.

    I can’t for the life of me find the two tracker items. The community update of a few months ago confuses me but that’s an user error on my part.  I’ll look later today.

    This post from last year captures a lot of what you recommended before, and I find it both very helpful (so thanks!) but also illustrates some of the larger issues. I talked to the nice FM tech support people six months ago and they confirmed many of these issues.

    To the best of my knowledge, I am following the directions for creating a tagged PDF in FM while heeding the advice from (among others, there are many helpful people) Matt Sullivan, you, Andrew Strauss, and Barb Binder in the forums and elsewhere about greeting accessible PDFs. I won’t recreate that information here but have a few links below.

    This is my understanding of key points from those conversations, I’ve been keeping them as notes to myself.

    Must do items

    • Add ‘alt text’ or alternative text to all figures.
    • Get rid of any ‘layout tables’, or tables used primarily for formatting text of pages (e.g., using a single-column multi-row table to organize a bibliography or using a 2x3 table with no header row to compose a series of images). Tables in a tagged PDF should ONLY be data tables, with rows and columns corresponding to data items, because screen readers will balk at layout tables. Make sure every table has a designated header row distinct from body rows.
    • Most critical is using the Publish panel and generating a Tagged PDF.  Using distiller directly does not go well.
    • PDF settings. This is described better elsewhere, but make sure that the PDF settings (Format > Document > PDF Setup) are consistent for all book chapters. Select all chapters in the book and set them all at the same time.
    • Clean up the document because any extra cruft seems to introduce errors into the tagged PDF or can disrupt the print process (e.g., get rid of unused reference and master pages, swap out old fonts, simplify equations where possible).

     

    Things that seem to matter sometimes but not others. All of these tweaks seem to lead to fewer crashes but they are inconsistent.

    • Output PDF must be on local drive, not DropBox or some other remote drive. FM seems to get stuck on the final pass of document tagging and either crashes or has to be force closed.
    • FM seems to get stuck if the final chapter (e.g., an index) is open and visible in the FM authoring interface.
    • When generating a PDF for the entire book, the settings in the top level book file will overwrite chapter settings. Make sure that file has the PDF tag-to-heading mapping. This said, these settings seem to disappear sometimes, it’s very frustrating.
    • Do a bookwide update on all chapters (e.g., refresh everything, especially TOC and index).
    • If FM persistently crashes, reboot the machine.
    • Occasionally, figures that rely on TIFFs won’t move to the PDF. The only workaround I have found is to open the original image, resave as TIFF in the OS, change the file extension to .TIF, and then reimport into FM.

    Missing features

    • Ability to add alt-text to the images on reference pages (e.g., the lines used to denote footnotes). Some of these images can be tagged as ‘decorative’ but there may be other ones, like warning signs or pictures, that should have alt text but FM doesn’t have the capacity.
    • Updated tagging of pagination artifacts (e.g., page numbers, running heads).
    • I’ve put in a feature request after talking to Adobe help. Ability to have a ‘figure above’ paragraph tag, which would free authors from having to use anchored frames that combine both an image and a figure caption. Combining these elements seems to confuse Acrobat when dealing with alt-text but the impact is inconsistent and hard to reliably recreate.
    • Figure references within figure captions fail (e.g., if you have a figure caption for Figure 2.3, and it refers (within the caption) to another figure (e.g., Figure 2.1), then the PDF check fails and you have to manually fix the issue in Acrobat.
    • Heading styles get incorrectly inserted in paragraph tags (i.e., the heading tags are stuck via a span inside <P> tags) no matter how many times you modify the Document > PDF settings.

     

    https://community.adobe.com/questions-643/accessibility-issues-when-adobe-framemaker-files-are-saved-to-pdf-753288#M86453

    https://community.adobe.com/questions-94/which-font-type-1503789

    Barb Binder’s blog posts at https://www.rockymountaintraining.com/ are very helpful for understanding the underlying settings

    https://accessible-pdf.info/en/basics/acrobat/general-working-with-pdf-tags-in-acrobat/

     

    Translate