Tutorials
Claude Opus 5.5: Repair the Reading Order of a Product PDF
Ask Claude Opus 5.5 to propose a reading-order map for a product brochure before changing its PDF tags.
Make it with Panelly
Turn inspiration into your next product ad
Bring a product image and an idea. Create a four-panel ad, a coordinated asset set, or a video with Panelly.
Create with Panelly Edit the brief before you generate.
Ask Claude Opus 5.5 to propose a reading-order map for a product brochure before changing its PDF tags. Supply both the visible page and its current structure. A visually correct two-column layout can still read across columns, separating a product claim from its qualification. The deliverable is an explicit content sequence and a verification script for the human reviewer.
Inspect structure as well as appearance
A 2018 developer question describes a screen reader traversing several columns left to right. The author later says the document was already tagged. That historical report illustrates why the presence of tags alone is not proof of correct order.
The W3C PDF3 technique explains how logical structure affects reading order and how to verify it with assistive technology. It is an informative technique, not a claim that one automated check certifies an entire brochure. Keyboard tab order for links and controls also needs separate attention.
| Evidence | What it reveals | What it cannot establish alone |
|---|---|---|
| Page screenshot | Columns, proximity and visual grouping | The actual tag sequence |
| Tag-tree export | Logical sequence and structure | Whether descriptions are useful |
| Copied plain text | A quick symptom of ordering problems | Actual screen-reader behavior |
| Reading and keyboard session | Observed spoken and focus sequence | Every reader and device combination |
Map six blocks without losing the qualifier
Use this fictional brochure: A is the product heading; B is a battery claim; C is its test-condition note; D is a care heading; E is care instructions; F is a support link. The intended sequence is A → B → C → D → E → F. A row-wise extraction A → D → B → E → C → F interleaves the two topics and delays the condition that limits the battery claim.
Keep stable block IDs in the review map. For each block, record page, visible text, proposed semantic role and next block. Do not move C to a general footnote pile merely because its font is small. Its connection to B is part of the meaning. Decorative lines may be artifacts; a meaningful product diagram needs an appropriate accessible alternative, not automatic removal.
Copy the bounded repair prompt
Review the supplied product PDF screenshot, extracted text and tag-tree export. Do not infer the existing tag order from the screenshot. If structure is missing, request an export and mark order unknown.
For this illustrative page, propose A(product heading) → B(battery claim) → C(test condition) → D(care heading) → E(care instructions) → F(support link). Preserve every claim, number and qualification verbatim in the real document.
Return page/block ID, current order, proposed order, semantic role, evidence and unresolved ambiguity. Keep the qualification adjacent to its claim. Distinguish meaningful illustrations from decoration. Report reading order separately from keyboard tab order.
Suggest the smallest source-document or tag-tree repair. Do not claim that you edited or certified the PDF. Provide a human test: read from page start through both columns, verify heading navigation, reach the support link by keyboard, activate it, and repeat after export. Record the actual reader/tool used and untested cases.This is an editorial workflow proposal using the official Opus prompting guidance, not a tested model remediation. The six-block sequence is a fictional diagnostic example.
Fix the source and test the new export
Where possible, repair heading structure and content flow in the authoring document, then export a tagged PDF. If repairing the PDF directly, retain the original and inspect the affected tag subtree. Re-exporting from an unchanged source can erase the repair. Check that the visible layout, claim wording and link destination remain correct, then perform the reading and keyboard sequence on the delivered file.
**Is selecting all text and copying enough?** It is a useful symptom check, not a substitute for the intended assistive reading workflow.
**Can I just rearrange the columns visually?** That may help sighted readers while leaving the tag order unchanged. Verify both layers.
Use product-spec extraction to approve factual inputs, then bring approved references to Panelly Studio for campaign visuals. This article addresses brochure reading order; it does not claim Panelly performs PDF remediation or integrates Opus.
