Keep the donor’s chosen language through confirmation

A multilingual donation form should let a donor understand the giving choice, correct an error, and read the confirmation in the language they selected. Check that whole path before publishing a translated campaign page.

Choose the languages your team can review and support. A translated headline alone does not establish that the embedded form, payment step, or follow-up text uses the same language.

List every surface the donor encounters

Map the route from the campaign link to confirmation. Include the campaign explanation, amount and frequency choices, custom questions, required-field errors, payment controls, submit button, result page, and receipt preview.

For each surface, record who supplies the text and how the language is chosen. Your website may control the first page while a fundraising provider controls the form and a payment provider controls another step. Those boundaries matter when a translation setting applies to only part of the route.

Donorbox's supported-language FAQ describes its donation-form translations and browser-language detection. This is a specific provider capability, not evidence that your own platform translates every donor-facing surface automatically.

Preserve the donor's explicit choice

Give the visitor an understandable way to choose another supported language. Browser settings can provide an initial suggestion, but a donor may want a different language for this task.

Use each language's own name in the selection. W3C's language-navigation guidance recommends labels such as “français” for French, so readers can recognize the destination language. Ask your page maintainer to confirm that the control is usable with a keyboard and clearly labeled.

Check whether switching languages preserves the selected campaign, amount, frequency, and other relevant choices. If the form must restart, explain that before the switch. Do not let a language change silently move a recurring selection back to one-time giving or change the campaign destination.

Use the embedded-versus-hosted page guidance to choose a route your team can inspect reliably. A separate hosted page may be simpler to review if you cannot control language behavior inside the embed; verify the actual experience before deciding.

Review the meaning of the giving choices

Have someone fluent in the target language review the complete route. Ask them to explain the amount, frequency, fees if present, and next action back to you. If their explanation differs from the intended choice, revise the text or configuration before release.

Pay particular attention to terms that change the commitment. “Monthly” must remain visibly connected to the amount. A button should make the submission action clear. A pending-payment message should not become a translation that implies completion.

Review custom questions as well as system labels. A provider may translate its built-in controls while leaving your campaign description or organization-written text untouched. Keep the same necessary fields across languages unless there is a documented reason for a difference.

Check errors and payment transitions

In a supported preview or test environment, leave a required field empty and use a safe invalid value. Read the resulting message and confirm that the donor can find the relevant field and correct it.

Inspect mobile wrapping, longer labels, and any right-to-left layout your selected language requires. Ask the technical owner to verify the page's declared language. W3C's HTML language guidance recommends declaring the default text language and marking language changes within the page.

The existing accessible donation-form checks can help with keyboard navigation, understandable errors, and labels. Language review adds another question: can the donor understand those instructions in the selected language?

Inspect confirmation separately

Do not assume the form's language setting also controls receipts and other notifications. Donorbox's receipt-language documentation distinguishes receipt-template text, translated variables, and a default communications-language setting. The exact rules belong to that provider; check your own configuration for equivalent boundaries.

Use a rendered receipt preview or synthetic data to confirm amount, frequency, status, organization name, and help route. Keep real donor messaging out of the review unless separately authorized. Name who can answer a donor's question in each supported language, or state the available support language plainly.

Retest the affected route when a template, form provider, or payment step changes. The release decision should rest on a complete reviewed language path, with any untranslated boundary visible to the team and the donor.