Method

Multi-column PDF reading order: sidebars, footnotes, tables and complex layouts

A pattern gallery for newsletters, annual reports, budget books and agenda packets: ten layouts, what a screen reader user often hears, the order that works, and how to tag it.

Multi-column PDF reading order: sidebars, footnotes, tables and complex layouts
The short answerIn a multi-column PDF, a screen reader should read down the first column and then the next, with headlines first and sidebars, captions and footnotes placed at a sensible break, never mid-sentence. Running headers, footers, page numbers and pull quotes that repeat body text are usually marked as artifacts so they are not read. Tables read row by row with their header cells marked. Where more than one order makes sense, such as a sidebar before or after the story, WCAG lets the author choose, so a person makes that call.

Multi-column PDF reading order is where accessibility problems hide in newsletters, annual reports, budget books, brochures and agenda packets. A screen reader follows the tags, the hidden structure that tells assistive technology what each part of the page is and in what order to read it. On a designed page, those tags often follow the order in which things were placed rather than the order a person reads them, so columns interleave and sidebars cut sentences in half. This guide is a pattern gallery: ten common layouts, what a screen reader user often hears, the order that works, and how to tag it. Where more than one order is reasonable, it gives a sensible default and says the call is yours. For tag order, content order and Acrobat's manual check, start with logical reading order in PDFs.

Why multi-column PDFs read out of order

When a PDF is tagged, by the program that exported it or by an auto-tagger, software infers the order from where things sit on the page. A one-column memo usually comes out fine. A designed page often does not.

  • Content often sits in the order a designer created it, so a pull quote added last can land anywhere.
  • Text boxes and floating images sit apart from the story they belong to.
  • Tagging that reads across the page can follow a line in column one with the line beside it in column two.
  • Paragraphs split across columns or pages, so reading halts mid-paragraph, a problem the University of Illinois Springfield's accessibility guide calls out.

These errors land hardest on screen reader users, and also affect people who read in Reflow view or with magnification.

Ten layouts and the order a screen reader should follow

Tag names below are standard PDF tags. Art is short for article, a self-contained story. It is not the same thing as an artifact, which is content marked as decoration so screen readers skip it.

LayoutWhat a screen reader user often hearsThe right orderHow to tag it
Two- and three-column textLines alternating between columns, or column two firstHeadline, then down column one, then column twoOne Art or Sect per story, paragraphs in column order, split paragraphs joined
Sidebars and callout boxesBox text dropped into the middle of a sentenceThe story, with the box read whole at a paragraph break or at the endSect around the box's heading and text (Aside in PDF 2.0)
Pull quotesThe same sentence twice, the first time out of contextRead once, where it appears in the storyArtifact, when it repeats body text word for word
Figures, captions and chart notesA caption read far from its image, or chart labels as loose wordsFigure and caption together, near the text that mentions themFigure with alt text, Caption tag right beside it
Footnotes and endnotesA note read at a random point, or a stray "3" mid-sentenceEach note after the paragraph that cites it; endnotes at the endReference for the marker, Note for the note
Running headers, footers and page numbers"Annual Report 2026, page 14" on every page, sometimes mid-sentenceNot readArtifacts
TablesNumbers with no labels, or columns read top to bottomRow by row, left to right, header cells markedTable, TR, TH and TD in page order
FormsA label read after its field, or Tab reaching fields out of orderLabel and instructions, then the fieldField tagged after its label, tooltip as name, tab order from structure
Stories continued on a later pageThe story stops mid-sentence and the next one startsThe whole story, then the nextContinuation placed right after the first part in the tag tree
Side-by-side languagesEnglish and Spanish alternating, Spanish read with English pronunciationOne complete language version, then the otherEach version in its own Sect with its language set

How to tag columns, sidebars, pull quotes and continued stories

Two- and three-column text

W3C's guidance on criterion 1.3.2 describes the natural order of a multi-column page: top to bottom of one column, then the top of the next. A headline that spans the columns comes first. When a paragraph breaks at the bottom of a column, the tags should carry the reader straight into the rest of it. Acrobat's Reflow view (View, Zoom, Reflow) makes interleaved lines easy to spot.

