Accessible use cases for stronger digital services

Accessible services begin with a clear account of what people are trying to do and what may stop them. Writing use cases that include accessibility requirements starts with those barriers, alternatives and measurable outcomes, rather than discovering them during a late audit. This benefits people with disability, older users, mobile-first customers and Australia’s culturally and linguistically diverse communities.

Australian use cases often involve imperfect conditions. A passenger may top up an Opal card on a crowded train in Sydney, compare insurance on a phone during a Melbourne commute, or complete a government form in Brisbane while caring for relatives. Patchy regional connectivity, public transport disruptions and time pressures make unclear labels, tiny controls and lost form entries especially costly.

Accessibility is also a legal and commercial concern. The Disability Discrimination Act 1992 and related state and territory laws may require reasonable adjustments, while Australian Government websites and apps must meet WCAG 2.1 AA. Banks, retailers, healthcare providers and travel platforms compete for Australian customers, so poor access can mean lost business as well as non-compliance.

UCDmanager gives teams a free, shared workspace for connecting user roles, personas, use cases and evaluation findings. Users can explore a demonstration project or create their own, then document requirements, trace decisions and coordinate research. That shared record creates a practical bridge between user needs, design decisions and delivery.

Start with the person and the task

Begin with the person, not a generic “user”. Define the user role, relevant persona attributes, trigger, goal and context. A person who uses a screen reader and magnification may need the same outcome as another customer but a different route. Record assistive technology, device, language and environmental constraints only when they affect the task.

A useful use case states preconditions, primary steps, alternate paths, postconditions, business rules and failure handling. Make each flow observable: what the person does, what the system responds and what can be completed. This detail supports design, implementation and testing.

Teams can export use cases for integration with development tools, then retain requirement IDs and accessibility notes in the linked work item. The export guide explains this handoff. Shared identifiers preserve traceability when an alternate flow becomes a backlog item or a test case.

Define inclusive preconditions and flows

Include accessible alternatives in the flow itself. A booking flow might support keyboard-only completion, clear focus, meaningful error recovery and a confirmation that works without colour. Describe what happens when captions are unavailable, a session expires, or a person needs more time. These alternate flows are part of the core journey, not optional extras.

Translate broad goals into acceptance criteria. For example, require a 44-by-44 CSS pixel target, visible focus, content that reflows at 400% zoom without loss, and form fields with programmatic labels. WCAG 2.1 AA is the baseline, while research may identify needs beyond it.

Content decisions belong in the same scenario. Specify plain-language instructions, correct heading order and alternatives for informative, decorative and complex images. For product imagery, teams can generate image descriptions as a starting point, then have a person review the result for context, sensitivity and whether it conveys the intended meaning.

Turn accessibility into acceptance criteria

Write criteria so another person can test them without guessing. Use statements such as “AC-01: A keyboard-only user can reach and activate every control” and “AC-03: A screen reader announces the updated search result count”. Link each criterion to the use case step and relevant WCAG success criterion. Record platform and assistive technology in the test evidence.

Cover content and communication requirements as carefully as interaction behaviour. Define page language, descriptive link text, caption and transcript availability, form instructions, error summaries and recovery routes. For time-sensitive tasks, specify warnings and ways to save progress. An accessible error message must identify the problem, preserve entered data and say how to proceed.

Documents require their own requirements. A downloadable form might need tagged headings, logical reading order, labelled fields and an accessible alternative. Authorised content staff can edit a secured PDF to remediate such assets, then include the tagged export, source file and verification result in the use case evidence.

Validate flows with real users

Validate use cases through automated checks, expert review and usability sessions. Include people who use keyboards, VoiceOver, NVDA or JAWS, plus participants with low vision, motor or cognitive disability. Recruit for the task context rather than relying only on internal volunteers.

Remote testing can reach participants beyond major cities, but a connection failure may itself affect the task. Provide a low-bandwidth fallback and observe whether the service can resume without losing work. Auslan interpreters or translated instructions may also be needed when communication is part of the scenario.

The same scenarios can validate navigation flows by checking landmarks, heading structure, skip links, focus order, back behaviour and error recovery. This method helps teams distinguish a content defect from a structural problem. Record each observation against the relevant step, acceptance criterion and persona so teams can prioritise the same evidence.

Build a reusable quality checklist

A reusable checklist keeps accessibility visible across discovery, build and release. In UCDmanager, assign an owner and status to each accessibility requirement, attach evaluation evidence and resolve issues before release. This turns a broad goal into accountable, traceable work.

Content and comprehension criteria belong in the scenario and its acceptance criteria:

Interaction checks should be equally specific, because a clear screen does not guarantee an operable task. Test the full flow rather than isolated components and include failures, interruptions and recovery.

Keep each use case current. When research, legal guidance or platform behaviour changes, revise the flow, acceptance criteria and evidence together so the documented journey remains a dependable source of truth.