UI/UX Design

Figma files with named components and variants, a design system covering typography, colour, spacing and interaction states, responsive layouts at agreed breakpoints, and interactive prototypes for the key journeys. Handover includes specifications developers can build from: redlines, token values, empty and error states, and motion notes. The files sit in your workspace, so future changes do not depend on us.

Yes, and it is usually done in stages. We audit the current interface, map the journeys people rely on, then introduce the new design system component by component so navigation habits are not reset overnight. Changes to high-traffic flows are validated with usability testing on a prototype before they are built, and where behaviour genuinely must change, in-product guidance is designed alongside it.

We design to WCAG 2.1 AA by default: colour contrast checked at design time, focus order and keyboard paths defined in the specification, targets sized for touch, and form errors described in text rather than by colour alone. Components are annotated with the roles and labels assistive technology needs, so accessibility is specified for developers rather than discovered during a later audit.

With prototypes tested on people from the intended audience rather than internal reviewers. A clickable Figma prototype is enough to run task-based usability sessions, and the output is a list of specific failures — where people hesitated, what they could not find — mapped to design changes. This happens before build, when a change costs an afternoon rather than a sprint.