Accessibility

We target WCAG 2.2 Level AA. This page says where we meet it, where we do not yet, and how to report something that blocks you.

Last updated 26 August 2026

What we have done

  • Every interface is operable by keyboard alone, with a visible focus indicator that meets the contrast requirement — not a browser default we suppressed and forgot to replace.
  • Semantic structure throughout: real headings in order, real lists, real tables with header cells associated to their rows and columns, and landmarks that are uniquely named where more than one exists.
  • Text meets 4.5:1 contrast, and interface components and focus indicators meet 3:1, in both light and dark themes.
  • Status changes — a readability verdict, a save, an error — are announced to assistive technology rather than only appearing visually.
  • Colour is never the only carrier of meaning. The readability verdict states its result in words, and the plan comparison marks inclusion with an icon that has a text label.
  • Decorative imagery is hidden from assistive technology; QR previews carry a description of what the code is for rather than the literal payload.
  • Motion is limited and respects prefers-reduced-motion. Nothing autoplays, flashes, or moves on a loop.

Where we fall short

Stated specifically, because a page that claims full conformance without qualification is usually the least trustworthy kind:

  • The design panel is visually driven. Choosing module shapes, eye styles and gradients is a fundamentally visual task, and while every control is labelled and keyboard-operable, the result is only conveyed visually. The readability verdict is the non-visual substitute, and it is a partial one.
  • The comparison table on the pricing page scrolls horizontally on narrow screens. It is keyboard-scrollable and marked up correctly, but a wide table remains harder to navigate with a screen reader than the information deserves.
  • We have not commissioned an independent audit. The claims above come from our own testing with keyboard navigation, automated checks and screen-reader spot checks — which is not the same as an expert review, and we will not imply otherwise.

Assistive technology we test with

Keyboard-only navigation on every release; VoiceOver on macOS and Safari; NVDA on Windows and Firefox; and browser zoom to 200% with reflow. We do not currently test with voice control or switch access.

Tell us

If something here blocks you, email support@saiberlab.com and say what you were trying to do and what got in the way. Accessibility defects are treated as functional defects, not enhancements, and we will tell you when it is fixed rather than closing the thread quietly.

If you need something from this site in another format while we fix it, ask and we will provide it. Other ways to reach us are on the contact page.