Kamano

Accessibility

Last updated:

We aim for the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, on this site and in the app. This is where we say what that means today, and where we fall short.

What we have done

  • Everything works with a keyboard, with a visible focus outline. A skip link to the main content is on this site, not yet in the app.
  • Pages use headings, landmarks and lists so a screen reader can move around them.
  • Text and controls meet WCAG 2 contrast (4.5 to 1 for text, 3 to 1 for controls) and we also check them against APCA. The colours come from one theme that is checked by tests, and it follows your device's light or dark setting.
  • In the app, every colour a member picks is made readable by us before it is used. We never apply someone else's colours to your screen.
  • Text resizes and reflows to a small phone width without sideways scrolling.
  • Motion is switched off when your device asks for reduced motion.
  • Colour is never the only way we show something.
  • Every place or person on the globe is also in a list, so nothing depends on seeing or pointing at the map.

What is not there yet

  • The globe is a drawn map. A screen reader cannot read the map itself, only the list that mirrors it.
  • We have not yet had the app audited by an outside specialist. One is planned before public launch.
  • The app is in English only for now.

Telling us about a problem

If something does not work for you, tell us what you were trying to do, what happened and what device or assistive technology you use. We will reply, and we will tell you when we can fix it, or why we cannot.

Accessibility
Contact form

Review

Drafting note: Replace the gaps list with the audit findings once the WCAG 2.2 AA audit is done (docs/launch-gates.md, section C), and confirm any accessibility statement your market requires.