How CampusMind works
What happens between an inaccessible PDF and a corrected, validated file.
In short
CampusMind rebuilds the structure an inaccessible PDF is missing, scores its own work against PDF/UA-1, and hands back the corrected file.
- Validated against
- PDF/UA-1 (ISO 14289-1) · 106 rules, checked by VeraPDF
- Automation resolves
- About 80% of common accessibility issues
- Always needs a person
- Alt text meaning, ambiguous layout, accountability
What's actually missing
An inaccessible PDF usually isn't missing its content — the words and images are there. What's missing is the tag tree: the machine-readable structure that says "this is a level-2 heading", "this is a data table with these headers", "this image means this".
Without it, a PDF is a picture of a document. A screen reader can often pull the text out, but it can't offer heading navigation, announce table cells with their headers, or describe a figure. Remediation is the work of rebuilding that structure.
Three words you'll see everywhere
| Term | What it means |
|---|---|
| Batch | One remediation run — a single file, or every PDF in a course. Everything on the hub is organized by batch, and each gets an ID like CM-1715 or Canvas-1711. |
| Source | Where a document came from: Canvas, Blackboard, Brightspace, SharePoint, or Local upload for anything you upload from your computer. |
| Group | The set of people a batch is shared with, and how access to its documents is controlled. See Set up your team. |
The pipeline
Every document takes the same seven steps.
Extraction
An extraction engine reads the page to find the paragraphs, headings, figures and tables. It returns candidates, each with a confidence score.
Confidence
How sure the engine has to be about what it read. Anything below the minimum confidence is flagged for manual review.
Fix method
Either a tag tree is written over the page as it stands, or the page is rebuilt. You choose this per batch.
Tagging
Elements become PDF tags —
P,H1–H6,Figure,Formula,Table,List,Link,Caption— in a reading order, the sequence a screen reader announces them in. Figures get generated alt text.Validation
VeraPDF checks the result against PDF/UA-1's 106 rules. The share that pass is the document's accessibility score.
Delivery
The corrected file is stored against its batch, ready to Download. The original is never changed.
Revision
Output lands as version
v1, attributed to System (autotag). Edits in the Tag & Caption Editor stack on top, and Revalidate re-runs step 5.
Checking the result
Validation runs against the original as well as the remediated file, which is what makes two before-and-after views possible:
- Comparison view — the two PDFs side by side, so you can confirm the page still looks right.
- Remediation report — original issues against remaining ones across four categories: document structure, headings and titles, tables and cells, and metadata and tagging. Each carries a severity.
A document can score highly and still have findings. Passing a rule set is not the same as being usable.
The two choices that change the output
Everything else has a sensible default. These two don't, because the right answer depends on the document. Upload & remediate covers where they live on screen.
Fix method
| Fix method | What it does | Reach for it when |
|---|---|---|
| Preserve Layout (Auto-tag only) | Writes a tag tree over the existing layout. Nothing visual changes. | The document must come back looking identical. |
| Full Remediation | Everything above, then rebuilds structure — table layouts, image descriptions, color contrast, layout corrections. | Tagging alone can't fix it. Page count may change as content reflows. |
These are a choice, not a quality setting: some problems can't be fixed without changing the page, and some documents must not change.
Note: Keeping what's already there
Keep existing tags updates a document's current tags instead of replacing them. Use it when a document was tagged by hand and you want corrections rather than a fresh start.
Extraction engine
General expert, the default, suits most documents and has no confidence setting. The other three engines each carry a Minimum confidence slider.
| Engine | Default minimum confidence |
|---|---|
| Formula expert | 50% |
| Text expert | 95% |
| Hybrid | 50% |
Raise it and more of what the engine read is flagged for manual review. Lower it and less is. Change it for a kind of document that keeps coming out wrong, not as a general setting.
Why a person is still required
- Meaning. Whether alt text conveys the purpose of an image is a judgment about the document's argument, not its pixels.
- Ambiguity. A sidebar might be an aside or the main point. The engine picks the likelier reading; only a reader knows which is right.
- Accountability. Your institution answers for its content. A high accessibility score is evidence of the work, not the final word on it.
Standards
- PDF/UA-1 (ISO 14289-1) — what remediated documents are validated against, and the number behind every score in the product.
- WCAG — the accessibility guidelines the PDF/UA-1 checks map to. The score itself comes from PDF/UA-1. In-product labeling reads WCAG 2.1; see Accessibility standards for how PDF/UA, WCAG, Section 508 and ADA Title II relate.
Next steps
- Quickstart — put this to work on a real document.
- Upload & remediate — the settings in practice.
- Trust & compliance — the obligations behind the product.