OIO

Accessibility

Last updated: 2026-10-01

OIO should work for everyone who runs client work, including people who use a screen reader, navigate with a keyboard, zoom in, or need reduced motion. This page says where we stand today and how to tell us when something gets in your way.

Our target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1, level AA. OIO has not yet been audited by an independent party, so we describe it as partially conformant: most of the app meets the standard, some parts do not yet.

What we support

  • Buttons, inputs and menus are real HTML controls with text labels, so screen readers can name them.
  • The main apps can be used with a keyboard, with a visible focus indicator. Escape closes popups and cancels edits.
  • Text can be zoomed to 200% in the browser without losing content.
  • Several colour themes, including light and dark, so you can pick the contrast that works for you.
  • The website respects your system's reduced-motion setting.
  • Recordings can be transcribed to text, and transcripts can be exported as captions.
  • The interface is available in many languages.

Known gaps

These parts are harder or impossible to use without a mouse or without sight today:

  • Whiteboard: the canvas is visual and pointer-based; notes and connectors are not fully reachable by keyboard or announced to screen readers.
  • Timeline and kanban: moving bars and cards relies on drag and drop. The same changes can be made in the item's edit popup.
  • Charts and some status colours: a few views use colour as the main signal.
  • Marketing videos on the website do not all have captions yet.

We fix these as we go and update this page when we do.

Report a barrier

If something in OIO blocks you, write to [email protected] with the page and what happened. We aim to reply within 5 business days and, where we cannot fix the problem quickly, to help you get the task done another way.

Technical details

OIO is a web application built with HTML, CSS, JavaScript and WAI-ARIA. It is tested in current versions of Chrome, Safari, Firefox and Edge, on desktop and mobile.