Evan,
Okay, lots of approaches available in Opus. Here some some ideas you might explore. I'm assuming you are 'into' scripting.
>>>Check out the suggestions and code examples at the end of the following post.
viewtopic.php?t=2688&highlight=text+input+return
Basically, checking for a NOT 'null' condition of User Text-Input.
>>> you can use 'AND' operators in your 'if' statements.... see the '&&' in syntax section of help files.
>>> As suggested by Sentosa above, you
can control a good portion of this task by how you let the User navigate. For example, you can only put so much on a page (well, you can put a lot and stack it up, but let's say we don't). You could Show() or Enable() the button for "Proceed" (or "next page" etc.). That routine could essentially be duplicated on subsequent pages... so maybe you are only checking 8 things at that time for completion, then moving on. ( somewhere here you have to think through... are these Pub vars, or Page vars (persistent??). When do you write these to a file or database?)
>>> If I recall Radio Buttons can be set up to have a "default" Radio "depressed" initially. That could be a
distinct Rad Button that holds a 'stop' code or 'false' (not answered). Checking any other Rad Button, unchecks the default. (I've seen a couple approaches with Radio's by the way. One in DW's sample pubs has each radio button set its own specific Variable. Another approach is to associate the radio
group to one Variable, each choice setting a different value for that variable.)
>>> Check out the Sample Pubs that ship with Opus Pro. Also, Search the forum for 'quiz' or 'student', or possibly 'question'. You will see how others use the SCORE accumulation to permit the student to "move on" in the pub. (there is a Question Wizard in Opus... I've not used).
Have a great weekend with your project.