Hello,I have to be candid: I am extremely disappointed to see partially translated form fields and labels in a donor-facing form in 2026.

Please see the attached examples of our partially translated forms, where the English elements are highlighted in red and the French elements in blue.

From our perspective, this is not acceptable for a public-facing experience, especially in a bilingual Quebec context. It makes the organization look unpolished and, frankly, not as serious as it should.

I've actually had to build scripts to detect blackbaud iframes and repaint them with ?|&locale=fr-CA. Although that "duct-tape-fixes" certain cases, it won't work on shared external embeds or shared blackbaud forms hosted on your sites. This is why proper localisation is critical - not a "nice to have".

In all of the CRM, ERP, or MRP systems I have worked with, locale handling and translation matrix files are standard expectations. Seeing mixed-language labels, field names, and validation messages in production forms is therefore very difficult to justify.

Please advise on the proper escalation path and, more importantly, whether there is a concrete fix or workaround on the near horizon.

scr3.png

scr1.png

scr2.png

Attachments Open full size