W3C's own example for 1.3.2 is a magazine article with callout sidebars, and it says: "The order of the article and the sidebars does not affect their meaning." So the position is the author's call. A sensible default is right after the paragraph the sidebar relates to, or at the end of the story if it stands alone, and never mid-sentence. Group the box's heading and text in one container so it is read as a unit, and give its heading a level below the story's. PDF 2.0 added an Aside tag for sidebars. A PDF 1.7 file has no Aside, so use a Sect.

Pull quotes

A pull quote repeats a line from the story in large type, so a screen reader user hears it twice, the first time out of context. If it repeats body text word for word, mark it as an artifact. If it contains words that appear nowhere else, such as a resident's quote missing from the story, it is content: tag it as a paragraph and place it at a break, like a sidebar.

Stories that jump to a later page

Newsletters often run "continued on page 4." The tag tree does not have to follow the pages. Put the continuation directly after the first part, inside the same story container, so the story reads straight through. The jump lines can then be marked as artifacts or left as text to match the print layout. Either is defensible.

Where captions, footnotes and page numbers belong

Figures, captions and charts

A caption belongs right next to its figure, before or after it, so the description and the caption are heard together. Keep the Caption tag beside the Figure tag rather than inside it, because Adobe notes that alt text on a parent tag stops a screen reader from reading that tag's children. If you use the Reading Order tool's Figure/Caption option, which tags both as one unit, check the result. For a chart, the alt text covers the chart and the labels drawn inside it, and a source line or side note set as real text follows the chart. Our guide to alt text for charts, maps and diagrams covers the description itself.

On a cover, read the title, subtitle, organization and date first, and mark a purely decorative background photo as an artifact. Text over a photo can also fail color contrast.

Footnotes and endnotes

Tag the superscript marker in the text as a Reference and the footnote itself as a Note. Where the Note goes is a judgment call. The University of Illinois Springfield's guide says there is no settled standard, and its own remediation team places notes after the paragraph that cites them. That is a good default, because the listener hears the note while the sentence is still fresh. Endnotes can stay at the end, with each marker linked to its note.

Running headers, footers and page numbers

Running headers, footers and page numbers repeat on every page, so they should be artifacts. W3C's technique PDF4 lists header and footer information, separator lines and decorative images as typical artifacts, and PDF14 describes Word exporting headers and footers as pagination artifacts. Artifact only what is repeated or decorative. A footer that says something found nowhere else, such as a "Draft, not adopted" notice on a budget book, should be read once, so tag it as text on the first page.

Reading order in tables, forms and bilingual layouts

Tables

A screen reader reads a table row by row, left to right, and can announce the matching headers as a user moves from cell to cell, but only if the table is tagged as a table. A budget table exported as loose paragraphs reads as a stream of numbers. W3C's technique PDF6 expects table rows (TR) holding header cells (TH) and data cells (TD), in the proper order. Multi-row headers need someone who knows which labels apply to which numbers. A table used only for layout should not be tagged as a data table. For depth, see the tables rule.

Forms

On a permit application or patient intake form, each label and its instructions should be read just before the field they describe, and the Tab key should reach fields in the same order. Set the tab order to Use Document Structure so it follows the tags. W3C's technique PDF10 treats a field's tooltip as its label. Our guide to accessible PDF forms covers the rest.

Side-by-side languages

Bilingual notices often set English and Spanish side by side. Read one complete language version, then the other, rather than alternating paragraph by paragraph. The exception is a bilingual form that pairs each label with its translation, where label-by-label pairs make sense. Put each version in its own container and set its language, so the screen reader switches pronunciation. That is WCAG 3.1.2 Language of Parts, and W3C's technique PDF19 shows how to set it in Acrobat's Tags panel. For scanned pages in right-to-left scripts such as Arabic or Hebrew, plan on a person checking the reading order after OCR.

Set the order once in your template

Most complex layouts come from templates that repeat, such as the monthly newsletter or the annual report. Fixing one export in Acrobat helps one file. Fixing the template helps every future issue.

  • In InDesign, add page items to the Articles panel in reading order, choose Use for Tagging Order in Tagged PDF, and export with Create Tagged PDF turned on.
  • In Word, keep sidebars and callouts in the main text at the point they should be read, not in floating text boxes, and use the built-in heading styles.
  • Mark decorative images and rules as decorative in the source wherever your tool allows it.

How Ockem Proof handles complex layouts

Ockem Proof, our product, does the structural repair and puts the judgment calls in front of a person.

