1. Define what each version should offer
Start with a page matrix: home, services, detail pages, articles, contact and downloadable documents. For each page and language, record an owner, translation status, reviewer and planned address. Add menus, error messages, alternative text and sharing titles to the inventory. A translated button is insufficient when the document it opens remains incomprehensible.
Separate language decisions from market decisions. Confirm the contact details, opening hours, units and offers actually available in each version of your project. When a page is missing, agree on an explicit message and destination. Mark the gap in the matrix instead of claiming its translation is complete. This matrix is a coordination tool proposed here, rather than a standards requirement.
2. Review translations in context
Prepare a short glossary of business terms, service names and recurring actions. Ask someone able to judge meaning in the target language to review the copy. Explain the context of each button or message: who reads it, when it appears and what happens next. Avoid approving only a spreadsheet of isolated sentences.
In the preview, look for long headings, clipped buttons, images that still contain text in another language and forgotten downloads. In a fictional example, “Request a quote” should lead to a step consistent with that request in each version. Record intentional differences so that reviewers can distinguish them from translation omissions.
3. Keep journeys available across languages
Google recommends distinct URLs for language versions and links that let visitors choose. It advises against automatic redirects based on an assumed language. Plan destinations that people can open directly.
For acceptance, start on a specific service page, change language and check the destination. As a project rule, propose preserving the equivalent page whenever it exists. Repeat by opening its address directly and using the browser’s Back button. Also test the documented missing-translation case: visitors should understand where they have arrived before continuing.
Source : Google Search Central — Managing multilingual sites
4. Separate language, direction and alternate versions
W3C recommends declaring the main language with lang on the html element. For a predominantly Arabic page, dir="rtl" separately defines the base direction. A language declaration alone does not set direction.
For alternate versions, Google says each hreflang set should include the page itself and its variants, using complete URLs and reciprocal links. Ask the team to check mappings between equivalent pages. Keep two separate pieces of evidence: visitors reach the right content, and annotations name the right addresses. Neither demonstrates a position in search results.
Source : W3C Internationalization — Declaring language in HTML · Source : W3C Internationalization — Structural markup and right-to-left text · Source : Google Search Central — Localized versions of your pages
5. Check formats without changing values
Intl.DateTimeFormat formats dates and times using a locale and options, including a time zone. Intl.NumberFormat formats numbers, including currency amounts. These tools present values; they do not convert currencies.
Prepare a few fictional values shared by all three versions: an appointment near midnight, a potentially ambiguous date and an amount with decimal places. Agree on the expected currency, rounding and time zone before testing. Compare the meaning of the displayed values, not just punctuation. Translating a page into English does not mean automatically replacing dinars with another currency.
Source : MDN — Intl.DateTimeFormat · Source : MDN — Intl.NumberFormat
6. Read Arabic on real screens
W3C recommends logical CSS properties based on start and end to ease direction changes. This foundation still needs a rendered-page check.
On a phone and then a desktop, review a long heading, table, email address, number and Latin reference inside an Arabic sentence. Ask an Arabic reader to check their meaning and punctuation. Navigate menus and buttons with the keyboard. Avoid a blanket instruction to flip every image: identify the purpose of arrows, logos and illustrations, then approve each visible case.
Source : W3C Internationalization — Structural markup and right-to-left text
7. Keep acceptance evidence for future updates
Freeze the content version to be reviewed and use the checklist below as a starting point. For each defect, save the language, address, device, steps, expected result and screenshot. After correction, repeat the scenario and pages sharing the same element. This targeted check replaces neither a full accessibility audit nor a legal review of the content.
After publishing, open the real addresses in all three languages and recheck the relevant article or service lists. When source copy changes, flag translations for review in the matrix and assign that review. Keep the evidence and approved version so that the next update can repeat a known journey instead of relying on a general impression of consistency.
An acceptance checklist to adapt
| Scenario | Expected result | Evidence to keep |
|---|---|---|
| Complete translation | Meaning and actions reviewed in every language | Copy version and approval |
| Specific page → another language | Equivalent page or explained absence | Starting and destination URLs |
| Direct opening and Back | Clear language and context | Steps and screenshot |
| Fictional date and amount | Agreed values, currency and time zone | Expected and displayed values |
| Arabic on a phone | Readable mixed text and usable controls | Screenshot and language review |
| Real publication | Approved content at the correct addresses | URL and check date |
Frequently asked questions
Must every language launch at the same time?
Decide according to the journeys that are actually ready. If a version is unavailable, say so clearly and provide an understandable destination. Do not present partly translated content as a finished version.
Is machine translation enough for acceptance?
It can provide a draft, but this method includes a meaning and journey review by someone competent in the language. In particular, have offers, conditions and expected actions checked.
Does checking hreflang replace acceptance testing?
No. It checks declared relationships between addresses. You also need to open pages, read their content and check navigation, formats and layout.
Prepare your next content batch
Choose an important page, complete its matrix for the planned languages and have its integrated journey reviewed. Use this first batch to agree on a delivery method with your team.
Sources and scope
Sources consulted on 31 October 2026. Organization recommendations are cited in the relevant sections; the matrix and acceptance scenarios are editorial workflow suggestions.
