By Nilesh Gadekar, Founder · Last reviewed .
How to use this term in a district project
Review sequence in the actual exported document, especially where columns, sidebars, footnotes, or charts interrupt the visual layout. A page that looks straightforward can be presented in a different order to assistive technology. Source changes, merging, and new exports can affect the result, so the tested version matters.
A district example
A newsletter has two articles and a side note. The intended sequence should keep each article understandable rather than jumping between columns sentence by sentence.
A useful review question
Can someone follow the information without relying on its visual placement?
Continue with a practical guide
Explore the related DistrictProof guide or service, or return to the full accessibility glossary. Technical criteria and legal obligations should be checked against the applicable primary references and the agreed review scope.
Read the meaning, not just the page positions
Reading order is the sequence in which document content is presented to a person using assistive technology. In district documents, the intended sequence can be obscured by columns, sidebars, footnotes, repeated headers and attachments. A designer may place two related items beside each other while the exported document presents them far apart. The review task is to preserve the meaning when visual placement is unavailable. That makes reading order relevant to ordinary newsletters and notices as well as complicated board packets. It should be checked in the actual file intended for publication.
District example: a two-column school newsletter
Imagine a fictional school newsletter with a principal’s message in the left column and a field-trip notice in the right column. A reader should finish the principal’s paragraph before moving to unrelated field-trip instructions. A callout containing an application deadline should appear where it makes sense in its own article. If the exported sequence alternates lines from the two columns, both articles become difficult to understand. The reviewer can describe that exact problem and identify the intended sequence with the editor, instead of treating every item’s geometric position as the final reading instruction.
Plan the source and the export together
The content owner should identify the main story, related notes and any material that must remain together. Use a source layout that supports that sequence rather than relying on manually positioned text fragments. After export, review headings, paragraphs, lists, tables and meaningful images in context. Decorative items and repeated furniture need appropriate treatment so they do not interrupt the message. Where an image introduces an important qualification, its description should occur at the relevant point. Ask the author about uncertain relationships rather than allowing the repair process to invent a connection between separate pieces of information.
Check navigation as well as continuous reading
A reader may navigate directly to a heading, follow a link or move between form controls instead of reading from the first line. The review should include the tasks relevant to that document. In a packet, staff may need to locate an agenda item and then reach its attachment. In a form, the next control should follow an understandable question sequence. The record should state which tasks were checked and with which software. Distinguish the content’s reading sequence from the keyboard sequence through interactive elements while checking that both support the intended use.
Preserve the tested sequence through publication
Merging attachments, changing source columns or making a late replacement can affect the sequence. Keep the reviewed file version connected to its evidence entry and intended public URL. If the editor makes a substantive revision after review, treat it as a new version and decide what needs retesting. A useful procurement sample includes a real multi-column or assembled document so the quote accounts for this work. Ask whether final-file reading order is reviewed after assembly and whether correction handling covers a sequence problem found during acceptance. Those questions turn a vague promise into a practical publishing responsibility.