Resources · 30
QA multilingual content and complete user journeys
Check languages, alternates, forms, formats and RTL screens beyond translated body copy.
· 18 min
What this guide helps achieve
- Map versions
- Test tasks
- Check RTL and formats
- Arrange human review
Quick check
- Does declared language match content?
- Are alternatives reciprocal and relevant?
- Do errors and confirmations stay in the chosen language?
- Are dates, numbers and direction adapted?
- Who approves sensitive domain terms?
Step-by-step method
- 01
Map versions
Link each URL to its language, canonical and real alternatives. Do not claim a translation that does not exist.
Deliverable: URL, language and alternate matrix.
- 02
Inspect markup
Check HTML lang and passages in another language; test reciprocal hreflang relationships and final accessible URLs.
Deliverable: representative sample audit.
- 03
Replay journeys
Test navigation, search, form, validation, error, email, checkout or download in each priority language.
Deliverable: complete scenario and state captures.
- 04
Review meaning and formats
Adapt dates, times, numbers, currencies, units and examples. Test right-to-left reading, visual order and overflow where required.
Deliverable: format and direction defect list.
- 05
Review higher-risk copy
Ask a competent speaker with domain knowledge to check claims, specialist terms, conditions and error messages. Rank defects by effect on the decision.
Deliverable: recorded review and priority corrections.
- 06
Retest after release
Check changed pages and states, language switch behavior and version links after each content or component update.
Deliverable: regression log and owner.
Management indicators
| Indicator | What it measures | First action |
|---|---|---|
| Coverage | Essential journeys complete per language | Translate missing states |
| Alternates | Reciprocal accessible versions | Fix clusters |
| Quality | Blocking defects found in human review | Correct sensitive copy |
| Direction | RTL screens without order or overflow errors | Adapt components and CSS |
Common pitfalls
- Translating only the landing page
- Pointing hreflang to a non-equivalent page
- Leaving form errors in the source language
- Assuming machine translation validates a domain term
Frequently asked questions
Must every URL have a translation?
No. Declare only existing versions with equivalent content.
Does HTML lang replace hreflang?
No. lang describes document or passage language; hreflang connects localized versions for search engines.
How should a 15-language site prioritize QA?
Start with critical tasks, visited pages and high-risk copy, then extend testing to each version.
Official references
Continue exploring
Related analysis
