What does EN 301 549 mean for PDF documents?

ICT means information and communication technology. The standard covers more than PDFs, including the web, software and equipment. For a standalone PDF, the document requirements in clause 10 are central. Other provisions may be relevant depending on function and context.

ETSI has published V4.1.1 dated 2026-09. That alone does not mean every national regulation, procurement or EU legal reference already uses that edition.

Sources: [1]

Consider a municipality publishing a decision as a PDF on its website. Sweden’s DOS Act establishes the accessibility duty. At this source check, Digg’s guidance points to EN 301 549 V3.2.1, based on WCAG 2.1. The standard helps specify technical requirements; the assessment must show what those mean for the decision’s text, tables, links and attachments.

This explains why ETSI’s latest published document and the edition referenced by an authority can differ. V4.1.1 has been published, but a Swedish DOS assignment should not silently change its target merely because a higher version number exists.

A concrete commission should record legislation, standard edition and testing method separately. A supplier can use newer software without changing the agreed requirement. The tool version belongs in the test record.

Sources: [4]

• Latest published standard: what the standards body has released.
• Legally referenced edition: the version identified by the relevant legal framework.
• Contracted edition: the requirement agreed between customer and supplier.

Chapter 10 of V3.2.1 covers non-web documents. For a typical report, text alternatives, information and relationships, meaningful sequence, contrast and language are central. A report with interactive fields also needs assessment of those functions. Begin by identifying what the file actually contains.

Give each applicable requirement a row in the review record. For tables, identify which tables were assessed and how. For language, record the document language and passages with language changes. A document without audio or video may have no relevant content for certain media requirements. “The tool found nothing” is not a reason to mark a requirement inapplicable.

This makes delivery understandable to the buyer. A PDF/UA report can be important evidence, but it does not itself show that every applicable EN 301 549 requirement was examined. Ask for a mapping between requirements and checks so gaps become visible before handover.

Suppose a municipal report has a table on page 6 where 105 means hours for February. In V3.2.1, clause 10.1.3.1 addresses information and relationships in documents, linked to WCAG 1.3.1. An assessment entry can identify that requirement, page and cell.

Method: compare visible headers with tag structure and test cell navigation in a recorded environment. Observation in this hypothetical example: the cell lacks its association with the Hours header. Assessment: a failure against the stated requirement. Remedy: restore the relationship and retest that cell and its neighbours.

This illustrates documentation, not a completed test of your file. It also shows why “tables checked” is insufficient: another reader needs to follow the method and conclusion.

Sources: [5]

To rely on a harmonised standard for a presumption of conformity, check the relevant EU citation, its coverage and any transition period. The standard’s title or a newly changed version number is not sufficient to establish that legal effect.

Sources: [2], [3]