Methodology

Methodology

Every report states the engine version, the file hash, the date and the profile used. This page explains what those checks can and cannot tell you.

Checks in the purchase-eligibility profile

Assessment checks and evidence type
CheckEvidenceMapped to
Document title present in metadataAutomated checkWCAG 2.4.2 (PDF18)
Title displayed instead of file nameAutomated checkWCAG 2.4.2 (PDF18)
Document language declaredAutomated checkWCAG 3.1.1 (PDF16)
Tagged structure presentAutomated checkWCAG 1.3.1 precondition (PDF/UA-1 requires tags)
Selectable text on pages (not image-only)Automated checkWCAG 1.1.1 / 1.4.5 suitability
Encryption and digital signatureAutomated checkSafety gate, not an accessibility criterion
Reading order, heading logic, alt text qualityNot evaluatedRequires human judgement

Finding statuses

A technical error or timeout makes the assessment incomplete. It is never reported as a pass. We do not show conformance percentages.

  • Passed automated check — the specific test passed. Not a statement about the whole criterion.
  • Failed automated check — the test found a defect.
  • Needs review — a person must decide.
  • Not checked — outside this profile or blocked.
  • Not applicable — the condition does not occur.

Use of AI

Where a broader audit record is available, some findings may include an AI-assisted hypothesis to help you prioritise review. These are labelled AI-assisted, cannot change a finding's classification, and do not affect price or eligibility. Document text is treated as data, never as instructions.

Standards are separate things

WCAG 2.2 is a set of success criteria for web content. PDF/UA (ISO 14289) defines technical requirements for accessible PDF files. Legal frameworks such as Section 508 or the ADA reference standards but are not standards themselves. Our report maps individual checks to individual criteria where the mapping is valid and does not claim full coverage of any of them.

Last updated 2026-10-01