User experience and accessibility for QCE Digital Solutions Unit 3
“Apply usability principles and accessibility standards, including WCAG, to evaluate and improve the user experience of a digital solution for a diverse range of users”
User experience is how usable, efficient and satisfying a solution is for diverse users; you evaluate it against usability principles (effectiveness, efficiency, learnability, satisfaction) and against the WCAG accessibility standard, whose POUR principles require content to be perceivable, operable, understandable and robust so people with disabilities can use it.
Jump to a section
What this dot point is asking
QCAA separates the visible interface from the broader user experience (UX), which is how usable, efficient and satisfying the whole solution is for real, diverse users. This dot point is about evaluating and improving UX against usability principles and against accessibility standards, specifically WCAG (Web Content Accessibility Guidelines). Accessibility means people with disabilities can use the solution; usability means everyone can use it effectively, efficiently and with satisfaction. Both are explicitly examinable and feed your IA1 and IA2 justifications.
Usability versus accessibility versus interface
These three terms are related but distinct, and mixing them up loses marks.
- The interface is the layout, controls and visual design (covered in the interface design dot point).
- Usability is how well any user can achieve their goals: effectiveness (can they complete the task), efficiency (how quickly), learnability (how easily a new user picks it up) and satisfaction.
- Accessibility is whether people with disabilities (vision, hearing, motor, cognitive) can use the solution at all.
A solution can have an attractive interface yet poor usability, and good usability for most users yet poor accessibility for some.
Usability principles
QCAA expects you to evaluate against recognised usability heuristics. Useful ones to apply:
- Visibility of system status: the solution tells the user what is happening (a loading spinner, a saved confirmation).
- Match to the real world: language and icons match the user's expectations.
- User control and freedom: undo, cancel and clear exits exist.
- Error prevention and recovery: validation stops mistakes, and messages explain how to fix them.
- Consistency: the same action looks and behaves the same everywhere.
- Efficiency: shortcuts and sensible defaults speed up frequent tasks.
The WCAG accessibility standard
WCAG organises accessibility around four POUR principles:
- Perceivable: users can perceive the content, for example text alternatives (alt text) for images, captions for audio, and sufficient colour contrast.
- Operable: users can operate the interface, for example full keyboard navigation and no time limits that cannot be extended.
- Understandable: content and operation are clear, for example readable language, predictable navigation and helpful error messages.
- Robust: content works with assistive technologies such as screen readers, which requires valid, well-structured markup.
WCAG defines conformance levels A, AA and AAA, with AA the common target for public solutions.
WCAG groups every accessibility guideline under four headings: Perceivable, Operable, Understandable and Robust. If you can recall POUR and give one concrete example for each (alt text, keyboard access, plain language, screen-reader support), you can structure an accessibility evaluation for any solution in the external exam.
Designing for diverse users
Diverse users include people who use screen readers, who cannot distinguish red from green, who navigate by keyboard only, who have limited literacy, or who use the solution on a small screen. Designing for them is not an add-on. Concrete moves include never using colour alone to convey meaning, ensuring a contrast ratio that meets WCAG AA, labelling every form field so a screen reader announces it, and making touch targets large enough.
Evaluating user experience
Evaluation should be evidence-based, not opinion. Methods QCAA recognises include usability testing with representative users completing real tasks, heuristic evaluation against the principles above, and accessibility audits against WCAG. You record what users struggled with, measure task success and time, then recommend specific improvements. In IA2 this evidence justifies your design decisions and demonstrates you designed for the user, not for yourself.
How this appears in assessment
IA1 asks you to design with the user in mind and justify choices against usability and accessibility. IA2 asks you to build and evaluate a solution, where UX evidence strengthens your evaluation. The external exam can ask you to identify usability or accessibility problems in a given scenario and recommend WCAG-aligned fixes, so practise turning a vague complaint into a named principle and a concrete change.
- Treating accessibility as optional polish. It is a core requirement; some users cannot use the solution at all without it.
- Colour as the only signal. Red-for-error with no icon or text fails users with colour blindness; pair colour with text or shape.
- Confusing usability with the interface. A pretty screen can still be hard to use; evaluate against task success, not looks.
- Opinion instead of evidence. Saying a design is intuitive is not evaluation; test with users and report what happened.
- Forgetting keyboard and screen-reader users. Mouse-only interactions and unlabelled fields lock out assistive-technology users.
Exam-style questions
Questions in the style of QCAA exam questions on this dot point, each with a worked answer. They are written by ExamExplained unless tagged "Past paper"; the year shows the paper a question is modelled on.
Practice4 marksA user interface symbolises a smart home system that manages plugs for efficient energy use. The home screen lists plugs alphabetically, users can group plugs, and schedules let users set on/off times. Evaluate the user interface of the smart home system to recommend two additional features that could improve accessibility. Justify your response.Show worked answer →
Two marks are for recommending two features that improve accessibility and two for justifying them, so pair each recommendation with a reason tied to a diverse-user need.
Recommendation 1 [1 mark]: a feature such as scalable text and high-contrast colour, or text labels alongside the on/off colour states. Justify [1 mark]: the interface currently signals on as white and off as grey, which colour-blind or low-vision users cannot reliably distinguish, so adding text or contrast makes status perceivable (a WCAG Perceivable requirement).
Recommendation 2 [1 mark]: a feature such as voice control or full keyboard/screen-reader support with labelled controls. Justify [1 mark]: users with motor or vision impairments cannot rely on precise taps on small plug icons, so an alternative input method makes the interface operable.
Markers reward an evaluative link to a specific accessibility need (perceivable, operable, understandable) rather than generic feature ideas.
Practice4 marksA high school is creating a map-based navigation app for new staff and students. Identify and explain two visual communication principles that could be implemented to ensure a good user experience while using the navigation app.Show worked answer →
One mark is for identifying each visual communication principle and one for explaining how it ensures a good user experience, so give two principles with an applied explanation each.
Principle 1, contrast [1 mark]: using high-contrast colours ensures unique elements stand out and that both the text and the map are easy to read, which supports accessibility and a good experience for users in varied lighting [1 mark].
Principle 2, harmony (consistency) [1 mark]: maintaining a consistent theme, for example similar icons such as squares or rectangles for buildings and consistent font styles and sizes for headings, gives the app a uniform, predictable feel that is easier to learn and navigate [1 mark].
Other principles (e.g. balance, alignment, proximity, hierarchy) earn the marks if each is correctly identified and its effect on the user experience is explained for the app.