Forum Discussion
language tag
- I am using Articulate 360 to build a course that teaches Russian. I need to be able to run the course with a screen reader. The issue I am having is how can I tag text in course that is russian so that the screen reader will read it in russian. I have the voices installed with JAWS and I have achieved this in html by using lang="ru". For example, <span>The following is Russian</span><span lang="ru" xml:lang="ru">Мой компьютер говорит по-русски</span> This reads correct in JAWs, the first part in english and the second part in russian. How can I "tag" text in Articulate to achieve the same results. Thank you.
Привет, Teresa!
To tell screen readers which language your course uses, let's select a language in your player properties:
- Go to the Home tab on the Storyline ribbon and click Player.
- When the player properties window opens, click Text Labels on the ribbon.
- Select a language from the Language drop-down list.
- Click OK.
These resources cover more details about how Storyline 360 handles the language attribute and how to use text labels:
- Storyline 360 Courses Have an HTML Language Identifier for Screen Readers
- Storyline 360: Customizing the Text Labels
Let me know if that helps!
Thanks for the information. However, what I am trying to achieve is the course is English but contains Russian words, sentences, etc. So only some text needs to have the Russian language tag, not the whole course. Is this possible?
Hello again, Teresa!
I appreciate you circling back with that clarification.
Right now, Storyline 360 doesn't support language tags for screen readers. Using the
lang="ru"attribute in HTML, exactly as you mention, is the best approach at this time. I'll still share your scenario with the right team and notify you of any pertinent changes!Have any updates been made (or upcoming plans to address) to add lang tags to either Storyline or Rise? Thank you!
Hi Alexandra,
Thank you for adding your voice for language tag support in Storyline and Rise 360. I don't have any updates regarding this feature request, but I informed our product team, and we'll let you know if any changes might help.
In the meantime, here's how we manage feature requests that we receive.
