What changed in Proof, and what it lets us say.

Only work that is live for customers is listed here. Each update names the claim it earns, so the marketing never runs ahead of the product.

October 2026

Updated

Changes through October 8: every WCAG criterion that applies to a PDF now evaluated, team workflow for multi-seat plans, stricter rules on what an automatic fix may change, less for a reviewer to do, and Proof on a phone. Everything below is live today.

  1. Every WCAG criterion that applies is now evaluated

    Proof evaluates every WCAG 2.1 A/AA criterion that applies to a document, by machine check or recorded attestation.

    Of the 50 WCAG 2.1 Level A and AA criteria, 39 can apply to a PDF, and Proof now has a check for every one. The new checks cover use of color; how a form behaves (on focus and on input, error messages, submission, labels in names, input purpose); what scripts do (content on hover, motion, status messages); and embedded audio and video (captions, audio description, audio control). Non-text contrast now covers chart keys and charts, and keyboard access and focus visibility are evaluated on documents with links.

    Where the thing a check looks for is absent — no chart, no submit button, no custom script — the check passes and says why, so a person is asked only about documents that have it.

    When every criterion that applies to a document was evaluated, its certificate says so: “every one of the M WCAG 2.1 Level A/AA criteria that apply to this document (M of M)”, with M the number that apply. Certificates issued earlier keep their “N of the M”.

    When a criterion applies and was not evaluated, the certificate now names it, by number and name, in its “Not claimed” section, and the public verification page says the same. Certificates issued earlier add the names the next time their holder opens or downloads them in Ockem Proof.

    WCAG coverage map
  2. Assign work, hand it in, approve it

    Assign documents to people, and get finished work back for approval.

    Administrators assign documents with a due date and a hand-off note, and can mention a teammate. Routing rules send newly imported documents to a person by folder, tag or language, and assigned work leads each member’s feed.

    Finished work is handed in for approval. An approver — who needn’t be an administrator — approves it or sends it back with a reason. Follow a document or a whole folder to get one daily digest of what changed. When someone leaves, their open work is handed on instead of orphaned.

    Webhooks carry the new events too: assigned, ready for approval, sent back, import finished and remediation finished. An endpoint that keeps failing is switched off and your administrators are told.

    Team workflow comes with multi-seat plans, which we set up with you.

    Workflows
  3. A fix that would lose words is refused

    Proof refuses any automatic fix that would remove or hide text the document already had.

    Every automatic fix is now checked against the version before it. If a fix would delete text, hide it from a screen reader, or — for a structural fix — change what is painted on the page, Proof refuses it and the run carries on from the earlier version.

    A new version after approval withdraws the certificate until a fresh check issues a new one. A rule Proof could not evaluate is listed as a manual review and counted on the certificate, never dropped.

    Two checks got stricter: a list or data table tagged as plain paragraphs no longer passes, and neither does a link tagged around the wrong words.

    Oversized images are re-encoded to shrink the delivered file only after you say yes, because that changes the file you publish.

    WCAG coverage map
  4. Less for a person to do

    Approved alt text follows the image, and text hidden from screen readers is restored automatically.

    Describe an image once. Wherever the same image appears in your other documents, Proof offers your approved description as a draft to review.

    Silenced text is a new check: sentences printed on the page but marked as decoration, so no screen reader announces them. A remediation restores the readable passages automatically and lists the rest for a person to decide.

    When a document has no usable title, Proof drafts one from page 1 for you to accept. And for many form documents, Focus Visible is now decided inside Proof instead of by a tab-through in Acrobat.

    AI assistance
  5. Contrast and reading order, decided on the page

    Every color pick shows your brand colors, and reading order is drawn directly on the page.

    Set your organization’s brand colors once. Every color pick then offers them beside the replacements you chose before, each checked for contrast. A color change is never applied without a person.

    On scanned pages, contrast is measured from the page image itself, and you are asked only where it falls short.

    Reading order is numbered block by block. Draw the order directly on the page, Shift-drag to draw a table, and screen-reader users are pointed to the keyboard method.

    Reading order
  6. Proof on a phone or tablet

    Review and decide from a phone or tablet. Proof’s main pages reflow at 320 pixels wide.

    The Library, the review queues and each document’s Steps and Page tabs work on a phone and a tablet: answer a picture, a title or a language question, approve and certify on a small screen. Drawing tools ask for a larger one.

    Proof’s main pages reflow at 320 pixels wide with no sideways scrolling (WCAG 1.4.10 Reflow). The PDF page itself and wide tables scroll inside their own frame.

    Every document now opens in the Steps view, which groups what is left by the decision you make, not by the rule that reported it. From Home, find any document across every project you can open; each project has its own address to bookmark and share.

    Platform, security & trust
  7. Help when Proof can’t finish, and fewer surprises

    On a document Proof couldn’t finish, ask Ockem to do it and get a price in documents.

    “Have Ockem do this” sits on any document Proof couldn’t process or that was escalated. Our team prices the work in documents, and an administrator accepts or declines it in Proof.

    Complex-file prices can be accepted several at once, or skipped. Administrators are emailed when a price is ready and before it expires, when the document balance runs low, and again at zero.

    Each document shows its turnaround: ordinary documents are usually done within the hour, while scans and long files run in the background, typically the same day, without holding the rest up.

    Every Proof email has one-click unsubscribe, and administrators choose the notifications new teammates start with. From any document, you can tell us when a fix didn’t work.

    Pricing

