Hey there, Paul. In Storyline 360 (and 3), text is no longer rendered as an image. However, we've disabled the "copy" function from the slide output. I've asked our developers for some clarification on the reasoning behind that decision.
While your at it perhaps you can also ask them why we cannot use 'web fonts' like we normally do for html5 development if that's the case. I get an awful lot of queries from backend IT guys about the fonts being turned into vectors/png's etc ... if its html5 text then it should be held in the .html files etc??
Clients could then edit the text themselves to a small degree.
Hi again, Paul. I am able to provide context around the way the slide output works in terms of copying text.
We currently have both Flash and HTML5 output available as publishing options. Ideally, we want users who access either output to have a consistent experience with slide content. Because Flash output must render text differently than HTML5, we opted to disable the copy functionality in HTML5 to preserve consistency.
Other considerations we’ve taken include intellectual property concerns and trigger functionality. Intellectual property has especially been important to our users, and we’d have to ultimately be aware of the impact on course authors if we made text (and other course elements) available from the output.
I can also appreciate the fact that you’d like to make minor modifications as easy as possible for your clients post publish. We are really shy about ever recommending changes to the published output, and we just can’t support it. The best practice will always be to make edits in the authoring environment and republish the course.
Hi Crystal, Ah i see your concerns regarding IP. However, it would be nice to have that checkbox functionality available to the developer and have a 'true' HTML5 application.
The copy and paste feature really should be available for accessibility reasons. Visually impaired students need to have this ability and have requested that ability. Seems like this should be accommodated.
The ability to copy and paste is really important for accessibility reasons as we have recently discovered. Being more accommodating to the needs of all is very important. If copyright is not an issue, why not allow a toggle/feature that allows it to be turned on and off as needed. I really want to stress how important the copy and paste ability is for visually impaired people who need to be able to copy that text and paste in other tools to allow for learning. We have recently learned that some limitations of the player are that students are not able to expand it large enough making the copy and paste feature even more important; Notes tab cannot be made larger and the limited space and scrolling in the notes tab is really inefficient. The inability to copy and paste from notes is also a problem. We were delighted that Storyline was touted as accessible, but now we are finding out that in this situation it is not. Please consider this seriously as an accessibility issue. Also, as Flash is going away by the end of this year, the need to have consistency between Flash and HTML5 will go away.
I can see that you've shared a bit more information here and you specifically mention the player.
Do you know what version of Storyline you're using?
You can check by going to: Help > About Articulate Storyline
I'd also be interested to know if you're using the classic or modern player.
It sounds like you may have a specific example and if you'd like our team to take a look, then with your permission, please share your project file with our support engineers to investigate what's happening. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.
9 Replies
Hi Simon,
It renders it as an image.
Hi Mark,
Can you tell us why this is pls? Lots of my clients are asking why the text is not selectable as per normal html standards etc...
I do think if articulate is saying it publishes as HTML5 then it should actually be html. Turning text into images is a real pain in the butt.
Hey there, Paul. In Storyline 360 (and 3), text is no longer rendered as an image. However, we've disabled the "copy" function from the slide output. I've asked our developers for some clarification on the reasoning behind that decision.
I'll update this discussion as soon as I can!
Thanks Crystal.
While your at it perhaps you can also ask them why we cannot use 'web fonts' like we normally do for html5 development if that's the case. I get an awful lot of queries from backend IT guys about the fonts being turned into vectors/png's etc ... if its html5 text then it should be held in the .html files etc??
Clients could then edit the text themselves to a small degree.
Hi again, Paul. I am able to provide context around the way the slide output works in terms of copying text.
We currently have both Flash and HTML5 output available as publishing options. Ideally, we want users who access either output to have a consistent experience with slide content. Because Flash output must render text differently than HTML5, we opted to disable the copy functionality in HTML5 to preserve consistency.
Other considerations we’ve taken include intellectual property concerns and trigger functionality. Intellectual property has especially been important to our users, and we’d have to ultimately be aware of the impact on course authors if we made text (and other course elements) available from the output.
I can also appreciate the fact that you’d like to make minor modifications as easy as possible for your clients post publish. We are really shy about ever recommending changes to the published output, and we just can’t support it. The best practice will always be to make edits in the authoring environment and republish the course.
I know it’s a functionality that you’d prefer, so I’ll submit a feature request on your behalf. Here’s how we handle feature ideas from you.
Thanks again for asking and sharing your thoughts!
Hi Crystal, Ah i see your concerns regarding IP. However, it would be nice to have that checkbox functionality available to the developer and have a 'true' HTML5 application.
Thanks.
The copy and paste feature really should be available for accessibility reasons. Visually impaired students need to have this ability and have requested that ability. Seems like this should be accommodated.
The ability to copy and paste is really important for accessibility reasons as we have recently discovered. Being more accommodating to the needs of all is very important. If copyright is not an issue, why not allow a toggle/feature that allows it to be turned on and off as needed. I really want to stress how important the copy and paste ability is for visually impaired people who need to be able to copy that text and paste in other tools to allow for learning. We have recently learned that some limitations of the player are that students are not able to expand it large enough making the copy and paste feature even more important; Notes tab cannot be made larger and the limited space and scrolling in the notes tab is really inefficient. The inability to copy and paste from notes is also a problem. We were delighted that Storyline was touted as accessible, but now we are finding out that in this situation it is not. Please consider this seriously as an accessibility issue. Also, as Flash is going away by the end of this year, the need to have consistency between Flash and HTML5 will go away.
Hi Susan,
I responded to a similar post of yours here.
I can see that you've shared a bit more information here and you specifically mention the player.
Do you know what version of Storyline you're using?
You can check by going to:
Help > About Articulate Storyline
I'd also be interested to know if you're using the classic or modern player.
It sounds like you may have a specific example and if you'd like our team to take a look, then with your permission, please share your project file with our support engineers to investigate what's happening. You can share it privately by uploading it here. It will be deleted when troubleshooting is complete.
This discussion is closed. You can start a new discussion or contact Articulate Support.