Upload & remediate
Send documents into the remediation pipeline and choose how they're processed.
Add your files, choose a fix method, run it. Every other setting has a working default, so a first run needs only those two decisions.
Add your files
On the Accessibility Hub, choose Upload. The Upload page has three numbered steps.

- Add files. Keep This computer selected, then drag PDFs onto the drop zone or choose Browse files. PDF is the only accepted format. For documents in an LMS or SharePoint, choose A connector instead. See Connect a source.
- Choose how this batch runs. Audit + Remediate, the default, scores and fixes every file in one run. Audit scores every file, then pauses so you can review the results and choose which files to fix.
- Name and share (optional). Choose Show options to name the batch and pick a group under Share with. Without a name, the batch keeps its ID. Without a group, only you can see it. You can share it later too.
Choose Continue to remediation settings.
Choose a fix method
The fix method is the one setting that changes what you get back, and it applies to every file in the batch.

| Aspect | Preserve Layout (Auto-tag only) | Full Remediation (Full accessibility reconstruction) |
|---|---|---|
| Best for | Print-ready or well-formatted documents whose layout must stay the same | Scanned documents, textbooks, lecture notes and complex academic content |
| You get | Tag structure, screen reader reading order, heading hierarchy, structured lists and tables | All of that, plus table structure and table headings, descriptions for images and diagrams, color contrast and layout fixes, and descriptions for math, chemistry and medical content |
| Changes the page? | No | Yes, page count included, as content reflows |
Choose an extraction engine
The engine reads your files before anything is tagged. General expert is selected by default and suits most documents.

| The document is | Choose | Why |
|---|---|---|
| Most documents, and especially scanned pages or large, complex tables | General expert (default) | It reads each page's layout before tagging, recovers tables inside images, and writes alt text for figures |
| Scientific, mathematical or engineering material, heavy on equations and tables | Formula expert | It detects formulas as elements in their own right |
| Descriptive and text-heavy | Text expert | It's the better classifier of headings, lists, paragraphs and text hierarchy. It has no formula detection |
| Both, such as research papers and technical reports | Hybrid | Formula expert handles formulas and tables; Text expert handles headings, lists and paragraphs |
Minimum confidence
Formula expert, Text expert and Hybrid each show a Minimum confidence slider from 50% to 100%. Text the engine reads below this confidence is flagged for manual review, so a higher setting flags more text.
| Engine | Default |
|---|---|
| Formula expert | 50% |
| Text expert | 95% |
| Hybrid | 50% |
Leave the default unless one kind of document keeps coming out wrong.
Tags and notifications
Both toggles are off by default.
| Toggle | What it does |
|---|---|
| Keep existing tags | Off rebuilds and replaces a document's tags. On keeps them and updates only the ones that need it. Use it for documents someone tagged by hand |
| Email me when it's done | Sends an email when remediation finishes. Worth it on a large batch, which won't finish while you wait |
The bar at the bottom shows the file count and an Estimated time. Choose Run remediation to start, or Back to files to change what's in the batch.
Track progress
You return to the hub, where the new batch appears at the top of the list.
| Status | Meaning |
|---|---|
| In progress | Queued or running. The progress bar fills as files finish |
| Completed | Every file finished |
| Failed | At least one file failed. Open the batch to see which ones |
Refresh list updates statuses without reloading the page. The files in queue counter beside Batches counts work queued across your whole institution, which is why a run can wait before it starts.
When a file fails
Failures are reported per file, with the reason on the file's row. On a course run the usual cause is an expired LMS authorization. Reconnect the source, then choose Retry on the batch's row in the hub. See Troubleshooting.
Next steps
- Manage batches — open a batch, check each file, share and download the results.
- Tag & caption editor — correct the output, then revalidate and approve it.
- How CampusMind works — what happens in between.