SEO & Search

Language Attributes on B2B Websites: Identify the Page and Its Foreign-Language Passages

A Spanish paragraph can look correct while the page identifies it as English.

The letters render. The accent survives. The editor approves the wording. The language declaration still describes a different passage.

Inspect the words and their markup together. Identify the page's default language, then examine the passages that depart from it.

This review follows a fictional bilingual documentation service. Its quotation, service terms, worksheet, and decisions are invented. They describe no client, completed audit, or observed commercial result.

Separate the Five Questions Hidden Inside “Language”

Use five fields when the review begins. A single checkbox marked multilingual cannot tell the next editor what was examined.

The page language identifies the language of the document's text. A passage language identifies a change within that document. Both belong in this review.

An alternate-language page is a separate destination. Keep its search annotations in the hreflang review. Selecting languages and queries belongs in multilingual keyword research.

Character encoding concerns the mapping between stored bytes and characters. A correct encoding does not identify the natural language. W3C: Character encodings for beginners.

Writing direction concerns the flow of text. Language markup does not establish direction; bidirectional content needs its own direction handling. W3C: Declaring language in HTML.

Record those boundaries before assigning findings. An editor might report a damaged character, a wrong inherited language, and an incorrect alternate destination in one screenshot. Give each observation its own record.

For the fictional page, the task is narrow: identify the English document and its Spanish preparation passage. Translation quality, search targeting, and right-to-left layout remain outside this example.

Keep the Two WCAG Criteria Separate

WCAG 2.2 SC 3.1.1, Language of Page, is Level A. It requires the default human language to be programmatically determinable. Normative SC 3.1.1.

SC 3.1.2, Language of Parts, is Level AA. It addresses passages and phrases. Exceptions cover proper names, technical terms, indeterminate language, and words or phrases adopted into the surrounding vernacular. Normative SC 3.1.2.

W3C's Understanding documents explain these requirements. They are informative guidance. The Language of Page guidance describes choosing the predominant language, or the first language when several are used equally. Understanding Language of Page.

Keep two decisions in the worksheet. First, does the default declaration match the document? Second, do the relevant changes within it have an appropriate declaration?

A correct English root does not settle an unmarked Spanish paragraph. A marked Spanish paragraph does not settle a missing root declaration.

Record the criterion beside the finding. Avoid an undifferentiated accessibility status that conceals which question remains open. This focused review establishes neither whole-page conformance nor legal compliance.

Inspect the Default Before Tagging Individual Words

For HTML, W3C recommends placing lang on the html element. Descendants inherit that language until a surrounding element declares a different one. Use BCP 47 language tags. W3C: Declaring language in HTML.

Inspect the rendered document's root. Record the exact value, including a missing or empty value. Do not fill an unknown field from the language visible in the headline.

Ask the content owner to confirm the language of the approved copy. Keep that confirmation separate from the observed attribute. One describes the text; the other describes the implementation.

For the fictional page, the owner identifies the introduction, scope, navigation, and closing instructions as English. The preparation passage is Spanish. The proposed root is lang="en".

Use the inspected ancestor chain to explain each passage's effective language. A paragraph without its own attribute can still have an inherited language. Writing “missing lang on paragraph” would leave that distinction unresolved.

Include reusable content in the inventory. In a separate fictional test variant, an English preparation note appears inside a Spanish section. The editor approves the note's words but leaves its placement unresolved.

Record the section boundary, the note's exact text, and the nearest language declaration. Ask the content owner whether the note belongs inside that section. If it stays there, ask the implementation owner to identify its English language explicitly.

Keep both decisions in the record. Moving the note and declaring its language are different proposed changes. Retest the selected version against the approved words. Do not close the finding because the reusable component looked correct on another English page.

Record the rendered document as well as the template. A correct template is useful evidence for implementation work. The actual page version remains the object of the review.

Walk Through a Fictional Bilingual Passage

The invented service page says that buyers submit approved samples before a documentation review. It repeats that preparation instruction in Spanish.

The quotation below is written for this example. It is not a testimonial or an attributed statement. The English explanation means “Send only approved documents.”

The proposed HTML is:

<html lang="en">
  <head><title>Documentation review</title></head>
  <body>
    <h1>Documentation review</h1>
    <p>Send approved samples before the review.</p>
    <blockquote lang="es">
      <p>Envíe solo documentos aprobados.</p>
    </blockquote>
    <p>The review excludes rewriting.</p>
  </body>
</html>

The introduction inherits English from the root. The quotation declares Spanish on its enclosing element. Its paragraph inherits Spanish. The final paragraph sits outside the quotation and inherits English.

