Digital Technologies 1.3 · Level 1 · 5 credits · External
Everything in this unit is exam preparation.
The standard
That is the Achieved wording. Merit and Excellence change the verb.
The verb progression
demonstrates understanding
→ examines
→ evaluates
Quoted from the achievement standard
Achievement Criteria and Explanatory Note 1 — quoted, not paraphrased.
The one sentence that matters
Excellence adds exactly two things:
a comparison
and a principle-grounded improvement.
Excellence is not
“the same answer, longer.”
The chain — on the board all week
Which links earn which grade
“Tell me what this interface is for, point at something a person could actually see or click, and name the principle it uses. If I can't picture the thing you're pointing at, you haven't described it yet.”
“Now tell me how that feature applies the principle, what changes for one named person doing one exact task, and why that matters to what the interface exists to do. If your sentence would still be true about a completely different app, it isn't an explanation.”
“Take the same action in two interfaces. Say which one does it better and why, using the principles. Then propose a specific change that isn't already there, and say what it would do for that person. That's evaluation.”
Now watch the difference
These three paragraphs were written to make the difference visible. They are not NZQA exemplars.
CityLink Events exists to help people find local events and keep track of the ones they want to go to. In Interface B, after the user selects “Save event”, a message appears reading “Saved: Harbour workshop”, with an “Undo” option beside it. This uses visibility of system status, because the interface tells the user what it has just done. The Undo option also uses user control and freedom, because it gives the user a way back out of an action they did not mean to take.
Why it stops here
Purpose named. A feature you could point at. Two principles, with their use described.
No mechanism. No named user. No comparison.
Interface B applies visibility of system status by returning a written confirmation that names the specific event: “Saved: Harbour workshop”. How it does that matters for Sam, who has low vision. She does not have to notice a small change in a star icon, and she does not have to remember which row she was on when she clicked, because the interface states both the outcome and the thing it happened to. She can also enlarge that text with the A+ control, which she cannot do to an icon's colour. This removes the step where an uncertain user clicks a second time to check — the step that produces duplicate saves and, worse, a user who arrives on Saturday without the event stored at all. Because Sam can confirm the save at the moment she makes it, the site is better able to do what it exists to do.
Why it's a Merit
Explains how the principle is applied. Traces the mechanism through a named user on an exact task. Reaches the interface's purpose.
Still no comparison. Still no improvement.
For the same action — saving the Harbour workshop and confirming it is saved — Interface A gives Sam a star icon that changes state, with no words and no named confirmation, while B returns “Saved: Harbour workshop” with an Undo beside it. B is more effective for Sam on this task. On visibility of system status, A requires her to perceive a small graphic change and infer which event it belongs to; B states the outcome and the object together. On user control and freedom, A offers no visible route back from a wrong save, whereas B's Undo sits inside the same message. On accessibility, B carries availability in text while A encodes it in a colour key she may not be able to use at all.
A is not simply the worse design: it shows more events per screen, so a user who can scan quickly gets more information for less scrolling. That compactness is a genuine trade-off, not a fault.
Two improvements to A. First, give A's star a text label that changes to “Saved” when the event is stored — this applies visibility of system status and gives Sam B's confirmation without giving up A's compact layout. Second, mark availability with text or a shape as well as colour, so meaning is not carried by colour alone — this applies accessibility. Neither change is already present in A.
One limit: a static mock-up cannot show whether either interface is keyboard-operable or whether focus is visible, so I cannot judge the keyboard part of Sam's task from this evidence.
Why it's an Excellence
One per grade. Each has a one-line fix.
Writing the definition of a principle instead of its use. “Error prevention is when the design stops errors before they happen” is a definition — alone it scores nothing, because the criterion asks for principles and their use.
“Point at it. What would I see on the screen?”
Replacing the mechanism with an adjective — “easier”, “more user-friendly”. Conclusions with the reasoning deleted, true of almost any interface.
Second most common: stopping at the user and never reaching the interface's purpose.
“Easier for whom, at which exact step, compared with what?”
Writing more rather than differently — a longer Merit with no comparison. Where they do compare, comparing unlike things: a feature in A against a different feature in B.
Close behind: proposing an “improvement” the interface already has.
“Same action in both. Which one, and why? What would you change that isn't already there?”
Where each task sits
Section
Teach both moves
Test the claim.
Supply an example.
A student trained only to test claims can freeze in the exam and score nothing.
An always-safe base they can write from
Give them this so they always have something honest and specific to write.
Sorting task · can you make it fit?
Rank each claim: strongly evidenced · possible but incomplete · better explained by ordinary HCI.
The honest position
NZQA sets the standard and the assessment. In the 2025 examination Resource A, rangatiratanga was operationalised as users having control over the interface. Recognise that wording and use it.
And then name one limit — one sentence on what the concept covers that the interface analysis does not reach.
Naming a limit is not hedging.
It is the difference between an assertion and an argument — and it is what a marker reading for depth is looking for.
Hold this line
Tino rangatiratanga is not
a synonym for “user control”.
Comparison is legitimate. Conflation is not.
Exam transfer
One explanation, linking:
A calibration note
Our pages insist on a trade-off. The standard asks only for comparison + improvement.
Treat the trade-off as what makes a judgement convincing — not as a gate that costs a grade.
Verify these — do not assume
The whole unit, in one line
Point at it. Explain what it does to somebody.
Then compare it, and improve it.