EN 301 549 10 -- Non-Web Documents Overview

For reference only -- not part of a11ybot's automated checks.

What It Is

Clause 10 of ETSI EN 301 549 v3.2.1 is the non-web-documents mirror of clause 9 (web content)[1]. It takes the WCAG 2.1 Level A and AA success criteria and re-applies them to artefacts that are not web pages: PDFs, Microsoft Office files (.docx, .xlsx, .pptx), OpenDocument files, EPUB publications, and standalone media files distributed as downloads or email attachments[2]. Each WCAG SC is mapped onto a clause 10.x equivalent with web-specific wording (web page, set of web pages) replaced by document-format wording, following the W3C WCAG2ICT Task Force Note. Clause 10 explicitly excludes documents that are rendered inside a web page (those stay under clause 9) and documents that are software user interface (those move to clause 11)[2].

Why It Matters

Most of the text the public reads from government and large enterprises -- tax forms, benefit determinations, policy documents, procurement notices, user manuals, board reports -- is delivered as PDF or Office files, not HTML. A WCAG-conformant web page that links to an untagged PDF hands the user a dead end: the HTML is navigable, the payload is not. Clause 10 closes that gap by pulling documents into the same regulatory surface as web content, so procurement language that says "complies with EN 301 549" covers both.

How It Relates to WCAG

The mapping from WCAG 2.1 to clause 10 is direct at the identifier level: 10.1.1.1 is WCAG 1.1.1 Non-text Content, 10.1.4.3 is WCAG 1.4.3 Contrast (Minimum), 10.2.4.6 is WCAG 2.4.6 Headings and Labels, and so on across every Level A and AA criterion[2]. The application is not direct, because a document has no browser, no DOM, no cascading user style sheet, and no HTML semantics to lean on. Assistive technology reads the document through whatever structural mechanism the format provides: the PDF tag tree for PDF, the OOXML styles.xml and document part relationships for Word, the ODF accessibility metadata for OpenDocument, the EPUB navigation document and ARIA-in-EPUB roles for EPUB 3. "Heading" in a PDF is not a visually-larger glyph run; it is an H1 through H6 structure element in the tag tree, and a screen reader that cannot find those elements will not expose heading navigation regardless of how the page looks.

The failure mode specific to clause 10 is applying WCAG criteria by visual analogy: authors style a paragraph to look like a heading, bump the font, and assume 1.3.1 Info and Relationships is satisfied. It is not. Clause 10 inherits WCAG 1.3.1 via clause 10.1.3.1, and the document-format equivalent of programmatic structure is the tag tree (or OOXML style, or ODF heading style) -- not the visual rendering. ISO 14289-1 (PDF/UA-1) is the concrete technical specification that says how that tag tree has to be built for a PDF to be machine-readable by assistive technology[3].

Practical Implications

  • Treat PDFs, Office files, and EPUBs as first-class accessibility targets under the same procurement clause as the website.
  • Use ISO 14289-1 (PDF/UA-1) as the concrete conformance target for PDFs -- it is the standard clause 10 implicitly relies on to turn WCAG criteria into PDF-specific structure rules[3].
  • Configure authoring tools (Word, InDesign, LibreOffice) to emit a tag tree on export. Visual-only styling never becomes programmatic structure after the fact.
  • Scanned PDFs without OCR carry no text layer and no tag tree. They fail clause 10 at 10.1.1.1 Non-text Content before any other check runs.
  • Complex layouts (magazines, annual reports, multi-column reports) need authored reading order in the structure tree. Tools that auto-detect reading order from glyph positions produce tag trees that linearise incorrectly.

Related Clauses

The PDF sub-pages in this section cover the failure modes that account for most document remediation work: structure, order, tables, forms, and image alternatives.

Sources

  • ETSI EN 301 549 v3.2.1, clause 10 Non-web documents[1].
  • Accessibility Standards Canada, plain-language summary of EN 301 549 clause 10[2].
  • ISO 14289-1 (PDF/UA-1)[3].
  • WCAG 2.1 -- the criterion set clause 10 adopts.