That final boundary matters. Suppose an editor accidentally includes the exclusion inside the Spanish block. The English exclusion would inherit Spanish too. Inspect where the element closes, not only where the attribute appears.

Keep the markup sample beside the approved words. If the quotation later becomes a longer passage, repeat the inspection against the changed boundary. A copied attribute is useful only when it still describes the text it surrounds.

The example uses general English and Spanish tags. It makes no claim about a regional voice, pronunciation preference, or translation suitability for a particular audience.

Apply Exceptions With a Written Reason

Do not tag every unfamiliar word because it looks foreign to the reviewer. Identify the actual passage and assess the relevant exception.

W3C's informative Language of Parts guidance explains that proper names generally need no explicit language change. It also notes that an individual word can require identification when no exception applies. Understanding Language of Parts.

Suppose the fictional English scope paragraph names a reviewer called Ana. Record it as a proper name. The example does not need a Spanish wrapper around the person's name.

The complete Spanish instruction is different. It is an ordinary instruction in another language. Calling it a quotation does not make it a proper name or a technical term.

When the editor cannot identify a phrase's language, record uncertainty. Ask a qualified language reviewer or the content owner. A guessed tag creates a new unsupported assertion.

Keep the exception reason beside the exact text. “Technical term” needs context. Record what the term refers to and who confirmed its use. Do not use the exception field as a place to dismiss every unresolved passage.

If the words change, reopen the decision. A product name followed by a full foreign-language sentence contains different review units. The name's exception does not resolve the sentence.

Copy the Language Review Worksheet

Use one record per text segment. This is a proposed editorial worksheet, not a required WCAG template.

Field Entry to preserve
Text segment Exact words and their location in the page
Actual language evidence Content-owner confirmation, language review, or unresolved question
Declared language Exact local attribute or no local declaration
Inheritance Nearest declaring ancestor and the effective value
Exception Applicable exception and reason, or none identified
Observed behavior Inspection result and any separately recorded assistive-technology observation
Owner Person responsible for wording, markup, or the next check

For the fictional quotation, enter the Spanish sentence as the segment. Enter author-specified Spanish as the example's language evidence. Enter es on the blockquote and inheritance through that element.

For the exclusion, enter English as the intended language. Enter no local declaration and en inherited from the root. Leave the exception field unused because no exception is needed.

For Ana, record the proper-name exception. Preserve the surrounding English sentence so another editor can see the basis of that decision.

Use a separate environment note for the page address, revision, date, browser version, inspection method, and reviewer. Repeating those details in every row makes the table harder to maintain.

Assign unresolved wording to the content owner. Assign an incorrect element boundary to the implementation owner. Keep the finding open until the relevant evidence returns.

Compare Markup Evidence With Observed Behavior

Inspect the root and each relevant ancestor in the browser's document tools. Compare the text with the approved version. Save an excerpt that includes the opening and closing boundaries.

Then examine the rendered passage. Read through the transition into Spanish and back into English. Record missing text, incorrect placement, or changes introduced by the content system.

If assistive technology is in scope, record its name, full version, browser, available voices, settings, navigation mode, and the passage examined. Distinguish continuous reading from examining an isolated link.

W3C notes that flattened accessible names can lose internal language distinctions in some modes. Spoken output alone cannot establish whether the underlying language markup is correct. Understanding Language of Parts.

Record the observed output without extending it to every browser or screen reader. If no speech test occurred, write “speech behavior untested.” A source inspection does not supply a pronunciation result.

In this fictional walkthrough, no assistive technology was run. The example's evidence consists of the stated markup and its proposed inheritance. A production review needs observations from the actual page and environment.

Retest the Changed Boundary

Suppose the implementation owner moves the exclusion outside the Spanish block. Retest the complete sequence: introduction, quotation, exclusion.

Confirm that the quotation retains its full instruction. Confirm that the exclusion retains the service boundary. Compare the effective language of each segment with the original worksheet.

Record the changed page revision. Preserve the earlier finding and the after-state excerpt together. A later reviewer should be able to identify what changed without reconstructing the conversation.

Use a bounded closing note: the specified segments now expose the intended declarations in the inspected page version. Leave unexamined dialogs, alternate pages, and other content states open.

Use the heading review when section structure also needs examination. Language attributes answer which language describes a passage. They do not establish whether its heading describes the contents.

Keep the words, boundaries, and evidence together.

Sources

Topic map: Accessible B2B websites

Articles in this cluster, then the 3 clusters that share the most topics with it.

This cluster: Accessible B2B websites

Neighbor: Technical SEO, crawling, and migrations

Neighbor: Customer and usability research

Neighbor: Topical authority and keyword strategy