Primary language – Failed
Acrobat’s “Primary language – Failed” means a PDF doesn’t say what language it’s in. How to set it, fix invalid codes and mark passages in other languages.
Last updated
This message comes from Adobe Acrobat's Accessibility Checker.
Primary language – Failed is a result from the Accessibility Checker in Adobe Acrobat Pro, in its Document category. It means the PDF doesn't say what language it's written in. Adobe's help explains that setting the document language lets some screen readers switch to the right language. Without it, a screen reader guesses, and a Spanish notice may be read aloud with English pronunciation.
What this means
A PDF stores its language as a short code, such as en-US for US English or es for Spanish. There's one main language for the whole document, and any passage in another language can carry its own code on its tag in the document's hidden structure. Three different things can go wrong:
- Missing: the document has no main language at all. This is what Acrobat's rule checks.
- Invalid: the code isn't a real language code. "English" isn't valid, and neither is
en_US, because language codes use a hyphen, not an underscore. Assistive technology ignores invalid codes, so they're no better than none. - Unmarked passages: a Spanish paragraph in an English document isn't marked as Spanish. Acrobat doesn't check this one, but WCAG does.
That last point matters for many public agencies, whose notices often include English and Spanish side by side. Each version needs its own language, or one of them will be mispronounced.
Why it matters
Screen readers use the language setting to pick a voice and pronunciation rules. With the wrong language, words are mangled, sometimes to the point of being unintelligible. Braille displays can also use the wrong translation rules. This affects screen reader and braille display users, and it's covered by WCAG 2.1 success criteria 3.1.1 Language of Page and 3.1.2 Language of Parts.
How to fix it in Acrobat Pro
- In the Accessibility Checker panel, right-click Primary language and choose Fix. Choose the language in the dialog that opens, and choose OK.
- To set it by hand, open File > Properties (Ctrl+D, or Cmd+D on a Mac). On the Advanced tab, under Reading Options, choose the Language, or type a valid code such as
en-USores-US. - For each passage in another language, open the Tags panel (Accessibility tags in newer versions), right-click the tag that holds the passage, choose Properties, and set its Language.
- Save the file and run the check again.
- Listen to a bilingual page with a screen reader to confirm the voice switches where it should.
Fix it in the source file
Language set in the source carries into the PDF:
- Word: select the whole document and choose Review > Language > Set Proofing Language to set the main language. For a passage in another language, select it and set its proofing language separately. Microsoft documents that recent versions of Word mark text in a different language with its own language code when exporting to PDF.
- PowerPoint: use Review > Language > Set Proofing Language in the same way.
- InDesign: set the language in your paragraph and character styles, and set the document language under Advanced > Accessibility Options when you export.
For bilingual documents, consider separate English and Spanish versions. They're easier to read aloud, and easier to keep up to date.
Fix it automatically with Includoc
Includoc fixes the main language automatically. We detect the document's language, set it for the whole document, and replace any invalid language codes with the detected language.
Passages in another language are assisted. We detect language changes, such as a Spanish paragraph in an English notice, and mark them with their own language. You confirm those passages on the review screen, because short phrases, names and place names are easy for any detector to misjudge.
Upload your PDF to fix this automatically
Free check in seconds. Files are deleted within 24 hours.
Standards
| Standard or tool | Reference |
|---|---|
| WCAG 2.1 | |
| PDF/UA-1 (ISO 14289-1) | Clause 7.2 |
| Matterhorn Protocol | Checkpoint 11-001, Checkpoint 11-002, Checkpoint 11-003, Checkpoint 11-004, Checkpoint 11-005, Checkpoint 11-006 |
| Acrobat rule | Primary language |
| Standard or tool | Reference |
|---|---|
| WCAG 2.1 | |
| PDF/UA-1 (ISO 14289-1) | Clause 7.2 |
| Acrobat rule | Primary language |
| Standard or tool | Reference |
|---|---|
| WCAG 2.1 | |
| PDF/UA-1 (ISO 14289-1) | Clause 7.2 |
| Matterhorn Protocol | Checkpoint 11-007 |
Related errors
- Title – Failed: the other document-level setting that screen readers announce first.
- Bookmarks – Failed: another document-level check in the same Acrobat category.
For the full checklist, read How to make a PDF accessible, or check a PDF free to see the language your file declares.
Related
- Title – Failed
Acrobat’s “Title – Failed” means a PDF has no title or doesn’t show it in the title bar. How to set and display the title, and how to write a good one.
- Bookmarks – Failed
Acrobat’s “Bookmarks – Failed” means a document of 21 or more pages has no bookmarks. How to create them from headings in Acrobat Pro, Word and InDesign.
- How to make a PDF accessible: a step-by-step guide
Make a PDF accessible from start to finish: fix the source file, export with tags, then check and fix tags, reading order, alt text, tables and forms.