What happens if a document fails PDF/A validation in court e-filing?

Court e-filing systems (like PACER) deploy automated validators that immediately reject non-compliant files, preventing document submission and potentially causing missed statutory deadlines.

Why does my file fail validation because of fonts?

PDF/A strictly forbids relying on system fonts. Every font used on every page must have its actual font program embedded inside the PDF so the document displays identically decades later.

Can I validate files without an active internet connection?

Yes! Because our validator runs 100% client-side inside your browser via WebAssembly, you can disconnect from the internet and validate files in complete offline isolation.

What is the difference between PDF/A-1b and PDF/A-2b validation?

PDF/A-1b is based on PDF 1.4 and strictly forbids transparency and layers. PDF/A-2b is based on PDF 1.7 and allows transparent vector art, layers, and modern image compression.

Can your tool fix the errors found during validation?

Yes. If your document fails due to missing Output Intents or non-compliant metadata, you can run it through our PDF to PDF/A tool to inject compliant profiles.

Are my files uploaded or stored on any server during validation?

Never. All document parsing, structural inspection, and reporting occur strictly inside your web browser's local RAM. No file data is ever transmitted across the network.

What is the difference between PDF/A-1b and PDF/A-1a validation?

PDF/A-1b only validates visual preservation (ensuring the document looks identical over time). PDF/A-1a also validates structural accessibility (tagged headings, logical reading order, and alternative text for screen readers).

How does the validator check alternative text for images?

For Level 'a' conformance, our engine traverses the /StructTreeRoot dictionary to ensure every /Figure element contains a non-empty /Alt string describing the image content.

PDF/A Archival Validator

In-Depth Technical Guide•8 min read•2RUN Engineering Team

100% Client-Side • Zero Upload

The Authoritative Guide to In-Browser PDF/A Archival Validation (ISO 19005 Conformance)

⚡How to Validate a PDF/A Document In-Browser

1. Import Your Target PDF

Drag and drop your document into the secure validation workspace, or select it from your local storage drive.

2. Select Target Conformance Level

Choose your expected ISO standard (PDF/A-1b, PDF/A-2b, PDF/A-3b) or allow auto-detection based on embedded XMP metadata.

3. Execute Structural Inspection

Our client-side engine traverses the object graph, inspecting font embedding, Output Intents, metadata, and prohibited tokens.

4. Review Detailed Compliance Audit

Inspect the itemized pass/fail diagnostic report with clause-level ISO citations, or export the audit log for compliance records.

Submitting electronic documents to judicial e-filing systems (such as the US Federal Court PACER system), national archives, tax authorities, and corporate compliance repositories mandates strict compliance with the ISO 19005 (PDF/A) standard. Simply possessing a PDF file that claims to be archival is insufficient; institutional intake gateways deploy automated validators that rigorously inspect the physical byte stream. If a single font glyph lacks an embedded TrueType program, an Output Intent ICC profile is missing, or an unapproved JavaScript snippet is detected, the filing is rejected immediately, leading to missed statutory deadlines, sanctions, and administrative delays.

Historically, validating PDF/A compliance required expensive desktop software suites (like Adobe Acrobat Pro Preflight) or complex command-line Java utilities (such as VeraPDF). Cloud-based validation services introduce unacceptable compliance risks by uploading confidential legal briefs and corporate filings to third-party servers.

Our client-side PDF/A Validator delivers VeraPDF-caliber structural conformance verification directly inside your web browser. Executing 100% locally using WebAssembly, our engine inspects font descriptors, color spaces, metadata schemas, and prohibited operator tokens in seconds—providing transparent, itemized pass/fail diagnostic reports with total privacy and zero cloud uploads.

Read the full technical guide

The ISO 19005 Validation Framework: VeraPDF-Style Structural Verification

A thorough PDF/A validation requires deep static analysis of the entire PDF object graph against hundreds of normative rules defined across ISO 19005-1, ISO 19005-2, and ISO 19005-3. Our client-side validator implements the comprehensive rule matrix utilized by international archival institutions:

1. Document Catalog and Header Syntax: Validating binary marker comments, PDF version compatibility (1.4 for PDF/A-1, 1.7 for PDF/A-2), cross-reference table syntax, and trailer integrity.

