Skip to content

The Shape of Access 3: Simple and Intuitive Use

The story

This story is fictional. The failure in it is common.

Marcel needed a booster appointment, and the clinic had a new online portal. He uses a screen reader and prefers to do things himself.

The page was clean and modern. He selected a time. There was no Next button and no confirmation.

He moved through the page with the Tab key and reached a button with no label. He pressed it twice. Nothing happened.

A support worker suggested that a small floating checkmark icon in the bottom corner might be the way to continue. It had no label either.

A friend booked the appointment for him.

The principle

Principle 3 of Universal Design (Center for Universal Design, NC State, 1997): use of the design is easy to understand, regardless of the user’s experience, knowledge, language skills or current concentration level.

Guideline What it asks Held by this portal?
3a Eliminate unnecessary complexity Yes, visually. The words that were removed were the necessary part
3b Be consistent with user expectations and intuition No. No Next button, no confirmation
3d Arrange information consistent with its importance No. The main action was a small icon in a corner
3e Provide effective prompting and feedback during and after the task No. Pressing the button produced nothing he could perceive

Service blueprint: current state

The booking breaks at the step after choosing a time: the control that moves it forward has no name. Rows marked (inferred) are deduced from the story, not observed.

Layer 1. Opens the portal 2. Selects a time 3. Looks for the next step 4. Asks support 5. Booking made
Evidence A clean, modern page A selected time; no confirmation A button with no label Spoken advice about an icon An appointment booked by a friend
Patient actions Navigates with a screen reader Chooses a time Tabs to the button, presses it twice Asks how to continue Hands the task to a friend
Line of interaction
Frontstage Portal Nothing announced. F2 Unlabelled controls. F1 Directions by position and shape. F3 None
Line of visibility
Backstage None No status message set (inferred) Icon buttons shipped without accessible names (inferred) No script for screen reader users (inferred) Booking logged under Marcel’s name (inferred)
Line of internal interaction
Support processes New portal launched None No screen reader test before launch (inferred) Support trained on the visual interface (inferred) None

1. Opens the portal

  • Evidence A clean, modern page
  • Patient actions Navigates with a screen reader
  • Line of interaction
  • Frontstage Portal
  • Line of internal interaction
  • Support processes New portal launched

2. Selects a time

  • Evidence A selected time; no confirmation
  • Patient actions Chooses a time
  • Line of interaction
  • Frontstage Nothing announced. F2
  • Line of visibility
  • Backstage No status message set (inferred)

3. Looks for the next step

  • Evidence A button with no label
  • Patient actions Tabs to the button, presses it twice
  • Line of interaction
  • Frontstage Unlabelled controls. F1
  • Line of visibility
  • Backstage Icon buttons shipped without accessible names (inferred)
  • Line of internal interaction
  • Support processes No screen reader test before launch (inferred)

4. Asks support

  • Evidence Spoken advice about an icon
  • Patient actions Asks how to continue
  • Line of interaction
  • Frontstage Directions by position and shape. F3
  • Line of visibility
  • Backstage No script for screen reader users (inferred)
  • Line of internal interaction
  • Support processes Support trained on the visual interface (inferred)

5. Booking made

  • Evidence An appointment booked by a friend
  • Patient actions Hands the task to a friend
  • Line of visibility
  • Backstage Booking logged under Marcel’s name (inferred)

F1 Critical: the main action has no name. F2 Major: no feedback after selecting or pressing. F3 Major: support can only describe the control in terms he cannot use.

Where it broke

The page looked simple because the words had been taken out. For a screen reader user, those words were the interface.

The step What the screen shows What Marcel’s screen reader gives him
Choosing a time No confirmation Nothing announced
The button he reached with Tab Not described in the story A button with no name; pressed twice, nothing announced
The checkmark support pointed to A small floating icon, bottom corner Another button with no name
Support’s directions “The checkmark in the bottom corner” A position he cannot use

F1: an icon is not a label. A checkmark carries meaning for someone who can see it in context. To a screen reader it is a button with no name, and a button with no name could do anything.

F2: no feedback means no way to recover. Pressing twice and hearing nothing leaves two possibilities: nothing happened, or something happened twice. Guideline 3e is the reason this story belongs under Principle 3.

F3: support inherited the design’s blind spot. The support worker could only describe the control by where it sat and what it looked like. A control that can only be described by its position cannot be found by someone navigating by name.

What the principle asks for is simple to understand, not simple to look at.

Standards and duties

These references show where the idea already appears in EU law and European standards. They illustrate the concept; they are not a compliance assessment.

Instrument Type What it asks that this portal missed
Web Accessibility Directive (EU) 2016/2102 Law, public sector Public health services must make their websites and apps accessible to EN 301 549
EN 301 549 Harmonised standard Its web and app clauses follow WCAG 2.1 AA
WCAG 4.1.2 Name, Role, Value (A) W3C standard Every control has a name that assistive technology can read
WCAG 1.1.1 Non-text Content (A) W3C standard An icon that does something has a text alternative that says what it does
WCAG 4.1.3 Status Messages (AA) W3C standard A selection or confirmation is announced without moving focus
WCAG 2.4.6 Headings and Labels (AA) W3C standard Labels describe purpose

If a private provider runs the portal, the European Accessibility Act is unlikely to cover it, as healthcare services sit outside its scope. The WCAG criteria still describe what a working portal looks like.

What good looks like

Put the words back. Every fix below costs less than sending patients to a friend.

Fix Fail point Layer Type Likely owner
A visible text button, “Continue”, with a matching accessible name F1 Frontstage Quick Digital team
The selected time announced when chosen, and a confirmation page after booking F2 Frontstage Quick Digital team
A design system rule: no icon-only button without an accessible name, checked automatically F1 Support processes Structural Design system owners
A support script that names controls, plus a phone booking route F3 Backstage Quick Support lead

How to test for it

  1. Screen reader runs. Book an appointment end to end with NVDA, VoiceOver and TalkBack. Record every control that is announced without a name.
  2. Automated checks. Tools such as axe catch missing names quickly. They cannot tell whether a name makes sense, so pair them with step 1.
  3. Support simulation. Ask support to guide a screen reader user to book. If the directions rely on position or shape, F3 is still there.
  4. Proxy signal. Track bookings made by phone or by someone else after a portal attempt. Each one is a booking the portal did not deliver.

Removing words made the page look simple. The words were the interface.

Sources

Previous
Next