Consistent design can use different page layouts

Shape the page layout around the task at hand. Someone selecting one entry from many options needs different information from someone confirming a specific action. A uniform grid can hide those differences if the team applies it unchanged to both situations.

Two tasks in the same portal

In this entirely fictional example, a person selects a project report from a list and then reviews it before sending. The table contains placeholder data. The first view should support selection; the second should show which version would go to whom.

A wide list grid is designed to compare several reports. In a confirmation step, the same columns may push important details to the edge or cut them off on small screens. In the example, selecting the correct file would still be problematic if the recipient went unnoticed.

Keep recurring functions recognisable

The W3C explanation of consistent identification addresses recurring controls with the same function. Familiar labels, icons and accessible names support this. It does not require every page to have the same arrangement.

Navigation, focus indicators and the behaviour of familiar buttons can remain shared. “Open report” and “Send report”, however, must be recognisable as different actions. Using the same vague label, “Continue”, would hide the meaning of the second action here. Shared design should aid recognition without blurring differences in the flow.

Fit the confirmation to the action

GOV.UK describes a review view with relevant details, a way to change them and a clearly named final action. In our example, the recipient, project and selected file version must appear together clearly before sending. The view itself is not a confirmation that the report has been sent.

If the person can change the recipient, they must be able to review the updated summary afterwards. Other selections already made should be preserved. The application must also handle permitted changes and the version actually sent reliably; a clear page alone does not determine these.

When a shared layout is enough

For a short task with little variation, a compact summary on the same screen may be sufficient. An extra page is not necessary for every process. What matters is whether all required details are available and understandable at the point of action.

Ask people to try both tasks with realistic examples: first finding the report, then checking the recipient and version before taking the action. Pay particular attention to long text, small screens and returning after a change. This helps assess which elements can stay shared and which arrangement each task needs.

Sources

• W3C WAI — Understanding SC 3.2.4 Consistent Identification

• GOV.UK Design System — Check answers