How to make the glossary work in HTML5?

[kayleenh71]

I've seen several posts from others who have had issues with the glossary in HTML5, but I haven't found an answer that fixes my problem. I have a non-responsive eLearning project that I need to publish as HTML5.

I inserted the glossary widget on a slide at the end of my project, and I have a button on the master slide that jumps to the slide with the glossary. I've added a close button to the glossary slide that will take the user back to the screen previously viewed. The glossary was built by importing an XML file, and I made sure there are no special characters in the label fields (unless spaces count, because there are some two-word terms).

The glossary functions perfectly if I publish to swf. However, when I publish as HTML5, the glossary shows up but is not interactive--I can't click on the letters across the top, the terms, or the search function. Nothing happens. I am using Captivate 9.0.2.437 on a Mac and viewing on SCORM Cloud. I've tested it in Firefox and Safari, and I've had someone else test running Windows IE (from SCORM Cloud) with the same results.

Thanks in advance for any help you can provide.

[kayleenh71]

I found this statement at cpguru.com: "You cannot use the Glossary Widget with projects published to .exe or .app or as an HTML5 project exported from Adobe Captivate 6 or above."

If this is true, does anyone know another way to build a glossary that will work in HTML5?

[Stagprime]

How about this idea...?

Create a box that will house the definition of the word.

This box will have a different state for each definition.

Then arrange the words in whatever fashion you creatively desire.

Make each word a hyperlink that changes the state of the definition box to show accordingly.

[kayleenh71 · Accepted solution]

So... I'm an idiot... I hadn't copied the xml file into the project file. Once I did that, the glossary works just fine. (I also ungrouped the glossary widget and return button and made sure the glossary was on top, but I'm not sure that had any effect.)

Thanks for the help though, Stagprime!

[Lilybiri]

Thank you so much for posting this answer! You are not afraid to tell that it was due to something you missed. That is a great example for other users. Thanks and best wishes for 2018.

BTW You are not an idiot, on the contrary. In a past life I used to congratulate students who dared to make mistakes while exploring, and learned from those mistakes.