The commissioning decision
An equipment distributor needs English and Chinese explanations while retaining the same model code. A translation pass changes a code or brand phrase, making the enquiry harder to match to the catalogue. Define a small protected-term register with the exact text, location and exception owner instead of marking an entire page untranslatable.
Source and claim boundary
The translate attribute declares whether an element’s text and translatable attributes should be localised. translate=no expresses an exclusion, but actual translation-tool behaviour still needs testing. MDN · Checked 16 October 2026.
Filled synthetic acceptance cases
Synthetic teaching data, not client records. Review the inputs and expected outcomes before running the isolated browser exercise. On narrow screens, scroll the table.
| Input | Check | Expected |
|---|---|---|
| Model RX-02, translate=no | DOM declaration | Excluded term marked |
| Description, translate=yes | DOM declaration | Localisable text marked |
| Unmarked child inside translate=no | Inheritance policy | Review inherited exclusion |
How to verify beyond appearance
- List model codes and brand terms with approved wording in both languages.
- Inspect declaration boundaries in the fixture; this is not a translator simulation.
- Run the actual selected translation workflow and compare protected strings and surrounding explanations.
Interpret the result
The fixture confirms which elements were marked, not that a search engine or AI will preserve them. Overbroad exclusion can leave useful customer instructions untranslated. Keep a before-and-after term register and flag any changed code for human review. This is a content governance task, not permission to alter existing frozen bilingual pages.
What this does not prove
No machine-translation service, ranking guarantee or AI-answer claim is tested. Tool-specific behaviour and terminology approval remain separate.
Runnable fixture and handover record
Open the browser acceptance fixture · Read the test source。The fixture creates temporary elements with synthetic values inside the browser. It reads no account, uploads no file, and sends no email or form. Record the browser version, check name, observed value and pass state. Keep real integration evidence separate: a local pass is not a live delivery result.