Using 28MARS on Mobile in Australia

Test the mobile experience by task rather than by screen size

A page fitting inside a phone display is only one part of mobile usability. A reader should be able to locate the sign-in area, read the terms without text being clipped, move between account sections and return to the correct page after following a link. If a table needs horizontal scrolling, that is different from the entire document overflowing the viewport. The relevant question is whether controls remain legible and usable.

Check the experience separately in portrait and landscape orientation. A payment field or identity-upload control that looks acceptable in one orientation can become difficult to operate when the keyboard is open in another. Browser zoom and device accessibility settings should not prevent a user from reading a confirmation message. A responsive layout is therefore a practical behaviour to inspect, not a guarantee derived from the word mobile.

Do not confuse a saved home-screen shortcut with a native application. A browser can place a shortcut on a phone without installing a separately distributed app. Claims about a dedicated app require a verifiable official distribution source; an icon, a third-party download page or a generic installation prompt is not adequate evidence of the app’s origin.

For access from a shared device, consider whether the browser is keeping an active session after the tab is closed and whether notifications expose account details on the lock screen. The website cannot control the security of a person’s device, so a discussion of mobile access should not imply that a browser session is private simply because the screen is small.

If a step fails on mobile, separate a display problem from an account restriction or a payment-method limitation. A button that is hidden by the keyboard calls for a layout check; an unavailable method calls for checking the current cashier; an identity request calls for reading the operator’s notice. Treating all three as an app problem makes the troubleshooting advice less useful.

The practical comparison is the same for someone returning to the site on another device: note which features are visible, which steps require a secure login and which claims have actually been verified. A mobile page should not be described as equivalent to a native app solely because the same article headings appear on both screens.

Mobile usability should also be judged on the information a user can actually review before confirming an action. A compact layout can hide explanatory text behind collapsible sections, place a disclosure below the visible screen or truncate a long payment-method label. Scroll through the entire relevant view, including any confirmation or error message, instead of relying only on the first screen. If a feature is unavailable, record the exact wording rather than assuming a different device would make it available. Browser permissions, connectivity and account eligibility are separate considerations, and a responsive page does not establish the status of any of them.

When reviewing this subject, distinguish the information displayed on the relevant page from assumptions based on a headline or a different account. The specific conditions matter more than a general label. Keep any time-sensitive statement tied to its source and date, and do not treat missing details as a guarantee. These checks help preserve the difference between a feature described in public material and what is confirmed for a particular reader.