A small design study about making an appointment screen easier to understand.
Independent learning project · November 1, 2026
Both screens are fictional. No patient information, NHS screens or live bookings are used.
When is the appointment? Is it booked? What happens if it needs to change?
Those are simple questions, but a small dot, an abbreviation or a button labelled “Edit” can leave the answer unclear. This project looks at those details in one fictional outpatient appointment screen.
The starting screen was deliberately created for this exercise. It is not taken from an existing service.
The revision spells out the date, adds a written booking status and names each action. A change is only applied after confirmation. Cancelling also has a separate confirmation step.
The first screen is a static illustration. In the revised screen, try changing the appointment, keeping the current booking or cancelling it. “Restart demo” restores the initial state. These actions only affect the demonstration.
| Detail | Change | Reason |
|---|---|---|
| A green dot without a visible label | “Appointment booked” written in text | The status should not depend on recognising a colour. |
| “12/11/26” and “OPD” | A written date and “Outpatient appointment” | Reduce the need to interpret abbreviations and date formats. |
| “Edit” and “X” | “Change appointment” and “Cancel appointment” | Make the result of each action easier to anticipate. |
| An action without a clear review step | Confirm the new slot or keep the current booking | Give the user a chance to check before applying a change. |
| Small controls and unclear feedback | Larger native controls, visible focus and a status message | Support keyboard use and make the result visible. |
The browser prototype contains two alternative appointment slots, a confirmation step, cancellation and a reset. It uses native buttons and a select control, moves focus when a panel opens and includes a live status region for feedback.
The code passed basic JavaScript syntax and element-reference checks. This is implementation evidence, rather than evidence that the design is easier for patients to use.
The next step is to ask people to find the appointment date, change the booking and explain what has happened. That would help test whether the wording and confirmation steps are understood.
Screen reader behaviour, zoom, text resizing and keyboard interaction still need browser testing. No participant testing or formal accessibility audit has been completed, and no improvement in task completion has been measured.
Selected WCAG 2.2 criteria informed the design: Use of Color (1.4.1), Contrast (1.4.3), Keyboard (2.1.1), Headings and Labels (2.4.6), Focus Visible (2.4.7), Target Size (2.5.8) and Status Messages (4.1.3). These references do not establish conformance.