This inspector reads any PDF in your browser. There is no upload. We have no server-side record of which files you inspect. The inspection is entirely a conversation between the file and your browser.
Drop a PDF below. The inspector will read its tagged structure tree, its XMP metadata packet, and the AI-governance provenance record if one is embedded. It will then classify the file into one of three tiers — MX Compatible, EAA tagged only, or plain — and surface what each tier means in plain language. You can download the inspection results as a machine-readable JSON, a human-readable markdown report, or (when present) the embedded AI provenance record lifted out for offline analysis.
For the conceptual background — what each of these artefacts is, why they matter under the European Accessibility Act and the EU AI Act, and how to verify any claim with three command-line tools — read the explainer: MX for PDFs. The inspector is the interactive companion; the explainer is the walk-through.
Drop the file
What the inspector checks
Four artefacts, in order of evidence weight.
Tagged structure (ISO 14289-1)
An MX Compatible PDF declares pdfuaid:Part=1 in its XMP metadata packet, indicating Level 2 PDF/UA conformance to ISO 14289-1. The inspector reads the XMP packet and reports the declared Part. The tagged structure tree itself (the /StructTreeRoot in the PDF's catalog) is what lets a screen reader walk the document the way a sighted reader does, and what European Accessibility Act Directive 2019/882 expects for documents published from 28 June 2025 onwards.
MX XMP namespace
An MX Compatible PDF carries a packet of MX-namespaced metadata in its XMP stream: status, content type, canonical URL, source repository, audience, conformance claims, and several other fields. The inspector probes for these fields and reports the first one found, plus its value, as evidence that the MX packet is present. The namespace URI is https://mx.allabout.network/ns/1.0.
Provenance AI payload
Every MX Compatible PDF this hub produces carries an AI-governance provenance record embedded inside the XMP packet under mx:ProvenanceAiPayload. The record is JSON. The inspector extracts it, parses it, and reports the number of steps recorded and the named operator. If the embedded record parses cleanly, you can download it as a standalone JSON file via the downloads panel.
Responsible Person Identifier
The responsible person block carries the human accountable for the file's audit chain: name, email, identifier URL, role, organisation, and country. The inspector reads it from the XMP packet (or from the embedded provenance payload as a fallback). The block is what regulators ask for under EU AI Act Article 4, the UK ICO accountability principle, the NIST AI Risk Management Framework, and EAA Directive 2019/882.
What the three tiers mean
The inspector classifies every file into one of three tiers.
MX Compatible. The file declares a tagged structure tree and carries the MX XMP namespace. It is accessible, attested, and machine-readable. This is the bar the MX Compatible badge represents.
EAA tagged only. The file declares a tagged structure tree but no MX namespace. It is accessible (Screen readers can walk it; EAA Directive 2019/882 conformance is plausible) but it is not attested. A regulator or AI agent cannot verify what the file claims or who authored it.
Plain PDF. The file does not declare a tagged structure tree. A screen reader has to guess. An AI agent has to do vision-based reconstruction. The European Accessibility Act compliance bar set on 28 June 2025 is not met.
Why this is not server-side
Some inspectors upload your PDF to their server, parse it there, and email you results. We do not. There are three reasons:
Privacy. The PDF you drop on this page may be confidential — a draft contract, a board paper, a medical record, a tax return. We do not want a copy. The inspector is built so that we cannot have one.
Verifiability. An inspection you can re-run locally, on the same file, with the same code, is more trustworthy than a server-side process you cannot see. The full inspector source ships in your browser. You can read it, copy it, run it offline.
Cost honesty. A free service that pays for itself in inspection volume eventually monetises in ways the visitor did not sign up for. We make our money from rebuilding documents into MX Compatible PDFs, not from inspecting yours.