Published October 15, 2026

WCAG 3.1.1 Language of Page, Level A

Does WCAG require a page language?

Yes. Success criterion 3.1.1 Language of Page is Level A, so it is also required at Level AA. The default human language of each web page must be programmatically determinable. In HTML, that is the lang attribute on the html element. The value has to be the language the page actually uses. The text is in the W3C WCAG 2.2 Recommendation.

What does a page language tell assistive technology?

It tells user agents which language rules to use. Screen readers can load the right pronunciation. Browsers can display characters and scripts correctly. Media players can show captions correctly. The W3C explanation is in Understanding Success Criterion 3.1.1. The default language is the one used most. When several languages are used equally, the first language used is the default. A page with no language set fails 3.1.1. A page whose attribute names a different language from the one used most also fails it.

Where does the language go in HTML?

The sufficient technique is technique H57: the language attribute on the html element, such as lang="en" or lang="es". Putting lang only on body, or only on a wrapper, does not follow that technique. A PDF has a different place for the same fact, the /Lang entry in the document catalog, covered on the accessible PDFs page. The title element in the same head is a different requirement. It has to describe the topic or purpose, covered on the page title page.

When does a passage need its own language?

Success criterion 3.1.2 Language of Parts is Level AA. Each passage or phrase in a different language must be programmatically determinable, except for:

• Proper names, such as a person’s name or a place name.
• Technical terms.
• Words of indeterminate language.
• Words or phrases that have become part of the surrounding language, such as “rendezvous” in English.

A German phrase inside an English sentence, or a link whose text is “Français,” needs its own lang. The technique is H58. The criterion text is in the WCAG 2.2 Recommendation, and the explanation is in Understanding Success Criterion 3.1.2. A single word is still a phrase unless an exception applies. Understanding 3.1.2 also notes that some screen readers speak an accessible name without switching language, even when the markup is correct. That limit is in the user agent. It does not fail the criterion. Check the code. Accessible names are a separate check, covered on the accessible names page.

Can a scanner tell that the language is wrong?

A tool can see that lang is missing, or that the value is not a language tag. It often cannot tell that lang="en" is wrong on a page written in Spanish. A person reads the page and compares it with the attribute. That is why a passing score is not conformance, as covered on the scanner page.

Does the Title II web rule include page language?

Yes. The Department of Justice rule for state and local government websites names WCAG 2.1 Level AA. That level includes 3.1.1 and 3.1.2. Who must comply, and the April 2027 and April 2028 dates, are on the Title II web rule page. The fix is one attribute on the page template, plus lang on passages that change language. That work is remediation.