Accessibility statement

Last updated 1 September 2026 · Version 1.0-draft

Draft — not yet reviewed by counsel.

This document is published so it can be read and corrected. It has not been through legal review and it does not yet bind anyone. If you are evaluating Rutba and need agreed terms, ask us and we will tell you where the review stands.

The short version

We build to WCAG 2.2 level AA. We have not been independently audited against it, so this page says partially conformant rather than claiming a certificate we do not hold, and section 3 names the specific things we know are wrong. If something stops you using Rutba, tell us and it becomes a defect with a severity — not a suggestion.

1. What we build to

The target is the Web Content Accessibility Guidelines 2.2, level AA, across the public site and every product interface.

In practice that means:

every interactive element reachable and operable by keyboard alone
a visible focus indicator that survives our own styling
text contrast of at least 4.5:1, and 3:1 for large text and interface components
semantic headings, landmarks and form labels rather than styled div elements
state that is announced rather than only shown — errors, loading, and the result of an action
no meaning carried by colour alone
layouts that reflow to 320px and survive 200% zoom without loss of content
respect for the reduced-motion preference

2. Where we actually are

Partially conformant. The platform is built to the standard above and has not been independently audited against it. Parts of it conform; parts of it have not been tested, and untested is not the same as conformant.

An external audit is planned as the products reach general availability, and this page will carry its date and findings when it has happened. Until then, this statement is based on our own testing.

The same distinction runs through the trust centre: what we are engineered against, and what we are certified against, are different claims and we do not blur them.

3. Known problems

A statement with an empty list here is a statement nobody checked. These are the areas we know are weakest:

Dense data grids. The tables that carry stock, ledger and order lines are keyboard-navigable but verbose with a screen reader, and the column headers are not always announced on a horizontal move.
Charts. Figures are rendered as SVG with a text summary; the summaries are not yet on every chart.
The document and spreadsheet editors. Rich editing surfaces are the hardest interfaces to make fully conformant and ours are not there yet.
PDF output. Invoices and reports we generate are not yet tagged for structure.
Third-party embeds. Where a page embeds something we do not control, its accessibility is not ours to guarantee, and we will say so on the page.

4. Assistive technology

We test with recent versions of NVDA and Windows, VoiceOver on macOS and iOS, and keyboard-only navigation in current Chrome, Firefox and Safari. Older combinations may work and are not tested.

5. Telling us something is unusable

Write to support@rutba.io with the page or screen, what you were trying to do, and what technology you were using. It becomes a defect with a severity rather than an item on a wish list.

We aim to acknowledge within 2 business days and to tell you what we are going to do within 10. If a fix will take longer than that, we will offer another way to do the thing you were trying to do.

6. If we do not fix it

If you are not satisfied with our response, say so and it goes to someone more senior. In the UK, the Equality and Human Rights Commission enforces the accessibility requirements that apply to services; in the EU, the enforcement body designated under the European Accessibility Act in your member state.

We would rather you told us twice than told them once, and we would rather you did both than neither.