From user characteristics to interface requirements
Name:
Date:
Class:
A
Quick Questions
Shade in the A or B circle for each question.
1. A user has low vision. Which interface requirement follows from this characteristic?
2. The users are young children aged 6 to 8. Which requirement suits them best?
3. Which statement describes how a characteristic-to-requirement table works?
4. Users are mostly older adults with limited experience of apps. Which requirement is the better fit?
5. A user has a hearing impairment. Which requirement should be written for the interface?
B
Match the Pairs
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1Characteristic: low vision -> Requirement: text size 18pt or larger | AThe requirement does not suit the characteristic. Young users need simple wording, not technical jargon. | |
| 2Characteristic: age 6-8 -> Requirement: short, simple words | BA user characteristic (low vision) is turned into a specific, measurable interface requirement (large text). | |
| 3A requirement should link to a characteristic and say what the interface must do, so the effect on the user experience is clear. | CA young age group leads to a requirement for simple wording so the user can understand the screen. | |
| 4A characteristic to requirement table lists each user characteristic beside the interface requirement it leads to. | DThe requirement is vague and does not link to the characteristic. It should be specific, such as large text or high contrast. | |
| 5Characteristic: low vision -> Requirement: make it look nice | E| Colour blind | Use labels and patterns, not colour alone | | |
| 6Characteristic: young users -> Requirement: use technical jargon | FReq 1: Users with limited hand control need buttons at least 44px wide. |
C
Definitions
characteristic to requirement
D
Fill in the Blanks
Complete each line of code by filling in the missing parts.
1.
User: low vision -> Requirement: __________
2.
User: young child -> Requirement:
______________
3.
User: shaky hands -> Requirement:
_____________
4.
User: _______
impairment -> Requirement: captions
5.
Low vision -> large text -> easier to ____
E
Spot the Error
Shade in the letter of the line that contains an error.
Question 1
A
Characteristic: good hearing
B
Requirement: large text
C
Effect: users can read labels
Question 2
A
Characteristic: colour blind
B
Requirement: use text labels
C
Effect: harder to use the app
Question 3
A
Table: characteristic -> need
B
Low vision -> large text
C
Young users -> simple wording
D
Hearing loss -> text only
Question 4
A
Young users -> complex jargon
B
Low vision -> large text
C
Hearing loss -> captions
Question 5
A
Characteristic: shaky hands
B
Requirement: tiny buttons
C
Effect: fewer mis-taps
Answer Key
From user characteristics to interface requirements
Section A: Quick Questions
Q1
B — Large text and high contrast colours
Q2
A — Simple wording and big, picture-based buttons
Q3
B — Each user characteristic is matched to a specific interface requirement
Q4
A — Clear labels and a simple, uncluttered layout
Q5
A — Provide captions for any video content
Section B: Match the Pairs
Q1
Characteristic: low vision -> Requirement: text size 18pt or larger → A user characteristic (low vision) is turned into a specific, measurable interface requirement (large text).
Q2
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.
Q3
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.
Q4
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 |
Q5
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.
Q6
Characteristic: young users -> Requirement: use technical jargon → The requirement does not suit the characteristic. Young users need simple wording, not technical jargon.
Section C: Definitions
Q1
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.Section D: Fill in the Blanks
Q1
User: low vision -> Requirement: large textQ2
User: young child -> Requirement:
simple wordingQ3
User: shaky hands -> Requirement:
large buttonsQ4
User: hearing
impairment -> Requirement: captionsQ5
Low vision -> large text -> easier to readSection E: Spot the Error
Q1
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'.
Q2
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.
Q3
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'.
Q4
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'.
Q5
B — Users with shaky hands find small targets hard to press. The requirement should be large buttons, not tiny ones, to reduce mis-taps.