In this lesson you
- Read the gate before approving
- Knew what approving uses and unlocks
- Opened the certificate and its public verification page
Transcript
The last step
Certifying a document. Your document is fixed. What does it take to make that official, and what happens when you do? Certifying means a person with approval rights signs off on this exact file. Proof then issues a certificate for it. That happens in the Certify step, the last of four. Objects, Reading and Visibility each carry a green check. A green check means that step has nothing left for you.
Is it ready?
The Approve as accessible card is the gate. Proof offers it only when nothing is left to fix, and nothing is left to review. The words at the card's top right tell you where it stands. Here, they read Gate open. When the gate is closed, the same place says why. Blocked, open work above, means an earlier step still has work, and the card lists it. Re-checking accessibility means Proof is still checking your latest change. Wait for it, because the gate opens only on a fresh verdict.
What approving does
Before you approve, it helps to know what it commits you to. The line on the card says it. First, it locks this version of the file, so the certificate always describes exactly this file. Second, it uses one document from your balance. This is the only moment your balance is used. Third, it issues the certificate. It also unlocks the fixed file for download. A document is used once. If this one had already been used, the card would say No charge for this document. If your balance is empty, Proof stops and tells you to buy a document pack from Billing, then approve again.
Approve, or hand it in
Approving needs approval rights. An organization admin has them, and so does any member they allow to certify. Without them, this card reads Ready for approval. That button hands the document to an approver. An approver who'd like a second pair of eyes can hand it in the same way. Reviewing a colleague's work has its own lesson, Reviewing and approving. This one is ready, and we can approve it. Choose Approve & certify. Proof locks the version and issues the certificate. The card now reads Approved as accessible. At the top, the document is now marked Certified. To see what you just issued, choose View certificate on the card. It opens in a new tab.
The certificate
The certificate is an accessibility report for this exact file. Its verdict is WCAG 2.1 AA Compliant. Under the verdict, three columns say who stands behind what. Verified by Ockem Proof counts the automated checks, and which of the WCAG criteria that apply to this document they covered. No attestation required says no check here needed a person's confirmation. When one does, this column names your organization instead. Not claimed says what the certificate doesn't promise. It isn't a legal ruling, and it covers only this version of the file. Below that is every check, with its result for this document.
Anyone can verify it
At the bottom is a code anyone can scan, with the certificate's ID printed below it. It opens Proof's public verification page. Nobody needs an account to use it. The page confirms the certificate is genuine, and names the file and the version it covers. What a certificate promises, and how to check it, each have their own lesson.
Your balance
Back on Home, the Plan budget shows where your documents went. Certified counts the documents you've approved, including this one. Held counts documents set aside by work in progress. Available is what's left. Now you can tell when a document is ready, what approving commits you to, and where to find the certificate it creates.
Recap
That's the end of this lesson.
Maple Ridge Community Health, its documents and its people are fictional, made for these lessons.