Forum Discussion
We have Upgraded Project Text, but user still can not resize using Helperbird type tools
To meet accessibility standards, we are trying to address WCAG criteria 1.4.4: Resize text.
We have upgraded the project text, and loaded the free HelperBird Chrome extension. Nothing we seem to do will allow text expansion.
Please help!
Have you set the text to accessible by switching the variable to true?
Sorry, I didn't include all the previously taken steps.
To alleviate the "did you try restarting your laptop?" kind of guidance, here is what we have already done:
- Player/Features/Player Controls/Accessibility controls: Checked
- Player/Features/Player Style: Modern
- Player/Features/Menus & Controls: On
- Design/Fonts: Upgrade Project Text: completed
Setting the Built-In variable Player.AccessibleText does not solve the problem. The Accessibility controls from line 1 already gives the user the ability to toggle that variable from False to True.
All setting it to True does is to set the Accessible Text toggle in the On position instead of the Off position when the course begins.
The only text that can be resized is the accessible text, not sure if helper bird is supported
Take a look here for reference: https://articulate.com/support/article/Storyline-360-Accessible-Text
Like I said, we are not just starting out, we have followed everything that we could find on the Articulate Community, including using the exact same browser extension for testing.
Only trying to help, there was no mention of accessible text in the initial post
Hi, Jeff.
Thank you for reaching out!
How are you publishing your project when testing it with Helperbird (Review 360, web, LMS, etc.)?
We have a bug report where Accessible Text Doesn't Work in Review 360 (or on the local machine), so I want to make sure we're ruling that out for your scenario. If that's what's happening, can you upload the project to a web server or Learning Management System and try Helperbird again?
Let me know if that works!
Thanks for the reply Maria.
I will try it in SCORMCloud and let you know what happens.
Hey Maria, that did the trick, at least in SCORMCloud! One giant step forward. It's nice to know we had been doing it right, just not looking at it the right way :)
Next I need to try it inside our LMS. We are currently publishing to Web and the zipped folder is then referenced as an asset in a larger SCORM wrapped course.
(We have our own home-grown authoring tool and LMS, so sometimes we have challenges with an added frame layered on top of the Storyline frame.
Wish me luck!
PS - Any idea when the Review 360 might be fixed to allow testing there? Loading to the LMS is less efficient for testing.
Hi Maria,
I'm wondering if you could update on the above bug - has it been resolved yet?
Kind regards,
Craig.
No worries, I get frustration I am testing something at the moment and everything I try is not working.
For accessible text, I mean when the variable is set to true, when it is false the text is an SVG and not resizable, when true it is text.
The the only thing you need to ensure is that the text is visible in the focus order (can be checked in the Size and position dialogue)
It sounds like we are on the same journey. I find it interesting that you are working at the variable level rather than allowing the user to toggle it during the course. Is your audience more likely than not to use the reader? Is that why you set it to default as true?
We have an audience that primarily does not require accessibility assists, so our default is to leave the variable alone and just turn on the control for the user to decide.
I would prefer not to set it by default, however, some of my clients expect it to be fully accessible from launch.
I have in the past set it whenever the user presses the tab key or even ask them via a dialogue when they press tab.
Hi Alchemist Learning Transformed,
Thanks for checking in on this! The issue the author of the original post was experiencing ended up lying within their LMS. They were able to figure that out by testing their course in SCORM Cloud. Have you tested your course in SCORM cloud? It's an online LMS environment that can be used to figure out whether the issue is with the LMS or the Story file. If you test your course on SCORM cloud and it works perfectly, then your issue is likely LMS-based.
Looking forward to your response!
