CampusMind Accessibility by Royal Cyber

Troubleshooting

Fixes for the common issues that come up during remediation and review.

Each entry below is a symptom, its cause, and the fix. Almost everything that goes wrong on a course run is a connection problem rather than a document problem — usually a source that isn't connected for your account, or an authorization that has expired.

The connector shows no files

Symptom — on the Upload page, your system's card reads Not connected, and the panel below it says Connect … to choose files instead of listing courses.

The Add files step with A connector selected and D2L Brightspace marked Not connected. The panel below reads Connect D2L Brightspace to choose files, with a Connect D2L Brightspace button
A connector you haven't connected asks you to sign in before it shows any files.

Cause — the source isn't connected for you.

Fix — choose the connect button in the panel, enter your institution's address for that system, and authorize CampusMind when the sign-in page appears. The authorization is tied to your own account, so a colleague being connected doesn't help you. See Connect a source.

A file failed with "Invalid access token"

Symptom — a file failed, and the failure reason quotes a Canvas or Blackboard error ending in something like {"message":"Invalid access token."}.

Cause — the access CampusMind was granted has expired or been revoked. It can still see the course listing but can no longer download the file.

Fix — on the Upload page, choose A connector and your system's card, and sign in again if it asks. Then choose Retry on the batch's row in the hub. If it fails again straight after reconnecting, the institution-level access set up at onboarding needs attention — contact Support.

The batch says Failed but there's still a file

Symptom — the batch is marked Failed and the document badge reads autotag failed, yet opening the document shows a remediated PDF beside the original.

Cause — the two are reported at different levels. A run can produce output and still be recorded as failed if a stage didn't complete.

Fix — compare the two panes before you decide. If the output is usable, carry on with it in the Tag & caption editor; if not, re-run that file.

The batch says Failed but most files finished

Symptom — a batch reads Failed, yet most of its files show a score.

Cause — one failed file is enough to mark the whole batch Failed. It's the normal outcome for a large course run where a handful of documents hit a problem.

Fix — open the batch and choose the Failed tab above its files. Only those rows need attention; the rest are ready to download.

Nothing happens when I add my file

Symptom — a document is rejected or ignored on the Upload page.

Cause — PDF is the only accepted format.

Fix — export from Word or PowerPoint to PDF first. Exporting usually carries some heading and list structure across, which gives remediation a better starting point than a flat scan.

I can't find a batch

Symptom — a batch you ran earlier isn't in the list.

The Accessibility Hub with a search box, status tabs for All, Completed, In progress and Failed, and Source, Engine, Fix method and Date filters above the batch list
The status tabs and the Source, Engine, Fix method and Date filters all narrow the list.

Cause — a status tab or filter is narrowing the list, or the batch hasn't been shared with you.

Fix — choose All, clear any filters, and search for the batch's name or ID. If it still doesn't appear, ask the person who ran it to share it with your group.

My colleague can't see my batch

Symptom — someone in your institution opens the hub and your batch isn't there.

Cause — access is scoped by group, not by role. A batch you upload is visible only to you unless you share it.

Fix — open the batch, choose Share, and add your colleague's group. See Share a batch.

A run seems stuck

Symptom — a batch sits at In progress with an unchanged percentage for a long time.

Cause — work is queued across the whole tenant, so a big course run ahead of yours delays everything behind it.

Fix — check the files in queue counter beside Batches on the hub for the tenant-wide backlog, and use Refresh list rather than reloading the page. For long batches, turn on Email me when it's done in the remediation settings instead of watching the screen.

The score is high and issues are still listed

Working as intended. The score is the share of 106 PDF/UA-1 rules that pass, so one unresolved rule on a long document barely moves the number — the list is the precise part.

Remaining issues names exactly what is left, which is what you take into the Tag & caption editor. Clear it, hit Revalidate, and the score follows. See FAQ and Accessibility standards.

Still stuck?

See FAQ for the questions that come up most, or Support to reach the CampusMind team.