Accessibility
Built for the person least likely to be comfortable using it.
Meeting the legal standard is the floor, not the achievement. We build to WCAG 2.2 AA as a baseline and then keep going — because she does not care what standard we met. She cares whether she can read it.
The numbers, and what they look like.
Not aspirations. Each of these is measurable, we measure it, and the demonstration beside it is live — rendered by the same stylesheet as the rest of the page.
- 44px
- Minimum touch targetEvery button and every link. A hand that shakes should still be able to use this. The WCAG floor is 24px; we hold ourselves to 44.
- actual size,
44 × 44 - 18px
- Minimum body textNever grey-on-grey, and pinch-zoom is never disabled. If you need it bigger, your browser is allowed to make it bigger.
This sentence is set at 18px.
- 45
- Languages, in their own scriptIncluding right-to-left, and romanised text where the script is unfamiliar. A font that breaks in Hindi is a bug, not a brand.
नमस्ते · مرحبا · 你好 · Xin chào
- 0
- Timers, anywhereNothing counts down at you. Nothing flashes, nothing auto-plays, and nothing expires while you are thinking about how to say it.
Session expires in 4:59
Take as long as you need.
The people most likely to need Keiro are the people least likely to be comfortable using it. Designing for anyone else would miss the point entirely.
So the target is not the confident user on a new phone. It is the person who has been quietly dreading this appointment for a week.
The choices behind those numbers.
Six promises. None of them are interesting on their own, and all of them are load-bearing.
- Every colour pairing on this site clears WCAG AA contrast, and the important ones clear AAA.
- If your device asks for reduced motion, every animation here turns off. Not softened. Off.
- You can reach everything by keyboard, every focused element is clearly outlined, and skip-to-content is the first thing you land on.
- Headings are real headings and forms have real labels, so a screen reader reads a document rather than a soup of divs.
- When Kai’s greeting changes language, it is announced, not silently swapped behind a screen-reader user’s back.
- Scripts render in fonts that actually contain their characters. A gorgeous Latin face that breaks in Hindi is a bug, not a brand.
Speaking, not typing.
Typing is a barrier we badly underestimate. It is hard on a cracked screen, hard with arthritis, hard in a script your keyboard barely supports, and hard when you are frightened.
So you can just talk, and switch mid-sentence without losing what you have already said. This is not a power-user feature. For a lot of our users it is the only way in.
Browser speech recognition is good at English and noticeably worse at exactly the languages our users speak. So when your browser is likely to do a poor job, Keiro quietly routes your voice to a stronger transcription model instead. You do not have to know that, or choose it. It just works better.
Or just talk. Typing on a cracked screen, in a script your keyboard barely supports, is a barrier we badly underestimate.
She is 72. Her phone is five years old and cracked in one corner. The clinic wi-fi is slow, her eyes are not what they were, and she is already worried about the appointment. If it does not work for her, it does not work.
Where we are still falling short.
It would be easy to end this page on the good part. Here is the honest state of it instead.
No formal audit
Keiro has not been independently audited for accessibility. Our confidence comes from building carefully to a standard, not from a certificate.
Not tested with the people it is for
We have not sat with a panel of screen-reader users or older users and watched them use it. That is the single biggest gap, and we know which one it is.
It still assumes you can read
Not every one of the 45 languages has been checked by a native speaker yet, and the conversation still leaves out people who cannot read at all.
If you use a screen reader, or you help older or disabled patients, and something here is broken or patronising, please tell us. That kind of message is worth more to us than any audit.
Designing for fear, not just for eyesight.
Does it work on an old phone?
That is the target, not the edge case. The site stays light and avoids heavy graphics, and it is tested at small screen sizes. If it is slow or broken on your device, we would genuinely like to know which device.
Do I need to be good with technology?
No. If you can open a web page and talk, you can use Keiro. Nothing to install, no account to make, no settings you have to get right first.
Will it rush me?
No. Kai has no timer and no progress bar shaming you for taking your time. It does not sigh, it does not repeat itself impatiently, and it never implies you should have known better. You can start a sentence over as many times as you need.
Can someone help me use it?
Yes, and a lot of people do it that way, an adult child holding the phone while a parent talks. Nothing about Keiro assumes the patient is the one tapping the screen.
Is it accessible if I cannot see the screen?
It is built to be: real headings, real labels, keyboard navigation, and announcements when content changes. But we have not yet tested it with a panel of blind users, so we will not claim more than that.
More about what Kai will and will not do in meet Kai, and what happens to your words in privacy & safety.