September 2026

Updated

Two weeks of changes to how a certificate is made, what it is allowed to say, and how a whole library gets remediated. Everything below is live today.

  1. The certificate is now a two-party record

    Every certificate records what was checked by machine and what your organization attested, and says what it does not claim.

    A certificate now carries a summary in three parts: what the machine checked, what your organization attested, and what is not claimed. The certificate names your organization as the attesting party and keeps the attester’s identity on file — and prints their name too, if your organization chooses. Before attesting, a person accepts an Attestation Statement, and the certificate cites it.

    “In force” means compliant. If a document is reset, the certificate that reset un-approves is withdrawn — a certificate never outlives the approval behind it.

    Automatic certificate issuance is opt-in per organization, and a certificate records when it was used. An auto-issued certificate is never described as reviewer-verified.

    The compliance claim
  2. If Proof did not test it, the certificate says so

    Proof never certifies what it did not check.

    A rule the pipeline could not evaluate now counts as pending, never “not applicable”. A page the audit never read cannot be certified. Where coverage has a gap, it reaches a person as a review item instead of disappearing.

    Reading order and color contrast are certified only on evidence the audit actually had.

    WCAG coverage map
  3. Remediations report their phase, progress and time left

    Start a remediation across your whole library and watch it report phase by phase.

    A running remediation shows which phase it is in, how far along it is, and an estimate of the time left. When it finishes, the report says what the run cleared.

    Several remediations running at once share your organization’s capacity fairly, and drafting image descriptions no longer holds up fixing — the AI work runs in its own lane beside the fixers.

    Batch remediation programs
  4. Projects and sign-in through your own identity provider

    Bring your agencies under one contract. Each agency gets its own project, its own people, and sign-in through your identity provider.

    Projects work as a portfolio: one contract, one project per agency, each with its own people and its own library. A Home page shows what is running now, with the same status summary as the assessment report. Each browser tab stays in the workspace named in its address, and you choose that name.

    On team plans, single sign-on runs through your own identity provider using OIDC. Rules you set place each person who signs in into the right team and project; multi-factor authentication done at your provider is accepted; those sign-ins last 12 hours. Access is granted per project at read, work or admin.

    Platform, security & trust
  5. What a reviewer does, simplified

    Every check Proof asks a person to make points at the exact spot on the page.

    Pictures: one picture is one question. The AI-drafted short alt text and the extended description sit in one place, beside the crop. A picture that is really text can be answered “It’s text”, and Proof transcribes it. The same image gets the same alt text everywhere it appears in your library.

    Forms: field names are checked for whether they actually identify the field. Names come from the printed label; AI drafts one only where the page prints nothing. Focus order walks the fields exactly as a screen-reader user tabs through them.

    Scans: an unreadable text layer is recovered by reading the page. OCR follows the document’s declared language across 37 language packs, 31 of them recognized automatically when nothing is declared.

    Language of parts and non-text contrast now come with located evidence, which closes the work of pointing every check at the page.

    Feature catalog

See it on one of your own PDFs.

Free, no account: one PDF of up to 10 pages and 50 MB per verified email, remediated file and verification record included. Certify it for $59 when you’re ready.