Test a multilingual website in two layers: first verify that its code and design support different scripts, locales, and text directions; then test each translated version for working features, usable layouts, accurate language, and market fit. Automated checks can find many technical and visual defects, but qualified language reviewers are needed to judge meaning and cultural appropriateness.
Internationalization testing vs. localization testing
Internationalization testing checks whether a product can support different languages, scripts, locales, time zones, units, and market conventions. Localization testing checks whether a particular localized version works well for its target language and market. It covers functional parity, visual quality, linguistic accuracy, cultural fit, and market-specific risks such as local features, legal requirements, audiovisual content, and support access. Addressing internationalization issues first makes localization easier to validate. Microsoft’s internationalization guidance and localization guidance describe these complementary stages.
Build a test plan for each language and market
- Define the target matrix. List each language and locale, writing system and direction, supported browsers and devices, critical user journeys, and market requirements. “Spanish” or “Arabic” alone may not specify regional formats or behaviors.
- Make the source content translation-ready. Prefer clear, consistent wording over slang and culture-specific references. Keep text separate from presentation in CSS, and do not build sentences by concatenating separately translated fragments: word order can differ by language.
- Test internationalization foundations. Verify UTF-8 handling through pages, forms, servers, and storage. Enter non-Latin and mixed-script data. Check locale-sensitive sorting and capitalization, dates, times, units, names, addresses, and phone formats. Confirm document language, direction, fonts, and text rendering. See Microsoft’s internationalization test guidance and the W3C Internationalization Quick Tips.
- Use pseudolocalization before translations are ready. Pseudo-translated text can expose strings that are not available for translation, layout clipping, text expansion, and fragile concatenation. For right-to-left (RTL) targets, a pseudomirrored interface can reveal layout assumptions. Test pseudo-localized versions both functionally and visually; they do not establish that a real translation is accurate or appropriate. Microsoft’s localization guidance discusses these checks.
- Run the same critical journeys in each real locale. Where the test suite is sufficiently globalized, reuse automated cases across versions. Check navigation, language switching, search, account creation and access, forms, error states, checkout, and other tasks that matter to the product. Confirm that each locale can complete the same intended task.
- Inspect localized pages at different viewport sizes. Check narrow and wide layouts, wrapping, line breaks, buttons, menus, tables, validation messages, font coverage, and text embedded in images. For RTL pages, check direction, mixed-direction content, and whether layout mirroring preserves usable navigation and controls. The W3C Quick Tips call out likely translation expansion, RTL direction, cultural suitability, and text in graphics.
- Arrange language-aware review. Have reviewers familiar with the target language and audience assess terminology, grammar, meaning in context, formatting, imagery, humor, and culturally or politically sensitive content. Automated checks can flag some visible issues; they cannot determine whether a translation is idiomatic or suitable for its audience. Microsoft treats linguistic validation as a distinct part of localization testing: How to perform localization testing.
- Record defects by locale and release. Include the browser and device, locale, reproduction steps, expected and actual behavior, a screenshot or text example, severity, and whether the problem affects one locale or several. Re-run affected journeys after fixes and preserve a regression set for supported versions.
High-value checks for multilingual sites
- Encoding and input: Confirm that pages, forms, APIs, and storage handle the scripts the product supports. W3C recommends UTF-8 and declaring the encoding; the Unicode Consortium’s web FAQ also recommends UTF-8 for pages and consistent encoding for multilingual databases.
- Language and direction: Check the document language, language changes within a page, text direction, and bidirectional text. The
dirattribute can express direction in HTML; test mixed content such as names, numbers, URLs, and punctuation rather than assuming a whole page behaves uniformly. - Locale-specific formats: Use realistic names, addresses, dates, numbers, times, phone numbers, and units. Check both display and input validation against the target market rather than carrying source-market assumptions into every locale.
- Text growth and typography: Test unusually long and short strings, wrapping, control sizes, line height, and script-specific glyphs. Check text inside images too; keeping text as a separate layer makes localization more manageable. The W3C Quick Tips notes that English and Chinese text will almost certainly expand in translation.
- Complete, translatable messages: Verify that status and error messages are available for translation and appear in the user’s language where appropriate. Avoid assembling user-facing sentences from fragments, since languages may place words in a different order.
- Market fit: Review imagery, examples, symbols, colors, payment and contact paths, legal constraints, and locally expected workflows for the audience and market.
Test Arabic and other right-to-left languages
Test an actual RTL locale, not only a mirrored mockup. Check text direction and alignment, navigation and control placement, mixed-direction strings, punctuation, numbers, URLs, and form entry. Confirm that fonts contain the required glyphs and that text remains readable when it wraps. An RTL page can contain left-to-right text, so inspect realistic combinations such as a person’s name alongside a URL or number. Use HTML direction metadata appropriately and check language metadata as well; W3C’s Quick Tips cover language and direction, while its Internationalization Best Practices for Spec Developers provides further guidance.
Tools: standards checks, browser tests, and human review
W3C Internationalization Checker
The W3C Internationalization Checker is a free online service that reports settings such as encoding, language declarations, and text direction. It considers markup and HTTP headers and offers warnings and suggestions. Use it as a page-level diagnostic, not as proof that translations, user journeys, or market choices are correct.
W3C i18n test suite
The W3C i18n test repository contains standard HTML and interactive tests for internationalization features in web specifications, as well as exploratory checks involving browser and font support. Some tests that depend on server settings, including encoding and language checks based on HTTP headers, remain on W3C-hosted pages. The repository describes tests as potentially educational and exploratory as well as pass/fail checks.
Automated browser checks and screenshot review
Automated browser tests are useful for repeatable functional checks across locales and for visual comparisons at set viewport sizes, provided selectors and content are robust. They cannot judge idiom, translation quality, cultural fit, or whether the chosen regional variant is right. Microsoft recommends automation when tests are sufficiently globalized, with manual validation where coverage is incomplete: localization testing guidance.
Rank #2
- Keep track of everything from attendance to test scores
- Spiral bound
- Measures 8-1/2" x 11"
For repeatable visual review, capture the same localized page at the same viewport and compare the result across locales and releases. ScreenshotNeo is a website screenshot API and MCP server; it can capture a page as PNG, JPEG, WebP, or PDF. Its clean-shot options accept cookie or consent banners and remove known consent platforms, newsletter popups, and chat widgets before capture, with each step configurable. Treat screenshots as evidence for visual inspection, not as a substitute for linguistic review. Details are at ScreenshotNeo.
Choose coverage that matches the risk
Before selecting a test approach, check whether it covers internationalization foundations or only translated content; functional parity or visual and linguistic review; actual target locales, including RTL and mixed direction; browser, device, and viewport coverage; response headers as well as markup; repeatable release-pipeline runs; and access to qualified target-language reviewers. Standards-oriented diagnostics can help with technical settings, while real translation and market validation require additional checks.
Or skip the browser setup
For a quick, repeatable page capture during visual localization checks, call ScreenshotNeo’s API. This cURL example saves a WebP screenshot of the URL being tested; replace the target URL with a localized page and supply an API key.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots. Sign up free for 1,000 screenshots a month, no card required.
Troubleshoot common localization test failures
- Accented or non-Latin characters appear as boxes or question marks: Check that the page declares UTF-8 and that encoding remains consistent through form submission, server processing, APIs, and storage. Verify the selected font includes the required glyphs. Use the Unicode Consortium FAQ and W3C Quick Tips as references.
- Text is clipped or controls overflow: Test longer translations at the affected viewport, then adjust flexible layout, wrapping, sizing, or line height. Do not rely on pseudo-localization alone; verify with actual target-language text.
- An RTL screen looks mirrored but reads incorrectly: Inspect the real locale with mixed-direction values and verify direction metadata, punctuation, numbers, URLs, navigation, and form behavior. Mirroring is not a substitute for testing bidirectional content.
- A sentence is grammatically broken in one language: Replace concatenated fragments with complete translatable messages that allow translators to control word order and context.
- Automated tests pass but users report awkward or inappropriate wording: Add qualified linguistic and cultural review. Functional success and visual cleanliness cannot establish translation quality.
- A page-level checker reports a warning, but the interface appears fine: Inspect the relevant markup and HTTP headers, then test the actual user journey. A checker is a diagnostic, not a full localization verdict.
FAQ
Can pseudolocalization replace translation testing?
No. It helps find implementation and layout weaknesses before translations are ready, but it cannot verify the accuracy, idiom, or market suitability of real localized content.
Does the W3C checker validate every page in a multilingual site?
It reports internationalization settings for the page checked. It is an initial diagnostic, not a complete site-wide functional, visual, or linguistic test.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallQuick Recap
Best Value
Rank #4
- Book - 1, 000 books to read before you die: a life-changing list (1000 before you die)
- Language: english
- Binding: hardcover
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
