AccessibilityPDF — Martin Schrammel AB

Standards and labels

Does a green check mean a PDF is accessible?

No. The result covers the rules the tool actually checked. The meaning of the content also needs review.

Applies to
Interpreting validation reports and accessibility claims
Sources checked
Language

Read the scope of the result

Automated checks can quickly find many structural problems. They cannot independently settle every question requiring an understanding of the document’s meaning. Read a pass result alongside the profile, version and scope of the checks.

Certified and fully accessible are stronger claims than a single validation result. Do not use them as synonyms for a green indicator.

Read the report before reading the colour

Start with the report’s summary. Which file was assessed? Which tool and profile were used? Did the run finish? An absent report or software failure does not mean there are no document defects.

Inspect a real finding next. If a Figure lacks an alternative description, first identify the image it represents. A chart needs an accurate description of its message. A purely decorative line may instead need to be treated as decoration. The same technical warning can therefore lead to different repairs.

Rerun the check afterwards, but also return to the image. The description needs to be correct, attached to the right object and coherent with surrounding text. Filling an empty field with “image” may change a report’s colour without resolving the reader’s problem.

Build an assessment record

PartWhat it contributes
Automated checkRepeatable assessment of the rules the tool supports.
Content reviewJudgement about descriptions, sequence and meaning, among other things.
Practical assistive technology testObservation of whether document tasks can be completed.
DecisionA responsible person weighs the evidence against the agreed requirements.
This table scrolls horizontally.

An example of what the measurement establishes

In our synthetic before-and-after example, veraPDF reported 55 failed checks before processing and none afterwards. That supports a precise claim about the tested machine rules and those two files. It does not establish that someone read the document using NVDA; no such run is part of that example.

A useful claim is still possible: identify the files, profile, tool version and changes. Add the manual and practical checks actually performed. Where a check is missing, record the remaining work. The buyer can then make an informed decision without guessing what “approved” means.

A supplier using the term certification should explain who issues it, which requirements were assessed and how. Certification is not a technical property created by saving a PDF. An internal delivery approval is another distinct thing: the organisation’s decision based on the available evidence.

Say what you actually know

Example A delivery statement

Before

The PDF is automatically certified against every accessibility requirement.

After

The file passed the specified PDF/UA profile’s automated checks. Manual and practical results are reported separately, including remaining issues.

Why this works Readers can see both the strengths and limits of the evidence. An AI assessment can contribute, but confident wording does not make it a human decision.

Results must follow the correct file

Record a file checksum, such as SHA-256. If someone edits the PDF after assessment, repeat the affected checks. An unchanged filename does not prove unchanged content.

Sources

  1. veraPDF validation documentationveraPDF
  2. PDF Accessibility Checker (PAC)PAC
  3. Web Content Accessibility Guidelines (WCAG) 2.2W3C

Examples are our own unless stated otherwise. These guides distinguish legal requirements, standards and practical advice. Passing an automated check is not a complete assessment of document accessibility.

All guides

Need help with your PDFs?

The service is in development. Sign up for an email when we open. You can read the full knowledge library in the meantime.

Get a launch notice