In this lesson you
- Ran a real PDF of your own through Proof's audit
- Fixed it in the real workbench, starting with the automatic pass
- Kept the fixed PDF and its verification record
Transcript
Your own file
Test Proof on your own PDF. Before you decide anything about accessibility, you'll want to see what Proof finds in a file you actually publish. Not a sample. A real PDF from your own website, the kind a screen reader user might open tomorrow. The public trial page is where you do that. It takes one PDF of up to ten pages, with no login, and one trial per email address. Your file stays private. It's never used to train AI models, and it's deleted automatically after thirty days. To start, drop your PDF on the page, or click to pick it from your computer. Here, it's a one-page park notice. Proof counts its pages first, so you know it fits. After that, say where to send your report. Proof emails you a link that unlocks it, so there's no password to make up. Then choose Run my free audit.
Your report
By the time this page opens, the audit is already done. Here, it found nine issues. It also says Proof can fix at least three of them on its own, and that the report shows how to resolve the rest. The report itself stays locked until you open the link in your email. This page unlocks by itself when you do. The link opens the full report. Its verdict reads Not Yet Compliant, and the counts underneath say why. Seven checks failed. Those are confirmed problems that would stop a screen reader user. Two more need review. Proof can't decide them alone, so a person has to look. Below that is every check Proof ran, grouped by topic, each with its result. It's the same report a customer sees, and the same checks behind a certificate.
The real workbench
A report tells you what's wrong. The trial also lets you fix it, in the same workbench customers use. Choose Fix this document. That's free too. The nine issues are now grouped into steps, by the kind of decision each one needs. The number on each step is how many issues wait there. Auto is Proof's automatic pass. Objects is pictures and tables. Reading is the order a screen reader follows. Visibility asks whether every reader can see the text. Certify comes last. Tags tell a screen reader what each part of the page is. This file has none yet, so the automatic pass has to come first. One click runs every automatic fix. Proof saves a new version and audits it again. When the pass is done, eight issues are fixed. That includes the two that needed review, which Proof could check once the file had tags. The one that's left is a judgment call. What does the photo show? Proof drafts an answer, and you check it. Here, the draft is accurate, so choose Use suggestion. Nothing changes until you choose Apply. Apply writes the description into a new version and audits it again. Now every picture has a description, and no step has anything left open. Whenever you like, choose Your report to go back. Every change you make shows up there.
What you take away
When nothing is left open, the report turns green, and it gives you two files to keep. Download remediated PDF gives you the fixed document. The verification record is the report as a PDF, with every check Proof ran. One thing the trial does not give you is a certificate. A certificate names a person in your organization who confirmed the checks no machine can judge. A trial has no such person on record, so it says Certification withheld. To certify this document, or to run Proof across your whole library, the page offers both next steps. Now you can test Proof on a real document of yours, see exactly what it fixes, and keep the result. To see your whole website at once, the free assessment has its own lesson.
Recap
That's the end of this lesson.
Maple Ridge Community Health, its documents and its people are fictional, made for these lessons.