1. Identify the language of the actual content
Read a representative page and record its main language. Do not infer it from the owner’s location, domain suffix, or intended market. A website aimed at one country may contain several language versions, and an English navigation menu does not establish the language of a long article.
For each template, identify where the language value comes from and who maintains it. A translated page should have an explicit content decision, not simply inherit the setting from the original page. Keep a list of routes that need review when their main text and shared navigation use different languages.
2. Declare the default on the HTML element
W3C’s internationalization guidance recommends using the lang attribute on the html element for the default language of an HTML page. The value is inherited by its descendants. For an English page, the simple example is <html lang="en">.
W3C also explains that character encoding and a Content-Language meta element are not substitutes for this declaration. Keep the distinction clear in the implementation record. The declaration identifies the language of text; it does not translate content, choose an audience, or prove that the writing has been checked by a fluent reviewer.
Sources: [1]
3. Mark meaningful language changes
W3C advises placing an appropriate language attribute on an element around content in another language. Inspect the actual passage before choosing the boundary so unrelated surrounding text does not receive the wrong language setting.
As an editorial review, identify longer quotations, translated instructions, or bilingual content blocks that deserve attention. Ask a competent language reviewer where the text is uncertain rather than guessing from a short phrase. Keep the review record precise: which passage changes language, what value is intended, and where the markup should begin and end.
Sources: [1]
4. Check values and text direction separately
Use recognized language tags rather than an invented label. W3C points to BCP 47 and the IANA language-subtag registry for choosing values. Add a regional or script distinction when it is warranted by the content, not merely to make the code look more specific.
Text direction is a separate concern. W3C explains that language markup alone does not establish direction for bidirectional text. If the page includes a right-to-left language, include direction and layout in a dedicated review instead of assuming a lang change completes the work. Keep examples and test content representative of the real page.
Sources: [1]
5. Verify generated pages and maintenance
Inspect the delivered HTML for each relevant template and language version. Confirm that the default value matches the content and that any passage-level changes survive the publishing process. A content editor field can be correct while the output template ignores it or applies it to the wrong element.
Where language-dependent browser or assistive-technology behavior is tested, record the actual environment and result. Do not describe source inspection as a complete pronunciation or accessibility test. Add language review to the translation and template-change checklist so new pages inherit the intended value without overwriting pages written in another language.
Your quick checklist
- The main language is determined from the actual page.
- The HTML element declares the intended default.
- Relevant passages in other languages are marked accurately.
- Language-tag choice and text direction are reviewed separately.
- Generated pages and any behavior tests have a recorded scope.
Sources & scope
W3C supports the HTML language-declaration facts. The template inventory and maintenance sequence are ATN editorial guidance. No translation, pronunciation test, or full accessibility assessment is implied.
- W3C Internationalization: Declaring language in HTML (opens in a new tab)Source checked October 9, 2026
Published October 9, 2026. No affiliate links or paid placements in this guide.
