Check a course before you accept it

One of nine use cases for the Clarity Box, Windows desktop software for learning teams from Clarity Writers.

Go back to the vendor with specific findings, each tied to a screen and a quote from the course.

The final build landed this morning, with an invoice due at the end of the month. Clicking through it in a test account catches some problems, but alt text and keyboard use are hard to see that way. And telling a vendor "the writing feels off" tends to earn a reply just as vague.

What you need

Only the SCORM zip the vendor was going to deliver. Load it on its own from the side menu, or add it to a module on a project board. Reading the package costs nothing, and scoring waits until you press Start review.

What it checks

• Writing quality. Plain language at a reading age of about 12, proofreading, and New Zealand and Australian spelling.
• Accessibility. Alt text, link text, colour contrast and keyboard use, measured against WCAG 2.1 AA by default.
• Interactivity. Empty elements, and quizzes that give the answer away.
• Media and assets. Images, audio and video, weighed against the text.

If your policies are in Clarity Bank, a review started from a module also names the bank page where the course contradicts them. It says nothing about topics the bank doesn't cover.

What you send back

Each finding gives its impact, the screen, a quote and a suggested fix. Download report turns them into a Word document you can forward. Screens the review left out are listed with the reason, so you can see what wasn't checked.

When the fixed version arrives, use Replace SCORM and score it again. Keep the first report, because a module only shows its latest run.

Where the content goes

Scoring sends the course's learner text, your governance documents and any references you leave on to your organisation's AI provider, on your own account. Clarity Writers sees none of it. Check the confidentiality clause in your vendor contract first.

What stays with you

A poor grade is evidence for a conversation, and the contract is still what you hold the vendor to. Your brief may have agreed a higher reading age, which Clarity Review can't know. Reading is tuned for Chameleon, Storyline and Rise, and other tools get less detail.

Tell the vendor at briefing what you'll check against, and the argument about standards is settled before the build begins.

A vendor course on your desk is the best way to see this. Book a demo.