EN 301 549 document accessibility API

Put EN 301 549 document checks inside the upload or document-generation path. PDF and DOCX use one asynchronous lifecycle while keeping locators and repair guidance appropriate to each source format.

For CMS, DAM, and document-generation teams gating files before publication

API profileen-301-549-v3.2.1-nonweb-document@1.2.0

Try it free Book a demo

Illustrative request202 Accepted

POST /v1/scans
Idempotency-Key: dam:asset:93812:v7

{
  "asset": {
    "type": "upload",
    "upload_id": "upl_annual_report_2026"
  },
  "profiles": [
    "en-301-549-v3.2.1-nonweb-document@1.2.0"
  ],
  "metadata": {
    "external_id": "dam:asset:93812:v7"
  }
}

queuedid: scn_01J…profile resolved

Inputs: PDF or DOCX upload
Evidence: Object, relationship, page, or part
Route: Back to authoring source

Route one document result through three operational layers.

The API preserves a stable decision contract while keeping PDF and DOCX evidence close to the source system that can repair it.

Asset
Resolve format and source ID
Attach the DAM or generator identity.
Profile
Run the non-web mapping
Pin the EN 301 549 profile version.
Owner
Return format-native evidence
Send object or OOXML repair work back to authors.

Normalize the decision without flattening the document.

The result fields stay stable, but the evidence points to the source object that an author or remediator can actually inspect.

PDF

Tag and object evidence

Locate document-wide structures, pages, annotations, and tagged-content relationships.

DOCX

OOXML part evidence

Point to paragraphs, relationships, styles, tables, and document properties.

Shared

One publishing decision

Return severity, confidence, coverage, remediation, and a configured gate outcome.

Give the DAM a result it can route automatically.

A signed completion event can update the asset state while the full report remains available to editors and accessibility specialists.

Signed eventscan.completed

Asset: dam:asset:93812:v7
Profile: en-301-549-v3.2.1-nonweb-document@1.2.0
Result: review_required
Publishing state: Needs accessibility review
Source retention: Configured separately from report archive

Inspect the policy behind the API profile.

Before EN 301 549 documents becomes a production gate, review its source mapping, supported input, automation boundary, and required human checks.

Read the EN 301 549 documents profile ETSI EN 301 549 V3.2.1

Put the EN 301 549 documents API in the path you already own.

Start with one asset flow, pin the profile, and keep evidence and unresolved human work attached to every result.

Check a website free Create an account

Automated preflight is not an accessibility certification or legal determination.