AccessibilityPDF — Martin Schrammel AB

Tags and structure

Language and document title in PDF

Identify the text’s language and give the document a meaningful name. This supports pronunciation and orientation.

Applies to
Document metadata and language changes in tagged text
Sources checked
Language

Language information supports pronunciation

Set the document’s main language. A longer passage in another language may need its own language property in the structure. A Swedish document containing an English quotation should not treat the entire quotation as Swedish.

Codes such as sv-SE and en-GB identify language and sometimes region. Choose according to the content, not the company’s office location.

Sources: [1], [3]

Document language and language changes must work together

The document’s main language supplies a baseline for interpretation. An English summary in a Swedish report should receive an appropriate language property in the structure. Changing the whole file to English to improve that summary may worsen pronunciation elsewhere.

Identify coherent passages where language changes matter. Proper names and established borrowed words require judgement; not every word of foreign origin automatically needs its own language marker. WCAG’s language-of-parts criterion has explicit exceptions that should be read in context.

Test in an environment supporting language switching with the necessary voices available. If pronunciation does not change, distinguish document markup from screen-reader settings. Poor pronunciation is an observation to investigate, not conclusive proof that the file’s language code is wrong.

The title is more than the filename

School travel guidelines 2026 says more than final_v7.pdf. Complete the document title field and check the option to display the document title. A useful filename helps, but does not replace that metadata.

Choose a title that makes sense when several documents are open. “Decision” is less useful than “Travel grant decision, autumn term 2026”. Include an edition or period when needed to distinguish documents, and avoid internal working names understood only by the project team.

Export can inherit an old template title even after the cover changes. The visible title may be correct while properties still describe last year’s report. Inspect the exported file’s properties and compare them with its content. Also check whether the reader displays the document title or filename.

Sources: [2]

Example: two languages on a page

Example A Swedish report with an English summary paragraph

Before

The document’s main language is English because the export template was English.

After

Set Swedish as the main language and identify the English paragraph’s language.

Why this works Assistive technology has better information for choosing pronunciation. Still test with the reader and voice actually used.

Check after export

Test again after merging PDFs. A Swedish report and an English appendix may acquire one document language without preserving the appendix language at passage level. Recheck bookmarks and title too, so the combined delivery is identifiable and navigable.

  • Is the title correct in document properties?
  • Does the reader display the intended title?
  • Are the main language and meaningful language changes identified?
  • Are abbreviations and proper names understandable without altering the source text’s meaning?

Sources

  1. PDF16: Default document languageW3C
  2. PDF18: Document titleW3C
  3. PDF19: Language changesW3C

Examples are our own unless stated otherwise. These guides distinguish legal requirements, standards and practical advice. Passing an automated check is not a complete assessment of document accessibility.

All guides

Need help with your PDFs?

The service is in development. Sign up for an email when we open. You can read the full knowledge library in the meantime.

Get a launch notice