Drawing the reading order on a two-column page in Ockem ProofA newsletter page with a headline, two columns of text and a small table. At first the numbers on each block show the order as tagged, which reads straight across both columns: headline 1, then left column 2, right column 3, left column 4, and so on. In draw mode a reviewer draws one line down the left column, up through the gutter and down the right column, and each block takes the next number as the pen first reaches it: headline 1, left column 2 to 5, right column 6 and 7. Holding Shift and dragging a box across the table makes it 8, read row by row. The panel beside the page lists the three ways to set the order: draw down each column, tap to add one block, Shift-drag across a table. It ends with all 8 blocks placed.Reading orderPage 3 of 12Draw mode1122436485365778Set the order1 Draw down each column2 Tap to add one block3 Shift-drag across a tableFlagged for reviewOrder reads across columns8 of 8 blocks placedSave and mark reviewed
In Ockem Proof’s draw mode, one line drawn down each column sets the reading order, and a Shift-drag reads a table row by row. A person draws it, then saves and marks the page reviewed.
  • Repairs in place. Proof rebuilds broken structure in place and keeps what is already correct, such as figures, tables, links and lists. A document with no tags goes through tagging first, so fixers never report progress they did not make.
  • Checks its own work. Any automated change that does not measurably improve the document is discarded. A fix that would remove or hide text the document already had, or a structural fix that would change what is painted on the page, is refused, and the run carries on from the earlier version.
  • Holds structure to a stricter bar. A list or data table tagged as plain paragraphs does not pass, and neither does a link tagged around the wrong words. Proof shows exactly where.
  • Shows the order on the page. Proof compares each page's visual order with its tag order. Flagged pages get a numbered overlay that shows the exact order assistive technology will follow, block by block. To change it, you draw the order directly on the page, and Shift-drag to draw a table. Screen reader users are pointed to a keyboard method.
  • Leaves content calls to people. Second-language passages are surfaced with their locations for a person to confirm, and ambiguous tables go to a table editor instead of being guessed.
  • Says when it cannot finish. A document exported with no repairable structure gets a "needs re-authoring" advisory with the reason. On a document Proof couldn't finish, "Have Ockem do this" asks our experts for a price in documents, which you accept or decline in Proof.

Whether the sidebar comes before or after the story is still your decision. A person confirms the final order, and that confirmation is recorded on the certificate as your organization's attestation. The reading order rule has the details.

Next steps

You can try one PDF (opens an external site) of up to 10 pages free, with no account. To size your library first, use the free PDF inventory tool. For how each check is handled, see the reading order rule and the tables rule. Related guides: logical reading order in PDFs, which checks software can fix and accessible PDF forms.

How many PDFs are on your site?Count them free. We keep a sample for 30 days and full imports for 90.
Count my PDFs

Questions

How should a screen reader read a two-column PDF?

Down the first column, then the second, with any headline that spans both columns read first. A paragraph that breaks at the bottom of a column should continue straight into the top of the next one.

Where should a sidebar go in the reading order of a PDF?

WCAG treats the position as the author's choice, because a sidebar's place usually does not change its meaning. A sensible default is right after the paragraph it relates to, or at the end of the story, and never in the middle of a sentence.

How do you tag footnotes in an accessible PDF?

Tag the superscript marker as a Reference and the footnote text as a Note. There is no settled standard for where notes go, and placing each note right after the paragraph that cites it is a common, listener-friendly choice.

Should pull quotes be read by screen readers?

If a pull quote repeats text from the story word for word, it is usually marked as an artifact so it is not read twice. If it contains words found nowhere else, tag it as content and place it at a paragraph break.

Should headers, footers and page numbers be tagged in a PDF?

In most documents they are marked as artifacts, which screen readers skip, because they repeat on every page. Tag a footer as content only when it carries information found nowhere else in the document.

This guide explains the rules in plain language. It isn’t legal advice. Check how they apply to your organization with counsel.

Ockem team

We build Ockem Proof, which finds, fixes and certifies PDFs against WCAG 2.1 AA. We check every figure in our guides against our measured product data and the primary sources listed below.

Sources

Start with one PDF.

Free, no account: a verified email, one document per email, up to 10 pages and 50 MB. Get the remediated file and its verification record, and see which checks still need a person.

Longer document? Request an assessment.

Back to Guides