Forum Discussion
Change HTML source language in Rise course
Dear community,
We developed an e-learning in Dutch using Articulate Rise and have gotten it tested on accessibility. One of the comments on the course was that in the HTML of the course the source language is shown as English ("html lang=en"), even though the full course is in Dutch. This results in screen readers selecting the language as English instead of Dutch which causes issues in, for example, wrong pronunciation of words. To overcome this users will have to manually select a different language on their screen readers.
I am wondering whether there is some kind of way to fix this and change the source language? Anyone experience with this?
Many thanks for your help!
Hello NadineBergmann-
Thank you for sharing what your learners are experiencing with your course.
Do you know when this course was created? We implemented an update in October to allow authors to select the source course language when exporting the training.
Hi Leslie,
Thanks for your answer. I assume you mean the option to select the source course language for translation/exporting xliff-files? That I have found, but would mean that I would have to translate the whole course (whereas the course is already in the "final" language)? Or am I overseeing something?
Thanks!Hi NadineBergmann-,
The option shared by Leslie is only to help translation apps recognize the source language of the text they are translating. That option doesn't automatically translate the entire course to a different language if this is what you are asking about. You'll still need to export the translation file, have it translated by a translation app or service, and then upload it back to the Rise 360 course to translate it.
Hi JoseTansengco, thanks for your reply. I don't need a translation of the course. The course is made in Dutch and should remain in Dutch. The issue is that in HTML the source language is shown as English (lang=en) and that doesn't help screenreaders/accessibility when working in Dutch.
The question is whether there is some way to change the source language in HMTL.
Hi NadineBergmann- & JudyNollet!
Thank you for bringing this to our attention!
I was able to replicate the same behavior you shared. When publishing a Rise 360 course that has been translated to a language other than English, the HTML source language tag, remains in English. I understand how this could be problematic for those using screen readers, so I've filed this behavior as a bug in Rise 360. I've linked this discussion to the bug report so we can notify you as soon as a fix is in place.
Have a great start to your week!
Hi StevenBenassi,
Thanks for this! May I add that it would be great if not only after translating, but also already in the export you could indicate the language. This since not every course is produced in English first, but in another language (and wouldn't need translation) hereby also considering the option to have labels in different languages.
Thanks!
NadineBergmann : You have discovered a "bug" in how courses are published.
I just did a test in which I set the Rise Labels to German, as would be done for a course in German. Yet when I published it, it still shows html lang = "en" (indicating the page is in English). Which, as your question stated, is a problem, because a screen reader would say words based on English pronunciation instead of German.
At this point, that means you'll need to open your HTML source files with a text application, and then edit them to change the language from English to Dutch.
By the way, I would have done my testing in Dutch, but the Labels are only available in English, French, German, and Spanish.
JoseTansengco : The publishing settings should have a way to indicate the language to be used in the HTML header tag. And that should be a priority.
Judy, unfortunately if you change the html so lang="nl", once the course loads it changes back to lang="en" so editing the html in a text editor is not a solution anymore, I believe it used to be but there must have been a recent change to prevent this.
Although you could add lang="nl" to the <body> tag, it stays. But I'm not sure how this will affect translation software.
