UX/UI Designers near you

Accessibility in interface design is mostly about states and semantics rather than about colour. Focus order, visible focus indicators, error messages tied to the field that caused them, controls that announce what they are, and interactive targets big enough to hit on a phone in a moving vehicle all get decided in the design, not in the code.

The Web Content Accessibility Guidelines are the benchmark Australian organisations design and procure against, and government and large enterprise contracts commonly require a stated conformance level. Ask a designer which level they work to and how they verify it, and expect a specific answer rather than a reassurance.

Testing with people who actually use screen readers, magnification or switch access finds problems that automated checkers never report. Budget for a small number of those sessions. It is far cheaper than redesigning a released product because a customer could not complete a transaction.

The Australian Consumer Law reaches conduct, and an interface is conduct. A flow that reveals fees only at the final step runs into the requirement that the total price be displayed as a single figure at least as noticeably as any part price. A pre-ticked add-on that a customer did not choose is a representation about what they agreed to.

The ACCC's guidance on unfair business practices covers false or misleading claims, undue harassment and coercion, and unconscionable conduct, particularly where a consumer is in a position of disadvantage. A cancellation flow built to exhaust the user, or repeated interruptions designed to wear down a refusal, sit uncomfortably close to that territory.

None of this is a reason to avoid persuasive design. It is a reason for the designer and the client to agree, in writing, that pricing is shown honestly, that opt-ins are not pre-selected, that cancelling is as easy as subscribing, and that anyone can see what they have agreed to before they agree to it.

Research generates personal information: names, contact details, recordings of faces and voices, and sometimes sensitive information about health, finances or family circumstances. Where the organisation is covered by the Privacy Act 1988, the Australian Privacy Principles govern how that material is collected, used, stored and destroyed.

Get written consent from participants that states what is being recorded, who will see it, how long it will be kept and how it can be withdrawn. Consent to a research session is not consent to publish a clip of someone's face in a conference talk.

Session replay and analytics tools on live products raise the same question at scale, because they can capture what people type into forms. Ask what is being recorded, whether fields containing personal or payment information are masked, where the recordings are stored, and who inside and outside the organisation can watch them.

A typical engagement opens with discovery: existing analytics, support tickets, staff interviews and sessions with real users. Support tickets are the cheapest research an Australian business already owns and almost never reads properly.

From there, flows and wireframes, then a clickable prototype that can be put in front of people before development starts. Testing five or six participants per round finds most of the serious problems, and testing early means the findings are cheap to act on.

Interface design and a component library follow, then handover and support during build. Expect the designer to stay available while developers implement, because an interface always raises questions the design file did not answer.