Many screen reader applications support multiple languages and can switch between them using appropriate voice and rule sets. However, screen readers are only able to do this if the language of content is identified in the underlying code or document.
Overview
Many screen reader applications support multiple languages and can switch between them using appropriate voice and rule sets. However, screen readers are only able to do this if the language of content is identified in the underlying code or document. Web and document authors should always identify the default language of a page or document and, if content changes to a different language, the language of that specific content should be identified as well.
Why this matters
Screen readers and assistive technologies use language information to apply the correct pronunciation rules, accents, and speech patterns. Without proper language identification:
- Screen readers cannot switch to the correct language voice, causing them to read non-English text with an English accent
- Foreign language content becomes unintelligible or mispronounced, making it impossible for assistive technology users to understand
- Users who speak multiple languages cannot rely on their screen reader to switch between appropriate voices
- Search engines cannot correctly index multilingual content
For example, a French phrase read with an English accent by an English-language screen reader becomes garbled. Properly marking the language allows the screen reader to switch to a French voice and apply correct pronunciation.
Techniques
Language in HTML
Use the lang attribute with BCP 47 codes to identify the language of your HTML page. For example:
<html lang=”en”>
For parts of a page in other languages, apply the lang attribute to the specific element:
<p lang=”fr”>Vaut mieux prevenir que guerir.</p>
Language in UGA CMS and Other CMS
WordPress and other content management system platforms automatically add the lang attribute to the <html> element during installation. As a content author, you typically do not need to change the default page language. However, you should mark passages of content that use a different language from the rest of the page.
Language in PDF (Adobe Acrobat Pro DC)
Setting the document language in PDFs ensures screen readers use the appropriate voice and pronunciation rules.
Setting Document Language
- Open a PDF in Adobe Acrobat Pro DC
- Go to File > Properties
- Click the Advanced tab
- Select your language from the Language combo box
Setting Language of Parts
- Open the Tags navigation pane: View > Show/Hide > Navigation Panes > Tags
- Select the foreign language text in the PDF
- Right-click and choose Find Tag from Selection
- Right-click the resulting tag and select Properties
- Click the Tags tab and select the appropriate language from the Language combo box
Language in Word and PowerPoint
To set the default language in Word or PowerPoint:
- Select all content (Ctrl+A or Cmd+A)
- Go to Review > Language
- Select your default language
To mark parts of a document in a different language:
- Select the text in the other language
- Go to Review > Language
- Select the appropriate language for that selection
Language in eLC (eLearning Commons)
eLC provides options for setting language at multiple levels.
Default Language
The default language can be configured at the course or platform level in your course settings. This setting affects the built-in eLC interface and content provided by the system.
Language of Parts
The rich content editor in eLC does not provide direct support for marking selected text with a specific language attribute. If your content switches to a different language:
- Switch to HTML view in the rich content editor
- Manually add the appropriate lang attribute to elements containing foreign language content
Common mistakes
- Missing lang attribute on the html element: Every page should have <html lang=”en”> or appropriate language code at minimum. Without this, screen readers default to their installed language.
- Not marking language changes inline: When content switches to another language mid-document, that passage must be marked with the appropriate lang attribute. Otherwise, screen readers won’t switch voices.
- Using wrong language codes: Use correct BCP 47 language codes (e.g., “en” for English, “es” for Spanish, “fr” for French). Incorrect codes may not be recognized by assistive technologies.
- Not identifying language of quoted foreign text: Even short foreign language quotes or words need language identification to be read correctly.
- Assuming content is obviously in another language: Visual presentation alone does not communicate language to assistive technology. Marking is always required.
WCAG 2.1 Success Criteria
- 3.1.1 Language of Page (Level A): The default human language of each web page can be programmatically determined
- 3.1.2 Language of Parts (Level AA): The human language of each passage or phrase in the content can be programmatically determined, except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text
Getting help
If you have questions or need assistance, the Digital Accessibility Services Hub (DASH) is available to support colleges, schools, and administrative units as they build sustainable accessibility practices.
- Contact DASH at [email protected] for consultations, training, or technical assistance.
Accessibility is a shared responsibility, and every step you take makes UGA’s digital environment more inclusive.