2. Metadata Stream Consistency: Verifying that the document contains an uncompressed XMP stream (<x:xmpmeta>) with the official PDF/A Identification schema (http://www.aiim.org/pdfa/ns/id/), and ensuring properties match Info dictionary values.

3. Conformance Level Verification: Checking conformance claims (Level 1b/2b/3b for visual preservation, Level 1a/2a/3a for tagged structural accessibility).

Font Conformance: Embedding, Glyph Programs, and ToUnicode CMaps

Font non-compliance accounts for over 75% of real-world PDF/A rejection errors. Our engine performs exhaustive typographic inspection across every font dictionary in the document /Resources trees:

1. Complete Embedding: Verifying that every referenced font descriptor has a valid /FontFile, /FontFile2 (TrueType), or /FontFile3 (CFF/OpenType) stream. Documents relying on standard system fonts (like Arial, Times New Roman, or Courier) without embedded subsets will fail immediately.

2. Character Code Mapping: Checking that composite fonts (Type 0 / CIDFonts) contain a valid /ToUnicode CMap mapping every glyph identifier to a standard Unicode codepoint, ensuring that future search engines can extract legible text.

3. Glyph Metrics (/Widths): Validating that the character widths defined in the font dictionary match the internal metrics of the embedded font program.

Color Space Management: Output Intents and Device-Independent Calibration

Uncalibrated device colors (DeviceRGB, DeviceCMYK, DeviceGray) are strictly forbidden in PDF/A unless the document catalog contains an explicit /OutputIntents dictionary containing an ICC profile.

Our validator verifies:

- The presence of an /OutputIntent with the subtype /GTS_PDFA1.

- The validity of the embedded ICC profile stream (/DestOutputProfile), parsing the ICC profile header to confirm color space matching (e.g., RGB vs. CMYK).

- Consistency between image color spaces and the Output Intent condition identifier (e.g., 'sRGB IEC61966-2.1'). Any unmanaged color spaces that could produce ambiguous color reproduction on future monitors or printers are flagged as critical compliance errors.

Detecting Prohibited Features: JavaScript, Encryption, and Multimedia

ISO 19005 strictly bans features that could compromise future readability or execute malicious code. Our validator conducts deep byte scans for:

1. Password Encryption: The document must not contain an /Encrypt dictionary. Any password protection or DRM locking triggers immediate failure.

2. Dynamic Scripting: Scanning document and page action dictionaries (/A, /AA) for /JavaScript or /JS operators. Executable code is disallowed.

3. Multimedia and Remote Streams: Searching for /Movie, /Sound, /Screen, and /Launch action annotations that rely on external applications.

4. LZW Compression: Verifying that streams do not use the deprecated, patent-encumbered /LZWDecode compression filter.

Transparent Itemized Reporting with Clause-Level References

Rather than presenting a vague 'Invalid' error, our validator generates a comprehensive, human-readable compliance report. Each inspected rule is categorized by severity (Pass, Warning, Critical Error) with direct citations to the relevant ISO 19005 clause (e.g., 'Clause 6.2.3.3: Font programs not embedded').

You can inspect specific page numbers, object identifiers, and font names associated with each violation. This allows legal preparers, desktop publishers, and software developers to pinpoint and fix non-compliant elements before formal e-filing submission.

Air-Gapped Privacy for Sealed Legal Filings and Financial Audits

Validating sealed court dockets, pending patent disclosures, corporate M&A prospectuses, or confidential patient records using third-party cloud validators exposes organizations to devastating security leaks and regulatory fines under GDPR, HIPAA, and attorney-client privilege rules.

2run.tools operates with 100% client-side privacy. The entire PDF parsing, font program analysis, ICC profile inspection, and rule validation pipeline execute locally in your browser's WebAssembly sandbox. Not a single byte of your document is ever uploaded to a remote server.

Tagged Structure Tree (/StructTreeRoot) and Accessibility Conformance (PDF/A-1a and PDF/A-2a)

While basic PDF/A conformance (Level 1b and 2b) focuses exclusively on visual preservation, Level 'a' conformance (Accessible Conformance - PDF/A-1a, PDF/A-2a) mandates that the document include a complete logical structure tree (/StructTreeRoot).

Our client-side validator inspects the logical structure hierarchy to verify full accessibility compliance:

1. Tagged Content Markers: Verifying that all text elements are enclosed within marked-content sequences (/BDC and /EMC) linked to structure elements.

2. Structural Tagging: Checking for standard semantic tags, including structural headings (/H1 through /H6), paragraphs (/P), tables (/Table, /TR, /TD), and lists (/L, /LI).

3. Alternative Text for Visuals: Ensuring that all images, charts, and figures include descriptive alternative text (/Alt strings) within their structure element dictionaries.

This in-depth structural inspection ensures that documents submitted to governmental accessibility audits (Section 508, ADA Title III, EN 301 549) meet both visual preservation and screen-reader accessibility mandates.

💡Pro Tips for PDF/A Validation and Compliance

•If validation fails due to missing font embedding, re-export the original document from Word or InDesign with 'Embed All Fonts' checked.
•Ensure the document is completely unencrypted; removing passwords is required before any PDF can achieve valid PDF/A certification.
•Check that XMP metadata properties (Title, Author) do not conflict with the document's legacy Info dictionary entries.
•Export the validation report as a record to prove compliance to clients, courts, or institutional archives upon document submission.

🛡️AST Traversal, Font Descriptor Auditing, and ICC Profile Verification

Our validation engine parses the PDF binary stream into a structured Abstract Syntax Tree (AST). It inspects the /Root catalog for /OutputIntents, verifying that the destination profile matches the standard ICC specification (ISO 15076-1). It recursively iterates through the /Pages tree, inspecting every /Font dictionary in each page's /Resources. For each font, it checks for /FontFile /FontFile2 /FontFile3, parses the font header to ensure glyph subset coverage, and verifies the /ToUnicode CMap stream. It verifies that /Annots arrays contain no prohibited subtypes and confirms that the XMP packet matches the RDF syntax for pdfaid:part and pdfaid:conformance.

Stack: WebAssembly • Multi-threaded Web Workers • HTML5 Canvas API

Privacy: Files never leave your device or touch a cloud buffer; analytics run only with your consent.