The story
This story is fictional. The failure in it is common.
At 10:47pm the grant application was due at midnight. Mina had her CV, portfolio and proposal ready. The site was minimal, with a single progress bar.
Then a question asked her to drag and drop her documents into a blank box. Mina uses voice software. Her commands did not move the files, and there was no Browse button.
Her sister lives next door. She came round, sat at the laptop and followed Mina’s spoken instructions to move three files.
On the final page a green banner read: “Thank you. Your application has been submitted.”
The principle
Principle 2 of Universal Design (Center for Universal Design, NC State, 1997): the design accommodates a wide range of individual preferences and abilities.
| Guideline | What it asks | Held by this form? |
|---|---|---|
| 2a | Provide choice in methods of use | No. Files could only be dragged |
| 2c | Facilitate the user’s accuracy and precision | No. Dragging asks for fine pointer control |
| 2d | Provide adaptability to the user’s pace | Partly. Nothing rushed her until the upload; by then the deadline left no slack |
Service blueprint: current state
The application breaks at the upload step, an hour before the deadline. Rows marked (inferred) are deduced from the story, not observed.
| Layer | 1. Prepares | 2. Fills in the form | 3. Uploads files | 4. Gets help | 5. Submits |
|---|---|---|---|---|---|
| Evidence | CV, portfolio, proposal ready | A minimal form, one progress bar | A blank box: “drag and drop” | None | Green banner: submitted |
| Applicant actions | At 10:47pm, with the deadline at midnight | Answers by voice | Tries voice commands; files do not move | Asks her sister to operate the laptop | Reaches the last page |
| Line of interaction | |||||
| Frontstage | None | Fields work with voice | Drag-only upload, no Browse button. F1 | No help offered on the page. F2 | Confirmation with no record of the workaround. F3 |
| Line of visibility | |||||
| Backstage | None | None | Upload component chosen without a non-drag option (inferred) | No support channel at that hour (inferred) | Submission logged as complete (inferred) |
| Line of internal interaction | |||||
| Support processes | Fixed midnight deadline | None | Testing done with a mouse (inferred) | No route to extend the deadline (inferred) | Analytics count completions, not how they happened (inferred) |
1. Prepares
- Evidence CV, portfolio, proposal ready
- Applicant actions At 10:47pm, with the deadline at midnight
- Line of internal interaction
- Support processes Fixed midnight deadline
2. Fills in the form
- Evidence A minimal form, one progress bar
- Applicant actions Answers by voice
- Line of interaction
- Frontstage Fields work with voice
3. Uploads files
- Evidence A blank box: “drag and drop”
- Applicant actions Tries voice commands; files do not move
- Line of interaction
- Frontstage Drag-only upload, no Browse button. F1
- Line of visibility
- Backstage Upload component chosen without a non-drag option (inferred)
- Line of internal interaction
- Support processes Testing done with a mouse (inferred)
4. Gets help
- Applicant actions Asks her sister to operate the laptop
- Line of interaction
- Frontstage No help offered on the page. F2
- Line of visibility
- Backstage No support channel at that hour (inferred)
- Line of internal interaction
- Support processes No route to extend the deadline (inferred)
5. Submits
- Evidence Green banner: submitted
- Applicant actions Reaches the last page
- Line of interaction
- Frontstage Confirmation with no record of the workaround. F3
- Line of visibility
- Backstage Submission logged as complete (inferred)
- Line of internal interaction
- Support processes Analytics count completions, not how they happened (inferred)
F1 Critical: the applicant cannot complete the step on her own. F2 Major: no fallback close to the deadline. F3 Minor: the service records a success it did not deliver.
Where it broke
The form worked with voice until the one step that asked for a hand on a mouse.
F1: one way to add a file. Drag and drop is a convenience for mouse users. As the only method, it excludes keyboard users, voice users and anyone without fine pointer control. A Browse button costs almost nothing to keep.
F2: the deadline removed every other option. At 10:47pm there is no time to call a helpline or find another route. A barrier that would be a delay at noon left one way through: someone else’s hands.
F3: the data says it worked. The service logged a completed application. It cannot tell that the applicant handed her laptop to someone else, or that her sister saw her application. A completion rate hides dependence: what looks like success is a transfer of work.
What the principle asks for is choice in method, not a single method made easy for some.
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 form missed |
|---|---|---|
| Web Accessibility Directive (EU) 2016/2102 | Law, public sector | If the funder is a public body, the form must meet EN 301 549 |
| EN 301 549 | Harmonised standard | Its web clauses follow WCAG 2.1 AA, including 2.1.1 Keyboard: every function available from a keyboard |
| WCAG 2.2, 2.5.7 Dragging Movements (AA) | W3C standard | Any action done by dragging can also be done with a single pointer, without dragging. The next version of EN 301 549 is expected to adopt WCAG 2.2 |
| WCAG 2.1, 2.5.3 Label in Name (A) | W3C standard | The name a voice user speaks matches the visible label, so commands reach the control |
A private funder is not covered by the Web Accessibility Directive or the European Accessibility Act for this service. The WCAG criteria still describe what a working form looks like.
What good looks like
Keep drag and drop, and add a button next to it. The fix is small; the testing habit behind it is the larger change.
| Fix | Fail point | Layer | Type | Likely owner |
|---|---|---|---|---|
| A Browse button beside the drop area, reachable by keyboard and named for voice | F1 | Frontstage | Quick | Digital team |
| Upload components chosen only if they pass keyboard and voice checks | F1 | Support processes | Structural | Design system owners |
| A visible way to ask for help or an extension, open until the deadline | F2 | Frontstage, backstage | Quick | Grant administrator |
| A short optional question at submission: “Did anyone help you complete this?” | F3 | Frontstage | Quick | Service owner, research |
How to test for it
- Keyboard-only run. Complete the whole form without touching a mouse. Any step that cannot be finished is F1.
- Voice control run. Repeat with the voice software built into the main platforms, using each control’s visible label.
- Component audit. List every drag interaction in the design system and its alternative. Missing alternatives go to the top of the backlog.
- Completion with consent. Recruit voice and keyboard users, paid, and observe completions near a real deadline rather than in a calm session.
A form that accepts one kind of hand has already chosen its applicants.
Sources
- Center for Universal Design, NC State University, The Principles of Universal Design, version 2.0 (1997)
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2, criteria 2.1.1, 2.5.3 and 2.5.7
- Directive (EU) 2016/2102, Web Accessibility Directive
- W3C WAI, European Union accessibility policies