These settings change how this site looks in your browser and are remembered next time you come back. Nothing is sent anywhere: they are stored on your device.
There is no "screen reader" button here: this site is built to work with the screen reader you already use, and a pretend one on top would only get in its way.
Accessible cybersecurity
Someone who can't read a CAPTCHA asks for help. Someone who can't type their password dictates it to another person. Every accessibility barrier left unsolved ends up as a security hole.
Data
Our key differentiator
Whatever can be resolved inside the device is resolved inside the device.
This is not an ideological stance: the less data that leaves, the less surface there is to protect and the less we have to ask people to trust us.
It is also what lets us in where other tools cannot go. In a health centre, a law firm or a public administration, the conversation does not start with price: it starts with what leaves the machine. If the gesture and the context never leave, there is nothing to negotiate.
When something does have to leave the device, we say so explicitly and explain what for. The formal detail will be in the privacy policy.
How we approach it
Hidden screen and private audio. It lets the device be used in a waiting room, an open-plan office or on public transport without sensitive information being visible — or audible — to whoever is next to you. For many people, today's alternative is not doing the task until they get home.
Visual CAPTCHAs shut out millions of people with visual impairments, and audio alternatives break down with background noise or a screen reader in the mix. Our CAPTCHA verifies that there's a person there from the way they gesture, which is hard to automate and requires seeing nothing.
Open framework
The Open Source Cybersecurity Framework is our open framework for accessible cybersecurity. It documents AGVS, the Accessible Gesture Verification Standard, and is published in the open with its source and change history visible.
We didn't write it as decoration. An accessible verification standard is only worth anything if other people can read it, implement it and argue with it — and for that it has to be public before it's finished.
What AGVS solves, and what it deliberately leaves out.
Replay of recorded gestures, automation, shoulder surfing and session abuse.
Rules for making the verification challenge usable multimodally, not just by looking.
Three levels — A, AA and AAA — so an implementation can show how far it goes.
Standards
AIntegra is not certified against any of these standards yet. The product is designed to meet them and we are working towards certification. When we hold a certificate, we'll publish it with its number and its certification body. Until then, putting it any other way would be selling you something we aren't.
If you're evaluating a public procurement or an internal rollout, tell us what's required of you and we'll tell you exactly where we stand.
