Who is the service for?
Name location, role, language, device, familiarity, accessibility needs, support route, and the job they need to complete. Avoid assuming English alone is sufficient.
Operating conditions / select from actual evidence
Test the service where its users and operators will actually meet it.
South Africa contains varied people, languages, devices, networks, organisations, and operating contexts. Do not turn that variation into a generic claim. The client identifies the audience, supplies representative conditions, and obtains qualified advice for changing requirements.
Which formats are legitimate?
Test approved province, postal, telephone, company, VAT, date, number, currency, name, and identifier behavior. Make optional versus required information clear.
What personal data is necessary?
Connect adviser-approved POPIA and other responsibilities to fields, access, operators, direct marketing, vendors, transfers, security, retention, rights, and incidents.
How does money move and fail?
Separate ZAR or other display, contract, provider, fulfilment, invoice, tax owner, refund, settlement, and reconciliation.
What device and connection conditions matter?
Use evidence from the actual audience to set asset budgets, progressive loading, timeouts, retry behavior, interrupted states, and operator support.
Can people understand and recover?
Validate headings, labels, focus, keyboard use, contrast, status announcements, zoom, error prevention, efficient content, and direct assistance.
Fixture pack
Ask the organisation to approve representative conditions.
Build non-sensitive examples for language, formats, ZAR, personal-information choices, permission levels, representative devices, slow responses, dropped requests, duplicate actions, vendor outages, restore, and the operator response. Do not present a single connectivity or language assumption as universal.
Choose the condition most likely to interrupt the service.
That becomes an acceptance test and an operating control—not a marketing phrase.