Start with the visitor language, not only the site default
WordPress has a site locale, but multilingual sites often need page, visitor, or plugin-level
language context. WPML exposes the current language through its documented
wpml_current_language hook, which lets compatible code read the language that WPML
has selected for the current request.
ACookies uses that kind of active site-language signal when it is available, then falls back to the visitor browser language and finally to the configured default. That keeps the banner closer to the page language without forcing every site into one detection method.
Translate the decision, not just the buttons
A multilingual banner needs clear localized wording for the purpose of storage, the available actions, the categories, and the policy route. If the page is Swedish but the preference panel explains analytics in English, the visitor may not have enough context to make an informed choice.
The European Commission describes valid consent as specific, informed, freely given, and based on a clear affirmative action. For a multilingual WordPress team, that standard turns translation quality into a practical consent issue: vague or machine-like copy can make the choice harder to understand even when the interface has the right buttons.
Use WPML-aware behavior where the site already depends on WPML
On WPML sites, the consent banner should follow the language the visitor is actually seeing. That includes the first banner layer, the customization panel, and links to cookie policy pages. If a site publishes separate policy pages per language, the banner should point visitors to the matching page rather than a generic default.
ACookies includes visitor-facing defaults for 25 locales, editable language overrides, WPML-aware language matching, and language context in consent records. Those claims match the local product configuration and the plugin language catalog in this repository.
Right-to-left languages need layout support, not only strings
Arabic, Hebrew, and Urdu are right-to-left locales in the ACookies language catalog. The banner and policy block need the correct text direction so sentence flow, buttons, category lists, and form controls feel natural. Treat this as a layout requirement, not a translation afterthought.
The fallback path also matters. If a requested language is not enabled, use the configured default instead of showing a partial or mixed-language interface. Mixed copy is harder to review, harder to support, and easier to misunderstand.
A practical multilingual banner review checklist
- Open every language version in a fresh browser session and confirm the banner language matches the page.
- Check accept, reject, customize, category names, and saved-choice messages in each enabled language.
- Confirm policy links point to the right translated or intentionally shared policy page.
- Test right-to-left languages for direction, focus order, button layout, and mobile spacing.
- Reject optional categories and verify optional scripts remain blocked or limited according to the configured mode.
- Review consent records to confirm language, policy version, timestamp, and categories are retained as expected.