remediation packet

Preflight a PDF for Remediation Before You Publish It — Free

Paste what was done to the document, and see which remediation steps are still open before the file is published.

The proof surface

Exporting from a word processor produces a tagged file in name only; the steps a screen reader depends on are the ones to confirm before publishing.

Inputthe remediation actions actually taken on the file

Rare devicechecks the reader's own remediation notes against the steps a screen reader depends on, rather than describing accessible PDFs

Output artifacta packet cover of steps marked present or open, with the tag-tree note

Cost$0 · local-first · one free run · samples labelled

Sample, not your facts: Sample: 12 of 14 images given alt text, reading order fixed on pages 1–6, form fields unlabelled, 40 pages, 6 hours available — four concrete points across four types.

Why the flat version breaks

Trusting the export

Word and Google Docs produce tags that frequently break reading order in two-column layouts, which is invisible in a visual check.

Alt text as an afterthought

Missing alt text on charts and logos is the most common open step and the easiest to close before publishing.

Unlabelled form fields

A form that looks complete visually is unusable with a screen reader when fields carry no label, and the fix is minutes not days.

How to work the remediation packet

List what was done

One remediation action per line, in your own words.

Give pages and hours

Pages set the scale; your available hours decide what can realistically close.

Read the cover

Present steps carry the stamped tick; open steps carry the exclamation box and are counted on the index line.

Re-export and re-run

Fix, re-export, then re-run the preflight on the final file and keep the record with the version.

What the preflight replaces

Question	Before	On the cover
Is the file accessible	assume export handled it	each dependent step marked present or open
What is left	recheck the whole document	open count on the index line
What to publish	'it's probably fine'	publish after the open steps are closed

The checklist is structural; a passed preflight is not conformance, and a screen-reader test remains the final check.

Run it on the samples, right here

FIRST-LOAD

Data note: Everything runs in this browser tab on the remediation packet: your remediation notes stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.

Go deeper: the companion app files the same reading as a stapled evidence packet

The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the ready-to-mail packet, and holds your drafts on this device — one free run, then $ 9 one-time for the layer that keeps filing.

The preflight and the open steps are free. The paid layer prints the remediation record and keeps it with the file version.

Open the remediation packet companion

Boundary

This remediation packet works only on the remediation notes you paste you paste. It does not certify accessibility, does not edit the PDF, and does not replace a screen-reader test. The figures describe what you supplied, not what is true in the world. Confirm anything you plan to act on with an accessibility specialist, and one screen-reader user, before publishing a public document before you rely on it.

What this is built on

Every figure comes from the remediation notes you paste you paste; nothing is looked up, scraped or asserted as verified.
Method: each step is matched against the words you pasted; presence is reported, not conformance
Sample values are labelled samples — illustrative by design, not your data and not a quotation of any organisation's policy.

Before: the reader assumed exporting from Word produced an accessible file. After: they can see tag structure and reading order still open.