What is a user interface?

In plain English

A user interface is the part of a system that allows a person to interact with it. In a website, it includes menus, links, buttons, fields and the messages that explain the result of an action. These elements need to communicate both what the person can do and what the system has done.

MDN’s definition of UI covers interaction between a user and a machine, including software interfaces such as webpages and input forms. On a business website, the practical focus is the set of controls customers and staff use to complete their tasks.

The interface contributes to user experience, but the whole experience also depends on information and the underlying service. A usable appointment selector cannot supply an appointment the business does not offer. Review the interface’s behaviour while keeping the customer’s actual task and the business outcome in view.

Why it matters for a Jersey business

A website’s enquiry or booking controls often connect a prospective customer to the business. Their labels and behaviour should help someone understand what to enter and what happens next. An unfamiliar icon or vague button can create uncertainty even when the technical action behind it is correct.

Staff interfaces matter too. Editors need to understand which controls save a draft, publish a page or change a live record. Appropriate permissions and clear feedback help the business maintain its website. The review should cover the people actually using each interface and the actions their role permits.

A realistic Jersey example

Imagine a Jersey activity provider reviewing its booking interface. This is a hypothetical example. The date selector, participant fields and confirmation button are checked together. The team verifies that labels identify each field and that unavailable choices are explained without relying only on colour.

The review also checks keyboard operation, visible focus and the message after submission. Staff confirm that a successful booking appears in the receiving system. Approval therefore rests on the working journey as well as its visual design, with no assumed conversion improvement attached to the example.

What to check before approving a UI

Make labels specific. Use words that describe the action or required information. A submit button should sit in a context that explains what is being submitted. Field labels should remain available while the person enters information; temporary placeholder text alone can disappear at the moment it is needed.

Use appropriate controls. Choose links, buttons and form fields that match their intended behaviour. The visible design and underlying HTML should support the same meaning. W3C’s development tips provide practical guidance on structure, controls and keyboard use for accessible websites.

Check feedback. Confirm that loading, success and error states describe the actual result. An enquiry interface should not claim a successful delivery solely because the browser accepted a click. Define which outcome the application can confirm and help the person understand when they need to try another step.

Review forms. W3C’s forms tutorial covers labels, instructions and useful feedback. Apply those principles to the real fields and workflow. Explain the required format where necessary, keep errors associated with the relevant information and help customers correct a problem without starting unnecessarily from scratch.

Check keyboard and focus. A person should be able to reach and use relevant interactive controls through supported keyboard interaction. Visible focus helps show the current location. Review menus and overlays as functioning controls, because a static design image cannot demonstrate how focus moves or what happens when the interface closes.

Review different layouts. Check useful screen sizes, text resizing and content that varies in length. A button label that fits a short mock-up may overflow after an editor changes it. W3C’s design tips also address contrast, navigation and other design considerations that affect real interaction.

Keep patterns consistent. Similar actions should use understandable, consistent controls and messages. Record the agreed patterns for later editing so that new pages do not invent confusing variations. Consistency still needs judgement: destructive or consequential actions should communicate their actual effect rather than borrowing a reassuring label from an unrelated task.

Common myths

UI means colours and decoration only. It includes controls and feedback people use to interact.

A screenshot proves the interaction works. Working states and access need practical review.

A familiar icon never needs explanation. Meaning depends on the person and the context.

Our take

Jersey Web’s view is to approve a functioning task flow alongside the visual design. Check labels, control behaviour, accessibility and the receiving outcome. A clear interface gives customers and staff understandable actions and useful feedback when the result differs from what they expected.