Remediators · Lesson 6.2

Reading order, many documents

Walk the flagged pages of many documents, redraw what reads wrong, and save each document as one version.

3:15Captions and transcriptRecorded October 2026For people fixing documents

Watch the lesson

In this lesson you

  • Walked many documents' reading order, page by page
  • Saved each redrawn document as one version
  • Flagged what can't be fixed, and confirmed the AI-cleared

Transcript

Reading order across a library

Reading order, many documents. When dozens of documents need their reading order checked, how do you get through them without opening each one? This session lines them up and walks you through them in turn. Fixing one document from its own page is covered in Attesting reading order. The list on the left holds the documents still to go. Only check left means confirming this one makes the document Compliant.

Which pages you walk

Which pages do you look at? Not always all of them. Proof sends you to the pages its layout check flagged, and to any page the AI read as wrong. When nothing is flagged, you walk every page, so no document is recorded from its first page alone.

Reading a page

On each page, the numbered boxes show the order a screen reader follows. Where the line joining them jumps backward, it's orange. For a listener, that means hearing the end of something before its start. The pill above the page carries the AI's call. Here it reads Page 1, AI issue, and its reason. That's advice. Only your answer is recorded.

Two answers for every page

Every page gets one of two answers. It reads right, or you redraw it. If it reads right, press Enter to confirm the page. Where the AI flagged it, the button adds as-is, because you're overruling the AI. So read before you press. If it reads wrong, D starts Draw order, and C starts Reorder by clicking. S stages the suggested order, a starting point you still check. Then press Enter to stage the page. Staging keeps your order without saving it, and the walk moves on.

One save, one version

Why not save each page as you go? Because every save writes a new version of the file. So nothing is written while you walk. Once every page is confirmed or staged, the button reads Save 2 pages, attest. One press makes one version, and records your attestation. Then a message says Reading order verified, with Undo for eight seconds. Undo removes only your own record. The next document opens.

A page you can't fix here

What if redrawing can't fix a page, for example because its tags need rebuilding? Choose Flag issue, or press X, and say what's wrong. The note is saved in your name. A flag fails the check, because a person confirmed the problem. The document moves to Flagged as failing, and only you can clear your flag.

Why there's no batch attest here

Last, a difference from other sessions. They let you tick reviewed documents and attest them together. Reading order doesn't, because its attestation rests on the walk. The exception is AI-cleared. When the layout check and the AI both find every page right, you can confirm those documents together, in your name. One in ten stays in the walk as a Spot check. If you find a problem there, choose AI missed an issue. Now you can walk many documents page by page, save each one as a single version, and flag what can't be fixed here.

Recap

That's the end of this lesson.

Maple Ridge Community Health, its documents and its people are fictional, made for these lessons.

Try what you just watched.

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.