
LibreOffice automatically enables Tagged PDF when you select PDF/UA, so the tagging control cannot be disabled in that mode. Tags are part of the accessible-document structure, not an optional image-quality setting. If the export fails a check, repair the source rather than trying to remove the required structure.
Key Takeaways
- PDF/UA export requires tagged output in LibreOffice.
- Tags do not automatically make every description or reading sequence correct.
- Review the exported PDF with the intended users' tasks in mind.
Understand the dependency
The PDF Export General documentation states that selecting PDF/UA automatically enables Tagged PDF and prevents disabling it. A locked control therefore reflects the selected standard, not necessarily a damaged application.
Confirm that PDF/UA is the required delivery target. If it is, retain that setting and address the reported accessibility issues. If another standard is required, document the client's specification before changing the export target. Do not remove accessibility features merely to make a warning disappear.
Prepare the source intentionally
Run Tools > Accessibility Check. LibreOffice's checker documentation covers title, language, image alternatives, headings and other source issues. A checker result helps locate problems, but meaningful alternatives still require editorial judgment.
For a hypothetical photo brief, an image of a marked camera position needs a description of the relevant position, not just “image.” A purely decorative flourish needs different treatment. Structure the brief's sections as headings and preserve genuine lists for step-by-step instructions.
Inspect what the PDF actually exposes
A tagged file can still have confusing order or inadequate descriptions. Open the exported artifact with an appropriate PDF tool and inspect headings, figures, captions and their sequence. The figure-and-caption reading-order guide provides a useful task-specific comparison.
Check the document language, especially in bilingual work. PDF language tags support pronunciation, but they do not translate the content or verify the accuracy of the wording.
Define a real acceptance task
Ask whether a reader can find the delivery deadline, navigate to the shot list and understand a reference image without seeing it. Those tasks test usefulness that a checkbox cannot establish. Record the reader, application and checks used if the brief has formal accessibility requirements.
Keep the source available for corrections. An export route that preserves structure is preferable to a print-style conversion that may discard it; compare the tagged export route guide.
This explanation is based on documented settings and proposed review tasks. It does not certify PDF/UA conformance or claim that an automated checker alone can establish accessibility.
When an image communicates a required editing step, ask a reviewer to follow that step from its description. If they cannot identify the selected region or intended change, revise the wording. A technically present alternative that omits the actual instruction is still inadequate for the task.
Related tasks
- Why Did My Word or PowerPoint PDF Lose Alt Text and Document Structure?
- Why Does My Bilingual Photo Book Use the Wrong Reading Language?
- Why Does a Screen Reader Read My Photo-Catalog Caption Before the Wrong Image?
Sources and scope
- PDF Export General: Mandatory dependent option; do not disable accessibility merely to alter file size.
Documentation-based guidance; proposed review checks have not been run on a sample file.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.