Requirement
Applicable clause and technical reference
The mapping stays pinned with the profile version.
EN 301 549 document accessibility checks
Inspect non-web documents without pretending PDF and DOCX are the same format. The profile maps applicable EN 301 549 V3.2.1 requirements while each source keeps its own structural evidence and repair path.
Scanning profile
en-301-549-v3.2.1-nonweb-documentEN 301 549 documentsTechnical preflight
- Input
- PDF or DOCX
- Mapping
- EN 301 549 V3.2.1 · non-web documents
- Boundary
- Format checks plus document-specific human review
PDFTags, objects, metadata, and page evidence
DOCXOOXML structure and authoring guidance
SharedOne normalized outcome and clause map
Use EN 301 549 documents through the API.
Send en-301-549-v3.2.1-nonweb-document with the asset and keep this profile’s evidence boundary in the returned result.
One policy profile, evidence native to each document format.
A shared decision contract should not erase the source object an author needs to inspect and repair.
- Decision
Normalized outcome
Severity, coverage, confidence, and gate state
- PDF
Object and page evidence
Tags, annotations, structure, and page references
- DOCX
OOXML part evidence
Paragraphs, relationships, styles, and properties
Document evidence must stay repairable.
A clause reference explains the requirement; a source locator tells the team where to act.
Location
Page, object, OOXML part, or document relationship
Evidence remains specific enough to reproduce the failure.
Guidance
Repair in the source authoring environment
DOCX guidance points to Word semantics; PDF evidence points to the PDF structure.
Boundary
Unresolved human questions
Machine-clean structure never silently clears meaning or usability.
Use the profile before the document becomes expensive to change.
The strongest insertion point is before client handoff, archive, or PDF publication.
- Source
Inspect the DOCX
Catch authoring structure while it is still easy to repair.
- Output
Inspect the generated PDF
Validate what the conversion preserved, lost, or changed.
- Handoff
Keep one evidence trail
Route both results without flattening their locators.
Read the source behind this profile.
The EN 301 549 documents source and its legal or standards context can change. AccessPreflight pins the profile version used for a scan; your organization should re-review applicability and the source when requirements change.
Run EN 301 549 documents where content enters the workflow.
Keep the profile, coverage boundary, evidence, and human-review queue attached to every result.
Check a website freeCreate an account
Automated preflight is not an accessibility certification or legal determination.