Portal audit exercise - Case 3 Answer
Answer guide · Difficult application form
25 multiple-choice answers with explanations and a sample evidence-based audit finding.
Facilitator use: Share after participants have attempted the portal task and submitted their answers. Use the explanations to discuss evidence and overlap between UI and UX.
General evaluation
1. What is the main task?
Correct answer: A. Complete a permit application
The task is to complete the permit application.
2. What happens on the first submission attempt?
Correct answer: B. A generic error and lost entries
The first submission displays a generic error and clears the fields.
3. What is the primary problem category?
Correct answer: C. Form usability and interaction
The form obstructs completion and error recovery.
4. Which evidence supports the finding?
Correct answer: D. The error message and cleared fields
These are observable behaviours in the simulation.
5. Why is Field 02 unclear?
Correct answer: A. It does not state what information is required
The label does not explain that it expects an event date.
6. What could reduce repeated effort?
Correct answer: B. Preserve entered values after validation errors
Retaining values prevents unnecessary re-entry.
7. Which error message is more helpful?
Correct answer: C. Enter an event date in DD/MM/YYYY format
Specific feedback explains the field and recovery action.
8. What does a simulated success confirm?
Correct answer: D. Completion of this simulated form interaction
No real application is submitted or approved.
9. Which user may struggle with unclear requirements?
Correct answer: A. Someone unfamiliar with the application process
Unfamiliar users cannot rely on prior knowledge.
10. Which outcome should be measured?
Correct answer: B. Completion, errors and recovery effort
These measures relate to form usability.
Audit: labels & requirements
1. What does Field 02 actually require?
Correct answer: C. Event date
The simulation expects an event date.
2. Where is the date format explained?
Correct answer: D. Only in the generic page instructions
The format appears away from the relevant field.
3. Which label is clearer?
Correct answer: A. Event date (DD/MM/YYYY)
The label states both purpose and format.
4. How should required fields be communicated?
Correct answer: B. Clearly before submission
State requirements clearly before users submit.
5. Which check validates improved labels?
Correct answer: C. Observe representative users entering the requested information
Task observation reveals understanding.
Audit: errors & recovery
1. Why is Invalid data unhelpful?
Correct answer: D. It does not identify the field or correction
The error lacks a specific recovery instruction.
2. Which change most helps recovery?
Correct answer: A. Specific inline errors and a clear summary
Identify each issue and explain how to fix it.
3. Should correct entries survive an error?
Correct answer: B. Yes, so users correct only problematic entries
Preserve valid entries to reduce effort.
4. What should be checked after an error?
Correct answer: C. Focus, error announcement and access to affected fields
Error feedback must be usable by keyboard and assistive technology.
5. What is sound audit evidence?
Correct answer: D. Submitted values disappear after the first error
This states an observed behaviour without assuming motives.
Audit: user effort & task flow
1. What increases user effort here?
Correct answer: A. Re-entering cleared fields
Lost entries force repeated work.
2. Which redesign best reduces effort?
Correct answer: B. Clarify inputs and retain data during correction
Clear requirements and recoverable errors reduce rework.
3. How should a revised form be tested?
Correct answer: C. Complete realistic tasks including deliberate input errors
Include recovery, not only successful entry.
4. What remains unknown from this exercise?
Correct answer: D. Real processing and approval quality
The exercise covers only the simulated interface.
5. Which conclusion is justified?
Correct answer: A. Unclear labels and destructive error handling impede completion
The conclusion follows the observed form behaviour.
Sample audit finding
Task: Complete a temporary event permit application.
Evidence: Field 02 expects an event date but does not explain it in the label. Details does not clearly request the event purpose. The first submission displays Invalid data and clears all values, even when the entered values match the stated requirements.
Impact: Users must guess inputs, identify errors without guidance and repeat work.
Classification: UX form usability, interaction and error recovery.
Recommendation: Use meaningful labels, place format guidance beside the field, provide specific errors and preserve entered values. The first-attempt failure is deliberately programmed for this exercise; a real implementation must validate according to actual rules.
Validation: Observe successful and erroneous task attempts, keyboard recovery, error announcements, completion rates and re-entry effort. The simulation checks the date pattern only, not calendar validity.
Scoring
10 general questions and three categories of five questions: 25 points total.