Merge tagged PDFs with an editor that preserves their document structures, then review the combined result. The important question is not simply whether every page is visible. Readers also need a coherent sequence, useful navigation, and accurate relationships between text, figures, links, and tables. An approval of each input file does not automatically cover the assembled publication.
Make an assembly plan before changing files
Suppose a fictional handbook contains a policy document, a timetable, and an application form. Record the source filename and revision for each, the expected page count, the intended section order, and any interactive features. Identify an input that has no tags or has unresolved findings. Combining it with a tagged document does not resolve those findings.
Keep the input files and work on a new output. Write a simple acceptance list: the policy comes first, the timetable follows it, the form is last, each section has a useful navigation entry, and no required page is missing. This list gives a reviewer something independent of the editor's success message to compare with the result.
Treat merge, insert, and replace as different operations
Adobe's accessible-PDF creation guidance discusses combining tagged and untagged inputs and checking structure after page insertion. In particular, newly inserted content can require attention to its position in the tag tree. Review the document structure as well as the thumbnail order; the two views answer different questions.
Adobe's page replacement documentation describes replacement behavior that retains original interactive elements such as links or bookmarks while replacing page text and images. That makes replacement especially worth reviewing: an old interactive target can remain present while the visible content changes. Confirm the behavior of the exact editor and operation you use.
| Operation | What to inspect next | Example failure to look for |
|---|---|---|
| Combine three files | Section sequence and content coverage | The form appears visually but its meaningful content is absent from the structure |
| Insert a revised timetable | Tag order and cross-references | The new page is read after the form rather than after the policy |
| Replace a page | Existing links, annotations, and destinations | A retained link points to the previous policy section |
| Delete an obsolete page | Navigation and references | A bookmark or contents entry no longer identifies the intended section |
Rebuild a coherent document identity
Choose a title and language appropriate to the combined publication. Check the heading hierarchy across input boundaries: three separate documents may each begin with a title, but the assembled handbook needs an understandable overall organization. Do not change levels mechanically just to make a tree look tidy. Read the sections and decide which relationships the combined publication actually expresses.
Review page labels against the printed numbering. A reader following an instruction to consult page 12 should not have to guess whether it means the twelfth physical page or a printed label. If the appendices retain separate numbering, make that distinction explicit and consistent. Confirm that the form remains usable in the intended reader environment.
Test navigation as a reader would
Adobe's bookmark documentation distinguishes miniature page previews from text-labeled navigation destinations. Inspect the bookmark names and the place each one actually opens. A bookmark that still works technically can be wrong editorially if it now lands in a different section. Check the visible contents page independently, because it is another set of links or references.
- Open the combined PDF and locate each planned section without scrolling through every page.
- Read across the boundary between two inputs and confirm that the sequence remains coherent.
- Follow internal and external links, then check that their destinations still match their labels.
- Test a table, figure explanation, and form interaction from the assembled file rather than from the original inputs.
- Run the chosen PDF checks and review new findings alongside the known input findings.
Bind approval to the assembled revision
Save the assembly plan, input revisions, editor version, and findings with the final output. If one attachment arrives late, identify what changed and repeat the affected checks. A replacement of equal page count can still alter links, text, and structure. Comparing only the number of pages would miss those changes.
Use the PDF tag viewer to inspect structure and the screen-reader procedure to test the reading experience. Before release, obtain the document from its real download link and confirm it is the approved assembled revision. For the separate organizational task of collecting many contributors' files, use the board meeting packet workflow.
Frequently asked questions
Can I assume two accessible PDFs make an accessible combined PDF?
Each input review is useful evidence, but the combination creates new section boundaries, navigation, metadata, and possible interactions. Review the assembled file and record its own findings before treating it as ready to publish.
Why can the page thumbnails look right while reading order is wrong?
Thumbnail order shows the sequence of visible pages, while the logical structure controls another part of the reading experience. Inspect both after inserting or combining content, then test the sequence in an appropriate PDF viewer.
Do I need another review when a replacement has the same page count?
An equal page count does not establish unchanged content or structure. Check the revised material, retained interactive elements, references, and navigation, and bind the updated review to the new assembled file.
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.
- Adobe: Creating accessible PDFs . Combined files, tagging, and inserted-page structure.
- Adobe: Replace PDF pages . Page replacement and retained interactive elements.
- Adobe: Page thumbnails and bookmarks . Navigation entries and destinations.
Keep reading
PDF bookmarks and accessible tables of contents
Create a useful bookmark hierarchy and linked contents page, distinguish them from heading tags, and test destinations after document revisions.
Read the guide →Accessible board meeting packets: review guide
Organize agendas and exhibits, review mixed-source PDFs, handle late replacements, and publish a packet with reliable navigation and version records.
Read the guide →See the tag tree an export wrote
Read the logical structure of any PDF in the browser: headings, tables, figures, and role maps.
Open the tag viewer →