Accessibility statement

We want Askobo to be usable by everyone, including people with disabilities. This page says what we aim for, what we have built in, where we know we fall short, and how to tell us about a barrier.

Last updated 22 October 2026 · Version 2026.10

At a glance

Our goal
We aim to meet WCAG 2.2 Level AA. We have not claimed conformance.
Themes
Light and dark.
Motion
Reduced when your device asks for reduced motion.
Report a barrier
[email protected]

What we aim for

In short: We aim to meet WCAG 2.2 Level AA. This is a goal, not a certificate.

We use the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as our target. We do not claim that Askobo fully meets it today, and we have not published an accessibility audit.

  • Semantic structure: We build pages with headings, lists and landmarks so the content has a clear structure.
  • Labels: We add labels to controls and use ARIA attributes where plain HTML is not enough.

Look and readability

In short: Light and dark themes, a minimum text size, and no colour-only meaning as a design rule.

  • Light and dark themes: You can use Askobo in a light or a dark theme.
  • Text size: Our design rule is that no text is smaller than 12.5px.
  • Colour: We aim for text that meets the WCAG contrast ratios of 4.5:1 for normal text and 3:1 for large text, and not to rely on colour alone to show meaning.
  • Zoom: We aim for pages that work when you enlarge text up to 200%.

Motion

In short: Animations are reduced when your device asks for it.

The animated parts of our public pages run only when your device has not asked for reduced motion. If you turn on “reduce motion” in your operating system or browser, those animations are switched off.

Keyboard and assistive technology

In short: We aim for every feature to work with a keyboard and a screen reader.

We aim for all features to be reachable with a keyboard in a logical order, with a visible focus indicator, and to work with screen readers. We have not published test results for particular screen readers or other assistive technology, so we do not list any as supported.

If something does not work with the tool you use, please tell us which tool and which page. See how to report a barrier.

Video, audio and meetings

In short: Live transcription is available where the host turns it on.

  • Transcripts: Where a host turns on live transcription, a transcript is available in the meeting.
  • Captions and audio description: We do not promise captions or audio description for every video. Videos that experts upload may not have them.

See Recording, AI and providers for how recordings and transcripts work.

Known issues

In short: Things we know are not yet where we want them.

  • We have not yet had an independent accessibility audit.
  • Content from experts, such as profile text, uploaded files, session materials and external links, is outside our control, and we cannot guarantee that it is accessible. We encourage experts to make their content accessible.
  • Video meetings and Zoom sessions run on provider tools whose accessibility we do not control.
  • Some parts of the site may not yet meet our goal. If you find one, please tell us.

Report a barrier

In short: Email us with what happened and where.

  1. Email [email protected].
  2. Describe the barrier and give the page address.
  3. Tell us which browser, device or assistive technology you were using, if any.
  4. Tell us how we could make it better, if you have an idea.

If you are not satisfied

For general questions, write to [email protected]. If you do not get a satisfactory answer, you can use our Grievance redressal process, which says how fast we reply and where to escalate.