KeenaBack to site

Good to know

Accessibility

Last updated 29 July 2026

Deciding where to go with your friends should not depend on how you use a computer. This page is an honest account of where Keena stands, including the parts that are not done.

We are working towards WCAG 2.2 Level AA, not claiming it. Parts of Keena have had a proper accessibility pass and parts have not. Rather than publish a conformance claim we have not measured, the current state is set out below.

What is in place

  • Keyboard navigation: interactive elements are reachable and operable without a mouse, in a logical order.
  • Visible focus: a high-contrast focus ring appears on keyboard focus and meets the 3:1 contrast the standard asks of focus indicators.
  • Reduced motion: if your system is set to reduce motion, looping and scroll-linked animation is switched off. Feedback that tells you something happened is kept; decorative movement is not.
  • Touch and pointer: hover effects are gated to devices with a real pointer, so they do not stick after a tap on a touchscreen.
  • Semantic structure: headings, landmarks and lists are used for what they are, so screen readers and reader modes can navigate the page.
  • Text alternatives: meaningful images carry descriptions; decorative ones are hidden from assistive technology rather than announced as noise.
  • Text contrast: body and interface text is checked against WCAG AA contrast ratios.
  • Resizing: layouts use relative units and reflow rather than breaking when text is enlarged or the window is narrow.

Known gaps

Things we know are not there yet:

  • The application itself (dashboard, lists, calendar and map) has not had a full audit against WCAG 2.2 AA. The marketing site has.
  • The map view is inherently visual and does not yet have an equivalent non-visual way to browse places by location.
  • Some drag-based interactions do not yet have a documented keyboard equivalent.
  • We have not completed testing with screen readers across every combination of browser and platform.

These are on the list. If one of them is what stands between you and using Keena, tell us: it moves things up the list faster than anything else.

Assistive technology

Keena is built with standard web technology and should work with screen readers, screen magnifiers, speech input and browser zoom. If it does not work with the setup you use, that is a bug and we want to hear about it.

Tell us what is broken

Email hello@keena.app with what you were trying to do, the page you were on, and the assistive technology, browser and operating system you were using. That last part genuinely helps us reproduce it.

We aim to reply within five business days and to tell you either when it is fixed or why it will take longer.