Accessibility
Last updated: 24 September 2026
AnybanQID is how people prove who they are, approve payments and sign documents. If someone cannot read what they are being asked to approve, that is not only an accessibility problem — it means a signature was given without informed consent. So we treat this as part of the security of the service, not a separate exercise.
This page says plainly where we are. It is not a claim of full conformance.
What we aim for
We work to WCAG 2.1 Level AA and the equivalent mobile platform guidance from Apple and Google. Sri Lanka's Personal Data Protection Act does not set accessibility rules for a private service, so this is a standard we hold ourselves to rather than one imposed on us.
What the app does today
- Screen readers. Buttons and controls are labelled for TalkBack and VoiceOver, including the approve button, the home screen actions and the identity card, which is read as one credential rather than scattered fragments.
- Larger text. The app follows your device text size. We do not cap or override it, and layouts reflow instead of clipping.
- Contrast. Text meets the 4.5:1 ratio in both light and dark themes, including the status labels that tell you whether you can sign.
- Not colour alone. Status is always carried by words and an icon as well as colour.
- Reduced Motion. If you have turned it on, animations are switched off rather than softened.
- Announcements. Time-sensitive changes — a request running out, a step completing — are announced rather than changing silently.
- Biometrics are optional. If fingerprint or face recognition does not work for you, a PIN does the same job.
- Three languages. The app is available in English, Sinhala and Tamil.
Where we fall short
These are known, and we would rather say so than let you discover them:
- Approval requests expire and cannot be extended. The time limit is what stops a request being captured and replayed later, so we keep it — but it means anyone who navigates more slowly, including screen reader users, may run out of time and have to ask the service to send a new request. We are measuring how long the screen actually takes to navigate with a screen reader, and will set the limit from that.
- We have not yet tested on real devices with assistive technology. The work so far was done by reviewing the app's code. Testing with TalkBack, VoiceOver, Switch Control and 200% text on physical phones is scheduled, and will almost certainly find things this page does not list.
- We have not heard the app read aloud in Sinhala or Tamil. The text is translated; how a screen reader pronounces it is untested.
Tell us about a problem
If something in the app is hard or impossible to use, please email sasith@clobe.lk with the screen you were on and what happened. You do not need to know the technical cause or name a guideline.
We aim to reply within five working days. If a problem stops you completing something — signing in, approving a payment, signing a document — tell us and we will help you complete it while we fix the underlying issue.
Changes
We will update this page as we fix what is listed above and as device testing finds more. The date at the top says when it last changed.