← VCE Software Development U3O2

Design criteria for an interface

Checkable standards, such as easy to read, easy to navigate or meets the requirements, that an interface is designed to meet and then judged against.

Part of: VCE Software Development - U3O2 - Analysis and Design — Module 89, VCE Data Analytics - U3O2 - Analysis and Design — Module 139, 9-10 Digital Technologies: Designing user interfaces and experiences — Module 10, QCE Digital Solutions Unit 1 — User Experiences and Interfaces — Module 40

Understanding Design criteria for an interface in VCE Software Development U3O2

What it does: The vague requirement becomes a checkable accessibility criterion with a measurable target. Counting the colours used lets the designer check the look of the interface against a standard. A criterion must be checkable. You can count the taps, but you cannot test 'really good'. Turning a requirement into a criterion means making it specific and testable. Text size and contrast can be measured, while 'looks nice' cannot. Usability criteria are about how easy and efficient the interface is to use. Using brand colours is an aesthetic criterion. Accessibility criteria make sure people with different needs can use the interface. Alt text helps users who cannot see the images.

Common mistakes: A design criterion must be checkable. 'Does it look nice?' is just an opinion. The test should measure the font size against the 16pt criterion. This criterion is vague and cannot be checked. A usability criterion for 'easy to navigate' needs a measurable standard, such as 'Any page in 3 clicks'.

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 Design criteria for an interface to a class →

This module's key terms are also in a printable crossword (Modules 86–109) and word search (Modules 86–119).

Take this worksheet further — free with Cloodit

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

Learning
Duo
Which is a checkable design criterion for a school canteen app?
The app should be really goodStudents can place an order in 4 taps or fewer
Matches
Criterion: The app should look nice
↓
Too vague. 'Nice' cannot be checked, so the design cannot be judged against it. Use something like 'uses no more than 3 colours and a consistent font'.
Applying
Meanings
Term
design criteria
Meaning
Checkable standards, such as easy to read, easy to navigate or meets the requirements, that an interface is designed to meet and then judged against.
Practice
Requirement: Easy for teens to read
Testing
Gaps
: Menu is visible on every screen
Check Answer
Spots
2crit ← "Text is 16pt or more"
3test ← "Does it look nice?"

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

The 'Butterfly' badge — Branch Hopper, 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. Which is a checkable design criterion for a school canteen app?
A. Students can place an order in 4 taps or fewer ✓
B. The app should be really good
A criterion must be checkable. You can count the taps, but you cannot test 'really good'.
2. A client says: 'Our app must work for people with low vision.' What is the best criterion to turn this requirement into?
A. Body text is at least 16 pt with high contrast against the background ✓
B. The app looks nice on every phone
Turning a requirement into a criterion means making it specific and testable. Text size and contrast can be measured, while 'looks nice' cannot.
3. Which one is a usability criterion?
A. The logo uses the school's colours
B. A new user can find the settings page without help ✓
Usability criteria are about how easy and efficient the interface is to use. Using brand colours is an aesthetic criterion.
4. Which one is an aesthetic criterion?
A. Every button can be used with a screen reader
B. The screens use the same 3-colour palette and font throughout ✓
Aesthetic criteria are about how the design looks and feels. Screen reader support is an accessibility criterion.
5. Which one is an accessibility criterion?
A. All images have alt text that describes them ✓
B. The home screen loads with a fun animation
Accessibility criteria make sure people with different needs can use the interface. Alt text helps users who cannot see the images.

Match the Pairs

Criterion: Text is at least 16pt → A usability or readability criterion that can be checked by measuring the font size
Criterion: Any page is reachable in 3 clicks → A usability criterion about navigation that can be tested by counting clicks
Turning a requirement into a criterion: the app must be usable by people with low vision → Requirement: low vision users -> Criterion: contrast ratio of at least 4.5:1
An aesthetic criterion makes the look of the design checkable → Criterion: Uses only the 3 brand colours
Criterion: The app should look nice → Too vague. 'Nice' cannot be checked, so the design cannot be judged against it. Use something like 'uses no more than 3 colours and a consistent font'.
Requirement: easy for everyone -> Criterion: easy for everyone → The requirement was copied, not turned into a criterion. It needs a measurable standard, such as 'a new user finishes the task in under 2 minutes'.

Key Term

design criteria
Checkable standards, such as easy to read, easy to navigate or meets the requirements, that an interface is designed to meet and then judged against.

Fill in the Blanks

1. Requirement: Users can find the menu fast Criterion: Menu is visible on every screen
Hint: Type the word for a checkable standard that is written from a requirement.
2. Type: usability Criterion: Users reach checkout in 3 taps
Hint: Type the category of criteria about how easy an interface is to use.
3. Type: aesthetic Criterion: Colours and fonts look consistent
Hint: Type the category of criteria about how the design looks.
4. Type: accessibility Criterion: Every image has alt text
Hint: Type the category of criteria about making the interface usable for people with different needs.
5. Requirement: App must be easy to read Criterion: Body text is at least 16 px
Hint: Type the label for what the client or users need, which criteria are turned from.

Spot the Error

Question 1
A need ← "Easy to read"
B crit ← "Text is 16pt or more"
C test ← "Does it look nice?"
Line C — A design criterion must be checkable. 'Does it look nice?' is just an opinion. The test should measure the font size against the 16pt criterion.
Question 2
A need ← "Easy to navigate"
B crit ← "Menu is nice to use"
C test ← "Count clicks per page"
Line B — This criterion is vague and cannot be checked. A usability criterion for 'easy to navigate' needs a measurable standard, such as 'Any page in 3 clicks'.
Question 3
A type ← "aesthetic"
B crit ← "Images have alt text"
C test ← "Check each image"
Line A — Alt text helps users who rely on screen readers, so it is an accessibility criterion, not an aesthetic one. Line 1 should be type ← "accessibility".
Question 4
A maxCols ← 3
B cols ← 2
C IF cols > maxCols THEN pass
Line C — The criterion allows 3 colours or fewer, so the design passes when cols <= maxCols. Using > passes designs that break the criterion.
Question 5
A minRatio ← 4.5
B ratio ← 7
C IF ratio >= minRatio THEN fail
Line C — A contrast ratio of 7 meets the minimum of 4.5, so the design meets the accessibility criterion. The result should be pass, not fail.

Student with a class code? Join your class →