Millisecond Online Community

Hi,

I am doing a survey and I would like to make it more convenient for respondents to get through it.  I am not happy with the default location of the 'next' button.  In fact, I am thinking the 'next' button is unnecessary and the better behavior  would be to click on a radio button and just go to the next question automatically.

Is it possible to automatically submit with <radiobuttons>?  How can move the next button somewhere more convenient?

Thanks!

Mike

I'm having a similar problem.  I want the question page to remain on the screen for 60 seconds regardless of whether the person has answered.  Trialduration and posttrialpause are not working for me.

Mike, have you thought about using regular stimulus screens rather than a survey? If your questions do not have many options, you can have keyboard responses or just use likerts.  That would allow respondents to move on as soon as they replied.

I have thought about that.  In another part of my study, I have an experiment that works as you describe (although you click with the mouse, rather than use the keyboard). 

I have a little bit more than 100 questions with complex skip patterns etc so I worry that converting them from surveypages into an experiment would be tedious.

But thanks - that suggestion could work if nothing else is available.

 - Mike

Hi Mike,

The reason <surveypage> uses the next button is to handle pages with multiple questions, and to provide a user interface that allows the participant to navigate back to previous pages if they wish to change an answer. For cases where you are presenting one question at a time with forward-only navigation, the <trial> or <likert> element would be the way to go.

I did some thinking about whether it would make sense to provide an option for automatic navigation on a survey page, but there are some problems. The feature would only make sense for a page that had a single single question with radiobuttons, dropdowns, or listboxes. It wouldn't work for any of the other question types such as checkboxes, textboxes, sliders, because with these controls, there's no discreet event that indicates the participant has completed their response. Even then, I'm not sure we could support allowing participants to select a response using standard keyboard navigation because again, there's no discreet event that indicates the user is finished navigating through the different options using the arrow key. At the end of the day, the best design for something like this is going to look pretty similar to <likert> feature, which presents buttons that that participants press to move to the next page.

-Sean