Please help us help you and fill where relevant:
Your LimeSurvey version: Current cloud version
Own server or LimeSurvey hosting:
Survey theme/template: Fruity Twenty-Three
==================
Hi there,

I was wondering why the TIMER menu is available for some question types (e.g. short free text) but ont for others.

We would want to use it within an Array question type because we have an audio files autoplaying as people move to a certain page and need them to listen to the entire file and only then rate it on a 7-point Likert scale. So, as a solution, we thought we would only activate the Next-button once the file has played through.

Is there any other workaround we should be considering?

Thanks so much,
all best

Jana

Hi,
if you had asked this in the German section I would have recommended to read my "Tutorial 3: Gimmicks...", Chapter 2.

Joffm

BTW:
What is "current cloud version"?
My current cloud version is 5.6.38.
But yours is obviously 6.something (because of the "fruity 23" theme)
 

Hi Joffm,

Thanks a lot - your solution solved the issue.

I was just wondering if there is a fix to the problem that participants would, in theory, be able to listen to the audio again if they refresh the page.

More specifically, if they fail to select an answer, lime survey comes back with an error msg (reminding them that the question is obligatory) and auto-plays the audio once more.

Is there any way of avoiding this by changing the code?

Cheers,
Affenbrotbaum

PS: LimeSurvey Cloud Version 6.2.11

Have the audio on one page, move on to the next page. Once that is done, ask the questions. I don't see how respondents would be able to listen to the audio again, if you don't allow them to navigate back.

Hm, thanks.

If possible somehow, we'd like participants to already see the Likert-scale while listening to the audio and we are looking to avoid any form of delay between listening to the full audio and evaluating it on a straightforward scale. The audio files are all quite similar, so the response should be immediate.

... thanks a lot for your input, though. Much appreciated!