Keep useful prose translatable, mark exact names and identifiers narrowly, and verify that translated display text remains separate from stable application values.
A reader can translate a website in their browser without the publisher creating a new language edition. That helps people understand unfamiliar prose, but names, identifiers and technical instructions need closer attention. Compare the original and translated view before treating changed wording as a publication or application-data error.
Imagine a fictional parts directory with a supplier named Spring Works, a part identifier SW-204 and a category called Spring assemblies. A translated view should help readers understand the category while retaining the exact supplier and part identity. The objective is useful comprehension, rather than making every word immune to translation.
Establish which version the reader is seeing
Record the page URL, its original language, the browser or translation tool, target language and the changed passage. Ask whether the reader selected a publisher-provided language version or invoked automatic translation. Those are different routes, and the same-looking wording problem may have a different owner in each.
Compare a fresh original-language view with the reported translated view. Keep the surrounding sentence and relevant label, not only the isolated mistranslated word. For the directory, “Spring” could refer to the supplier or a mechanical component. Context matters to the intended meaning.
The WordPress translation workflow covers publisher-maintained content and interface strings. This guide concerns a reader-side transformation of a page that already exists, including how to preserve precise terms without replacing that editorial workflow.
Choose a narrow boundary for text that must stay exact
The HTML Standard defines translation modes through the translate attribute. Yes enables translation, no excludes it, and an omitted or invalid value inherits the parent’s mode. The boundary can cover an element and its descendants, so placement deserves deliberate review.
For the directory, propose protecting the supplier name and part identifier while leaving the surrounding explanation available for translation. A sentence such as “Order the replacement from Spring Works using reference SW-204” should still explain its action to the reader. Excluding the whole page would prevent that benefit.
Make a short inventory of content whose exact spelling serves identification: product codes, account handles, commands quoted for exact entry and specific names. Review each item individually. Ordinary descriptive prose should not be excluded just because its translation needs better context.
Treat translation control as a supported hint to test
MDN documents the translate attribute and cautions that recognition varies among translation systems. A no-translate boundary is useful markup, but it is not a universal promise that every browser, extension or external service will preserve the marked text.
Propose checking the tools actually relevant to the audience. Include the original-language view, a translated view and a return to the original. For the supplier name, compare spelling and capitalization. For the identifier, compare every character rather than relying on a quick impression that it looks similar.
Keep a way to refer to the original wording when helping a reader. Support instructions can ask for the original label alongside the translated one, without blaming the reader for using translation. If the site offers a reviewed language version, make that route understandable as a distinct option.
Keep machine values independent of visible labels
MDN’s option-element reference explains that an explicit value is the submitted option value; without it, the element’s text content supplies the value. That makes text-based identity an important implementation detail to inspect. It does not prove that a particular translator changes any given control.
Suppose the fictional directory identifies a category internally as CAT-18, while showing Spring assemblies to readers. Recommend keeping the stable identifier separate from the human-readable label. If the interface later uses a translated label, the application should still know which category the reader selected.
Ask the authorized developer to compare the selected control’s actual value and the resulting application record in a safe test environment. Do not infer that stored data changed merely because the visible wording changed. Conversely, a correct label does not establish that the application used the intended identifier.
| Content in the example | Intended treatment | Proposed evidence |
|---|---|---|
| Spring Works | Preserve the exact supplier name | Compare original and translated spelling |
| SW-204 | Preserve the complete identifier | Compare every character and copied text |
| Spring assemblies | Translate the explanatory label | Review meaning in its sentence and control |
| CAT-18 | Keep stable application identity | Inspect the selected value and test record |
Review dynamic updates after translation is active
A page is not always finished changing when translation starts. Propose repeating the directory journey after opening a details panel, changing a category and loading another set of results. Record whether newly shown text remains understandable and whether the protected identifiers retain their intended form.
Do not claim that all translation tools process later updates identically. The useful finding is narrower: what happened with this tool, this page state and this interaction. If the problem appears only after a category change, that sequence gives the developer something concrete to reproduce.
For amounts, distinguish meaning from formatting. The number and currency formatting guide covers representing an amount for the reader. An automatically translated sentence is not evidence that an amount, currency or application record has been converted correctly.
Preserve original meaning without hiding essential guidance
Review warnings and action labels in context, especially negation and terms with several meanings. For the directory, “Do not fit SW-204 to the older assembly” deserves a meaning check, rather than only checking that the part code survived. An intact identifier beside a reversed instruction is not a successful reading experience.
Where precision is essential, offer a reviewed explanation in the relevant language or an understandable route to assistance. Do not present automatic translation as a substitute for a qualified review of consequential instructions. Equally, do not make routine supporting prose inaccessible by protecting entire paragraphs unnecessarily.
The content-language declaration guide covers identifying the language of the original publication and mixed-language passages. Language identification and translation exclusion answer different questions; neither alone verifies the meaning of a translated instruction.
Define acceptance around comprehension and identity
Keep a compact record of the tested original page, translation tool, target language, protected terms, selected values and later updates. The exercises here are proposed; no particular browser translation result or application submission has been tested for this article.
Close the issue when readers can understand the explanation, identify the right supplier or item and complete the intended safe journey with stable application meaning. Preserve a clear original-language reference for support. The strongest outcome combines helpful translated prose with exact identifiers, rather than choosing one at the expense of the other.
Sources and verification
Editorial review 2026-10-15. Source check dates are recorded separately. Notes describe what each source supports and its limits.
View sources
- WHATWG: the translate attributeChecked Inherited translation modes and content left unchanged.
Limits: A standard mode is not a guarantee about every translation implementation. - MDN: translate global attributeChecked Translation control values and support caveats.
Limits: Automatic tools do not all honor the attribute. - MDN: option elementChecked Explicit submitted option values and text-content fallback.
Limits: It does not establish how an individual translator rewrites a control.