Logical Reading Order – Needs manual check

Logical Reading Order – Needs manual check appears every time you run the Accessibility Checker in Adobe Acrobat Pro. It doesn't mean Acrobat found a problem. Acrobat can't judge whether the order of the document's tags, the hidden structure that screen readers follow, makes sense, so it asks a person to check. You resolve it by verifying the reading order yourself and correcting it where it's wrong.

What this means

A screen reader reads a tagged PDF in the order of its tags, from the top of the tag tree to the bottom, not in the order things appear on the page. Usually the two match. These layouts often break it:

• two or three columns, where the tags run across the columns instead of down each one;
• sidebars, pull quotes and callout boxes that interrupt the main text;
• captions separated from their figures, and footnotes read in the middle of a paragraph;
• form labels that are far from their fields in the tag tree;
• content added after the file was tagged, which often lands at the end of the tag tree.

Adobe's help says to make sure the reading order shown in the Tags panel matches the logical reading order of the document. Acrobat shows order in more than one place, which confuses many people. The Tags panel is what screen readers follow. The Reading Order tool and the Order panel show how content is grouped and numbered on each page, and they're useful for spotting problems, but the tag tree is the order that matters.

Why it matters

When the order is wrong, sentences are split in two, columns merge into nonsense, and a sidebar's contact details land in the middle of instructions. People who use screen readers, and people who use reflow or read-aloud tools, get a document that doesn't make sense. This is WCAG 2.1 success criterion 1.3.2, Meaningful Sequence. It's one of the most important checks in any document, and one that software can't fully settle.

How to fix it in Acrobat Pro

Fix it in the source file

Reading order problems are cheaper to prevent than to repair:

• Word: use real columns (Layout > Columns) instead of side-by-side text boxes, use styles for headings and lists, and set pictures to In Line with Text so they stay with their paragraph.
• PowerPoint: on Windows, open Review > Check Accessibility > Reading Order Pane and drag the slide title to the top of each list. On a Mac, use the Selection Pane (Home > Arrange > Selection Pane), which lists objects in reverse: the bottom item is read first.
• InDesign: set the order of stories in the Articles panel and turn on its option to use that order in tagged PDF (the option's label varies by version). Check the exported tags in Acrobat.

Fix it automatically with Includoc

Includoc sets a column-aware reading order when it fixes a file: the main text column by column, and sidebars and callouts after the text they relate to. Our AI pass then checks each page against the rendered layout, and we flag pages where the order looks out of sequence, such as a right-hand column read before the left.

What you confirm is the final order. On the review screen, each page shows its reading order as numbered blocks, and you can move anything with drag and drop or the keyboard. For documents with complex layouts, the human-verified tier includes a full screen reader pass.

Standards

Related errors

• Tab order – Failed: keyboard order follows the tag order, so fix the tags first.
• Content is tagged or artifacted: untagged content can't be in the reading order at all.

To learn how the tag tree works, read What is a tagged PDF?, or check a PDF free to see pages where the order looks out of sequence.