Enterprise Power Suite

REFRACT PDF isn't just about rendering pixels; it's about generating highly discoverable and inclusive assets. The Enterprise Power Suite provides three core pillars that transform standard PDFs into accessible, searchable, and auditable records.

Three Core Capabilities

1. Unified Accessibility (PDF/UA & Section 508)

Every document tagged, structured, and validated - automatically.

• The Problem: Standard PDFs are "invisible" to screen readers, creating legal risk and excluding users.
• The Solution: Tags and checks every PDF against PDF/UA (ISO 14289-1) automatically. The REFRACT Engine validates every PDF against the standard at render time - heading hierarchy, table headers, alt text coverage, reading order, language declaration, and font embedding. The check produces a PASS, WARNING or FAIL verdict per document, written to a retrievable trace; nothing blocks delivery of the PDF regardless of the verdict.
• Compliance Coverage: Section 508, ADA, WCAG 2.1, PDF/UA (ISO 14289-1).
• Activation: Set "section508Accessibility": true in your template options.

2. Sovereign Discoverability (XMP Metadata)

Bridge the gap between document content and enterprise search.

• The Problem: Documents get "lost" in SharePoint or ERP systems because the internal data isn't indexed.
• The Solution: Embeds an Extensible Metadata Platform (XMP) stream directly into the PDF header, from a fixed set of fields the render already knows (document ID, correlation ID, doc type, template name/version, generation timestamp, PDF hash, title, language). This allows SharePoint, Adobe Acrobat, and Windows Explorer to "read" that metadata without opening the file.
• Activation: Set "xmpMetadata": true. There is no xmpData request object and no way to add custom business properties today - see XMP Metadata Embedding.

3. Render Trace Auditing (Explain Document)

A render trace for document generation.

• The Problem: Auditors ask, "How was this specific value calculated?" or "Why was this section redacted?"
• The Solution: Creates a trace that records every data transformation, conditional logic branch, and security masking event during the render.
• Activation: Set "explainDocument": true. There is no .vtrace file - the trace is fetched later by correlationId or documentId through the explain API.

Strategic Comparison

Implementation Pattern: Three-Pillar

For regulated industries, we recommend the Three-Pillar Pattern. This ensures every document generated is accessible, searchable, and auditable.

{
  "options": {
    "features": {
      "section508Accessibility": true,
      "xmpMetadata": true,
      "explainDocument": true
    }
  },
  "documentId": "TX-LLC-4920",
  "docType": "ComplianceReport"
}

documentId and docType are ordinary top-level request fields, not part of an xmpData object - there is no such object. They feed the XMP fields described above when xmpMetadata is enabled.

Verification & Trust

Audit the Auditor

You can pull a human-readable explanation of any document via the API. This is a POST with the correlation or document ID in the JSON body, not a GET with an id query parameter, and it requires an Entra bearer token:

curl -X POST "https://your-dispatcher.azurewebsites.net/api/explain/generate-pdf?mode=detailed" \
  -H "Authorization: Bearer $ENTRA_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "correlationId": "CORR_ID" }' \
  -o audit-trail-4920.pdf

Performance

No verified render-overhead or file-size figures are available for these features combined - measure them against your own templates rather than relying on a fixed benchmark.

Licensing

Availability depends on your licence.

Related Documentation

• Section 508 Accessibility Tagging
• XMP Metadata Embedding
• Explain Document
• REFRACT Template Assist