Imagine a fictional Western Australian resident comparing a new everyday finance app. The person and events in this scenario are invented to illustrate a small usability trial. The example is not a product recommendation, a medical account or a claim about a real customer’s experience.
The resident prefers larger text and wants to understand transactions without relying on a family member to interpret every screen. Before changing an important routine, they plan to test the whole task, including authentication, finding a record and obtaining help.
The trial starts with a defined task and actual needs
In the scenario, the resident chooses one task: locating an occasional household charge and understanding its date, description and amount. They write down the display settings and device they intend to use. A general claim that the service is easy becomes a question about this particular task.
The resident also decides what information is necessary for the initial exercise. A suitable demonstration or fictional sample is preferred where available. The trial should not require moving money, changing investments or exposing records beyond what is appropriate to the agreed purpose.
A family member can help take notes with permission, but the resident remains the decision-maker. Assistance with a device is kept separate from authority over an account or permission to disclose credentials.
A feature description becomes something to check
The resident reads the proposed provider’s own information about supported devices, display settings and assistance. They ask how the relevant feature works under their actual setup, rather than assuming every app behaves identically.
For a real example of such documentation, NAB’s online accessibility page describes text sizing, contrast, zoom and assistive technology. It says the bank is working towards WCAG 2.2 Level AA. That wording should not be changed into a claim of complete certification or compatibility with every device and task.
The scenario does not select NAB or any other provider. The page illustrates the kind of specific information to obtain and verify with the service actually being considered.
The exercise includes authentication and an incomplete result
The resident plans to check how login and authentication work alongside the larger-text setting. A readable main page is less useful if a necessary message, code prompt or error cannot be understood. The exercise also includes returning to the record after leaving the first screen.
The Australian Human Rights Commission’s digital accessibility guidance discusses completing the full task. The guidelines are not legally binding in themselves, and the scenario does not use them to declare compliance or determine an individual legal outcome.
The resident records where assistance is needed and whether the app preserves the information necessary to continue. A single successful screen is not treated as evidence that every future transaction or support interaction will work.
Convenience is checked alongside control of access
The family member is not asked to keep the resident’s password or receive authentication codes. Instead, they help identify questions for the provider’s verified support route. Any arrangement for another person to act would require its own proper authority and procedure.
The ASD’s personal cyber security handbook recommends multi-factor authentication, strong unique passwords, updates and checking unexpected messages. In the scenario, those principles remain part of the trial rather than being removed to make the task seem easier.
The resident asks how access could be recovered after a device change and whether the relevant support channel can be used comfortably. A convenient new setting should not leave recovery dependent on one informal helper.
The trial record separates findings from assumptions
The resident’s short note includes:
- The task, device and display settings used.
- The actions completed independently.
- The information that was unclear or difficult to reach.
- The assistance and provider answers still needed.
- The costs and transition questions to check before changing.
The note does not claim the experience represents every person with similar needs. It records a specific exercise under particular conditions. If the provider changes the app or the resident changes device, relevant parts of the task may need checking again.
Before a commitment, the resident also checks what the proposed service costs and what is included. A successful usability exercise does not settle the account terms, information handling or the work of leaving another service. Those questions are kept on the same decision record, with the relevant provider asked to clarify them through a verified channel rather than relying on the helper’s assumptions.
The scenario ends before a premature switch
The resident decides to obtain an answer about the unclear step before moving the routine. Necessary records remain available through an appropriate arrangement, and no financial outcome is invented. The trial has exposed a question that matters to independent use.
The practical lesson is to assess inclusion through the whole task and the actual person using it. A small trial should support a choice the person can understand and control, with useful assistance and remaining uncertainty clearly recorded.