LibreOffice Writer to PDF/UA: export and verify

LibreOffice Writer provides an open-source route from an editable document to a tagged PDF using its PDF/UA export option. Prepare the source, resolve relevant source-checker findings, export, and review the resulting file. Selecting a standards-oriented option is an instruction to the exporter, not an independent assessment of the author's headings, descriptions, or table design.

Build a source document that explains itself

Use an illustrative two-page volunteer information sheet to plan the process. It has a title, three sections, a numbered application procedure, a small opening-hours table, and a location diagram. Before considering PDF settings, ensure the sheet answers the practical questions: who can apply, how to apply, when the office is open, and how to locate it. A reader should not need to infer those answers from the appearance of a page.

Represent sections as a coherent heading hierarchy, use actual list formatting for the procedure, and keep the opening-hours table simple. Give the diagram a useful explanation and put essential directions into readable text. Confirm the document title and language. Keep the editable ODT alongside the final deliverable so corrections can be made without rebuilding structure in a PDF editor.

Run the Writer accessibility check

LibreOffice's Accessibility Check documentation describes the Tools-menu command and a sidebar panel that links to findings. Its documented checks include document identity, image descriptions, heading order, manual numbering, and certain table patterns. Use the findings to locate issues in the source and decide how to correct them. A flagged pattern is a reason to investigate, not a universal rule about every possible document.

For example, if the volunteer procedure was created by typing numbers at the start of ordinary paragraphs, replace that visual convention with a real numbered list. If the hours table uses merged cells to create a decorative title band, move the title into normal document content above a simpler table. These changes make the information easier to maintain as well as easier to review.

Export with the intended options

Open the PDF export dialog and select the PDF/UA option in its general settings. The LibreOffice PDF/UA help states that this automatically enables tagging. Use the current dialog for your installed version and record that version with the result. The help page also contains an older implementation note; it should not be mistaken for a complete description of every current build.

The general export documentation distinguishes export ranges, image settings, and other output options. Check that the intended pages are included and that image reduction has not made the location diagram unreadable. Review the security and distribution implications of optional content such as an embedded source document; a PDF intended for public download should include only what the publisher intends to disclose.

Save a clearly identified source revision and review its accessibility findings.
Choose the intended PDF/UA export configuration, page range, and image settings in the installed version.
Save a new PDF and reopen it from disk, rather than reviewing only the still-open Writer document.
Record the resulting PDF's identity and the validation profile used for any automated check.
Correct the source or document the remaining repair, export again where necessary, and repeat the affected checks.

Check the reader's result

Illustrative review of the volunteer information sheet.
Content	Verification task
Sections	Navigate to the application procedure by its heading
Numbered steps	Confirm the sequence and identify every required action
Opening hours	Find the closing time for a named day with its correct context
Directions	Explain the route using the text alternative and surrounding instructions
Application link	Reach and activate the correct destination by keyboard

Inspect machine-detectable findings with a suitable PDF checker, then review reading order, descriptions, and the tasks above. Use the screen-reader procedure in a recorded viewer environment. A checker can identify many structural problems; a person must still decide whether the directions are useful or whether the hours table communicates the intended information. The PDF/UA and WCAG comparison explains why these reviews answer different questions.

Keep the publication reproducible

Store the source revision, export settings, PDF, and review findings together. If the opening hours change, update the source and produce a new reviewed output. Do not assume that a previous approval applies to the changed file, even when its visual design is nearly identical. At publication, download the file through the public link and confirm that the new version is actually being served.

When a recurring structure does not export satisfactorily in your environment, simplify the source or plan a documented repair. Avoid presenting an unresolved issue as a software feature that guarantees conformance. The PDF checker can support the review, and the record of what was checked gives the next editor a useful starting point.

Frequently asked questions

Does the PDF/UA checkbox guarantee conformance?

The PDF/UA option requests standards-oriented output and enables tagging, but it cannot establish that the author's content is meaningful or that every output requirement is satisfied. Check the exported file and document the manual review.

Why does Writer flag a table or numbered paragraph?

Writer checks specified patterns that can interfere with accessible structure, including some merged-cell layouts and manually typed numbering. Inspect the specific finding and revise the source when needed rather than assuming every visually similar example has the same solution.

What should I save with the exported PDF?

Keep the editable source, application version, export configuration, reviewed PDF revision, and test notes. Those records let a later editor repeat the workflow and identify changes that require another review.

Sources

The statements above rest on the primary sources below. Where a source is a law or standard, the version and date named in the text are the ones checked on the review date. This guide is general information, not legal advice.