User journeys
Audit Statement Discovery and Download
Published by whatisADA / Grow Wild Agency · Updated
Purpose and preparation
Review how an account holder locates, downloads and reads a statement. Use a test account with synthetic financial records. Treat the web interface and the downloaded document as separate parts of the same task.
A practical example
A customer chooses an account and month, downloads a statement and locates a transaction total.
How to check it
- Navigate account and period selectors, checking names, selected values and loading feedback. Verify that download links identify the document and relevant period.
- Download the test statement and inspect its title, language, text, tags, table structure and reading order. Test finding a particular synthetic transaction.
- Return to the account interface and try a missing or unavailable statement. Check whether an accessible alternative and a clear next step are offered.
What can be missed
A tagged PDF is not automatically a usable financial statement. Likewise, an accessible document does not help if its download controls cannot be operated.
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.