User journeys
Audit a Student Admissions Application
Published by whatisADA / Grow Wild Agency · Updated
Purpose and preparation
Review an admissions process across program choice, eligibility questions, documents and status tracking. Use a test account and fictional records. Include dependencies between answers so contradictory or stale values are detected.
A practical example
An applicant switches from domestic to international study and receives different document requirements.
How to check it
- Map the branches that change required questions, documents or fees. Record how the application explains those changes.
- Complete representative branches with the keyboard and a screen reader. Change an earlier answer and verify that later requirements and stored values remain consistent.
- Test saving, returning, correcting errors and reviewing the application. Check whether the status page explains missing items in text and provides a clear next action.
What can be missed
A successful default path can hide failures in transfer, international or returning-student branches. Select branches based on meaningful changes in the process.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.