← QCE Digital Solutions Unit 1

From user characteristics to interface requirements

Linking each user characteristic to a specific interface requirement, e.g. low vision needs large text and young users need simple wording, so the design suits them.

Part of: QCE Digital Solutions Unit 1 — User Experiences and Interfaces — Module 25

Understanding From user characteristics to interface requirements in QCE Digital Solutions Unit 1

What it does: This requirement names the characteristic (limited hand control) and a specific interface feature (big buttons), which makes the experience easier to use. A table row pairs one characteristic with one requirement, so designers can see why each requirement exists. Low vision means users struggle to read small or faint text, so the requirement is large text and strong contrast. Young users are still learning to read, so simple words and clear icons make the interface easier to use. Limited experience means users need obvious labels and simple layouts, not features they have to guess at. Captions give the same information in text, so users who cannot hear audio can still understand the content.

Common mistakes: Large text is the requirement for users with low vision. Good hearing does not lead to a need for large text, so line 1 should be 'Characteristic: low vision'. Adding text labels removes the reliance on colour, so the effect should be positive (no information is lost). Line 3 should show the improved user experience.

Class: _____________________  ·  Name: _____________________  ·  Date: _________

Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.

🖨 Print worksheet + answer key Add From user characteristics to interface requirements to a class →

This module's key terms are also in a printable crossword (Modules 82–148) and word search (Modules 82–380).

Take this worksheet further — free with Cloodit

Each concept is reinforced from every angle — learned, then applied, then tested.

Learning
Duo
A user has low vision. Which interface requirement follows from this characteristic?
Small text so more fits on screenLarge text and high contrast colours
Matches
Characteristic: low vision -> Requirement: make it look nice
↓
The requirement is vague and does not link to the characteristic. It should be specific, such as large text or high contrast.
Applying
Meanings
Term
characteristic to requirement
Meaning
Linking each user characteristic to a specific interface requirement, e.g. low vision needs large text and young users need simple wording, so the design suits them.
Practice
IF characteristic = low vision THEN
Testing
Gaps
User: low vision -> Requirement:
Check Answer
Spots
1Characteristic: good hearing
2Requirement: large text

Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.

The 'Fox' badge — Cunning Debugger, one of Cloodit's 106 collectible badges
Students earn collectable badges

Over 100 of them, across seven natural biomes.

Study Buddy
Students build a real study resource

Turns their work into revision material ready for Flash Cards and Exam study.

Diamond Dash — one of Cloodit's live, competitive Sprint games
Students lock in with Sprints

Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.

A Cloodit certificate of achievement, ready to personalise and print
Custom printable certificates

Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.

Add to class →

Quick Questions

1. A user has low vision. Which interface requirement follows from this characteristic?
A. Small text so more fits on screen
B. Large text and high contrast colours ✓
Low vision means users struggle to read small or faint text, so the requirement is large text and strong contrast.
2. The users are young children aged 6 to 8. Which requirement suits them best?
A. Simple wording and big, picture-based buttons ✓
B. Technical terms and long paragraphs of text
Young users are still learning to read, so simple words and clear icons make the interface easier to use.
3. Which statement describes how a characteristic-to-requirement table works?
A. Each interface requirement is matched to a programming language
B. Each user characteristic is matched to a specific interface requirement ✓
The table links who the users are (characteristic) to what the interface must do or provide (requirement).
4. Users are mostly older adults with limited experience of apps. Which requirement is the better fit?
A. Clear labels and a simple, uncluttered layout ✓
B. Hidden gestures and shortcuts to discover
Limited experience means users need obvious labels and simple layouts, not features they have to guess at.
5. A user has a hearing impairment. Which requirement should be written for the interface?
A. Provide captions for any video content ✓
B. Add louder background music to alerts
Captions give the same information in text, so users who cannot hear audio can still understand the content.

Match the Pairs

Characteristic: low vision -> Requirement: text size 18pt or larger → A user characteristic (low vision) is turned into a specific, measurable interface requirement (large text).
Characteristic: age 6-8 -> Requirement: short, simple words → A young age group leads to a requirement for simple wording so the user can understand the screen.
A requirement should link to a characteristic and say what the interface must do, so the effect on the user experience is clear. → Req 1: Users with limited hand control need buttons at least 44px wide.
A characteristic to requirement table lists each user characteristic beside the interface requirement it leads to. → | Colour blind | Use labels and patterns, not colour alone |
Characteristic: low vision -> Requirement: make it look nice → The requirement is vague and does not link to the characteristic. It should be specific, such as large text or high contrast.
Characteristic: young users -> Requirement: use technical jargon → The requirement does not suit the characteristic. Young users need simple wording, not technical jargon.

Key Term

characteristic to requirement
Linking each user characteristic to a specific interface requirement, e.g. low vision needs large text and young users need simple wording, so the design suits them.

Fill in the Blanks

1. User: low vision -> Requirement: large text
Hint: Type the interface feature that helps users who struggle to see small print.
2. User: young child -> Requirement: simple wording
Hint: Type the language requirement that suits users who are still learning to read.
3. User: shaky hands -> Requirement: large buttons
Hint: Type the control feature that makes tapping easier for users with limited hand control.
4. User: hearing impairment -> Requirement: captions
Hint: Type the user characteristic that creates the need for captions on videos.
5. Low vision -> large text -> easier to read
Hint: Type the action that gets easier for the user, showing the effect on their user experience.

Spot the Error

Question 1
A Characteristic: good hearing
B Requirement: large text
C Effect: users can read labels
Line A — Large text is the requirement for users with low vision. Good hearing does not lead to a need for large text, so line 1 should be 'Characteristic: low vision'.
Question 2
A Characteristic: colour blind
B Requirement: use text labels
C Effect: harder to use the app
Line C — Adding text labels removes the reliance on colour, so the effect should be positive (no information is lost). Line 3 should show the improved user experience.
Question 3
A Table: characteristic -> need
B Low vision -> large text
C Young users -> simple wording
D Hearing loss -> text only
Line D — Users with hearing loss need captions or transcripts for audio and video. 'Text only' does not match that need. Line 4 should be 'Hearing loss -> captions'.
Question 4
A Young users -> complex jargon
B Low vision -> large text
C Hearing loss -> captions
Line A — Young users need simple wording they can understand. Complex jargon would make the interface harder to use, so line 1 should be 'Young users -> simple wording'.
Question 5
A Characteristic: shaky hands
B Requirement: tiny buttons
C Effect: fewer mis-taps
Line B — Users with shaky hands find small targets hard to press. The requirement should be large buttons, not tiny ones, to reduce mis-taps.

Student with a class code? Join your class →