65 Replies
Leslie McKerchie

Hi everyone,

Thank you all for continuing to share the crucial need for creating accessible content for all learners. While more work remains, we're at a point where we're confident the job done so far delivers meaningful real-world improvements for learners with accessibility needs.

I've included links below where you can find all the details on what this means for Storyline 360 Update 36:

You'll also see our general FAQ on accessibility in Articulate 360 tools here.

This release makes it significantly easier for those users to perceive, operate, and understand content published with Storyline, while opening up more choices of the browser, assistive technology, and devices for the first time. Learners will benefit from the vast majority of these improvements, even when the course author is not designing their course for accessibility. 

If you have any questions or concerns, let us know here or reach out to our Support team. We know there is more to do, so we'll continue to keep you posted about future releases.

John Morley


I have found that this is a function of increasing the resolution up from the default 720 x 405, which makes items on the player small, so I increased the Player font size (see attached) to 150% and that is what sent the button off the bottom, because the enclosing dialog box does not scale  appropriately with the higher resolution.

By taking the player font size down to 120% the result is acceptable, although not all the best. Also, taking the resolution down closer to the default also helps.

I don't know if this is your situation, but it was my work around.

Bob Stryker

Thank you John. That's great information. 

Just a side comment: It's unfortunate that 720 by 405 pixels is considered default. That low a resolution doesn't allow images to scale up well for people with large monitors. 

If anyone at Articulate is monitoring this conversation, I vote for enhancing user control over the size, look and feel of the popup dialog boxes in the Player Text Labels panel. At the very least, they shouldn't allow the OK button to overflow the dialog box.

Tom Dalgaard Petersen

You got a point Bob, and I do not see any way around it. To put it mildly, I see it as a design flaw. Who want to have two different designs in their feedback...

It would be possible to correct by puzzle a solution with JavaScript. But I consider that to be waste of good working hours.

Maria Costa-Stienstra

Hi, John.

We appreciate your patience while our team investigated this.

I am happy to share some great news! We fixed the issue you reported where:
HTML5: Classic Player tab label is cut-off if Player > Colors & Effects > Player font size is set to more than 120%

Be sure to install the latest Storyline 360 update (Build 3.49.24347.0) to take advantage of all the recent features and fixes. 

If the problem happens again, please let us know, or you can always work directly with our support engineers here.

Kay Fenton

I am also frustrated at the limited options for customising the invalid answer.  While I can play around with the colours I cannot fix the OK button text which is not centred within the button border - as shown in the attached.  While its a small matter my client is asking for it to be centred!  Is this possible?