Choice

Suggestion: a repeat of the SAVE button between every few choices so there is always one visible if a list scrolls off the screen. Possibly at each choice? Or, once a radio button is clicked, move focus to a SAVE button or dialog box. That way a user won't leave thinking the button click alone had accomplished everything.

Agree: earlier suggestion of displaying choices in multiple rows and columns instead of just one of either.

Kudos for the Choice module.
It worked brilliantly to schedule high school parent conferences.
Using the choice module, a parent could look to see what times were available to see me (their kid's teacher) and book an open time. It updated instantly to close that choice to the next parent online. They could change their time, or cancel. Automatically. And I could Excel my schedule. Brilliant.
It was simple - I set up one choice for each time slot (with a limit of 1) plus a cancel choice (high limit). One button every 10 minutes of the visiting hours.

I chose the horizontal display, although it scrolled far right off the screen, because I wanted their first view of the screen to show the all important SAVE button, which they may have otherwise never seen at the bottom of a vertical scroll.  That's why above I supported the idea of a grid display of the buttons.

I have until Spring conference to figure any such code changes if I want to learn to dabble in PHP. But if someone more familiar with the module gets to it first, so much the better.