HTML5 - Using variable as Checkbox label - publish layout issue


I want to create a checkbox interaction and publish to HTML5. The checkbox labels are variable text. In the Flash version the text looks perfect but the HTMl5 version has the text overlapping the checkbox and it jumps on hover. Basically it looks terrible. I've attached an example story file. Has anyone come across a fix? I can get round this issue by having the variable text in a separate text box and aligning it with the checkbox but it's not ideal. Has anyone come across this and is there a solution I'm missing?

Thanks :-)

6 Replies
Steve  Galway

Hi Ashley,

Thanks for getting back to me. I tested the file on SCORM Cloud using Chrome Version 46.0.2490.86 m, Firefox Version 38.4 and IE v11. I get the same problem in all browsers. I have also tested using a local web server. The same file looks perfect when using the Flash version. 

Were you able to replicate the problem using the file I uploaded?

Many thanks


P.S. I decided to change my profile name to the slightly more professional 'Steve G' :-)

Ashley Terwilliger-Pollard

Hi Steve,

I do see the same thing after testing the HTML5 output in Chrome as we don't support HTML5 in Firefox or IE as detailed here.  I see that this issue was recently reported to our QA team for review as well and I'll include this thread in the report filed with our team. I don't have a time frame to offer in regards to when I'll hear back from them, so in the meantime I'd suggest to look at not using variable references as a part of the answer choices or ensure your users are accessing the Flash output. 

I'll be in touch once I have any additional information to share in this thread. 

Ashley Terwilliger-Pollard

Certainly Steve - and we'll keep you posted here as I mentioned. If you're not using it as a standard question type - perhaps instead you could look at separating the text box from the radio button? That way you could at least disable the hover behavior that moves the question text and play with the text spacing a bit further? Not sure if that's a viable workaround for you - but figured it was worth mentioning since we're unable to offer a timeframe in regards to a fix.