We're currently designing a checkout process for course registration at a University. One step of the process is to check the student has the required prerequisite courses in their academic history. The mockup below shows the proposed interface for this step, at a point when the user has failed to meet prerequisites for the courses they're registering for (in the case below they've failed 2 out of the 5).
The part that we're having difficulties with is clearly directing the user to make the right set of actions. They have a number of options at this point:
- Send a message requesting help, and exit the registration process by exiting the browser.
- Do not send a message, but continue with registration for the remaining courses.
- Send a message requesting help, and continue registration for the remaining courses.
- Do nothing, exit the registration.
So unusually, this interface has two completely optional, and yet not mutually exclusion paths the user can take. Given the mockup below:
- Does the current UI communicate these choices optimally?
- If not, how can we effectively communicate this to our users without extensive instructive copy? Particularly, if the user isn't paying attention and doesn't read the second option of continuing with their remaining courses.