Forum Discussion
Accessibility - Publishing Storyline to Word as text only
Big caveat to Joe's suggestion: the format of the Word file exported for translation includes lots of extraneous text, such as labels and duplicate text when a object has multiple states. So it won't make any sense to a program that just reads the text.
Unfortunately, the way to get a good "script" of the course into Word is to copy and paste the text from the slides into the Word file.
For accessibility, it seems like it'd be easier to have a screen reader go through the published course.
Hi is there any update on this with the new "Localization" option instead of "Translation"? I'm trying to do the same thing (export the storyline as a word doc to use as a transcript for accessibility), and I no longer see the option to export to Word. Thanks!
- SarahFlynn2 months agoCommunity Member
Or is there a better way to have screen readers be able to access a Storyline block within a Rise course?
- JudyNollet2 months agoSuper Hero
The option in Storyline to Export to Word is available under File > Localization > XLIFF/Word Translation.
As I mentioned in a previous reply, exporting the text this way results in a document with a lot of extra info, which is needed so translated text can be properly imported. In other words, it'd be a mess to listen to a screen reader go through that file. However, you could use it to copy and paste text as needed.
As per the User Guide, a Storyline block should be accessible if the Storyline file it was made from is accessible. There's more info about that here: https://www.articulatesupport.com/article/Rise-Use-Storyline-Blocks-to-Embed-Storyline-360-Courses
If you have additional questions, I suggest you start a new discussion that focuses specifically on the accessibility of Storyline blocks in Rise. That will increase your question's visibility to those who have that expertise. It will also make it easier for others to find the discussion when they have a similar question.
Related Content
- 10 months ago