Localization proxy language hack in Storyline 360: what can break?

Hello Favio_Trasi,

Thanks for laying this out so clearly. You’re asking all the right questions, and you’re right to pause before relying on a proxy-language approach.

While it’s technically possible to use a supported language as a container and manually replace the strings, that method isn’t officially supported and does carry some real risks, especially around language metadata, accessibility, and long-term maintenance. In particular, published output and screen readers may still treat the course as the proxy language rather than the actual one you’re displaying.

The underlying need here is the ability to define and use additional or custom languages in the Localization Add-on, including correct language tagging and accessibility behavior, without relying on workarounds. I’ve shared your feedback with our product team so they can see how important this is for real-world localization and compliance needs.

We really appreciate you taking the time to outline both the use case and the potential pitfalls so thoughtfully.