11Trust · Accessibility

Accessibility

Last updated: 2026-04-25 · Pre-launch · partial conformance

Jubi should be usable by people who rely on assistive technology. This page is honest about where we are with that today, and how to tell us when we've fallen short.

Our commitment

We treat accessibility as part of normal engineering, not a checklist applied afterward. The goal across the marketing site and the customer console is keyboard-first navigation, semantic markup, contrast that holds up at AA, text that scales, and interaction that doesn't surprise.

Standard we work to

Our target is the Web Content Accessibility Guidelines (WCAG) version 2.2, conformance level AA, as published by the World Wide Web Consortium. This is the most commonly referenced standard in enterprise procurement and aligns with the EU's EN 301 549 reference standard for digital accessibility in public-sector procurement.

What we test

Keyboard-only navigation across primary user journeys.
Screen reader compatibility on major combinations: NVDA on Firefox/Chrome (Windows), VoiceOver on Safari (macOS / iOS), TalkBack on Chrome (Android).
Colour contrast against WCAG 2.2 AA thresholds.
Browser zoom up to 200% without loss of content or function.
Reduced-motion preferences for users who prefer minimal animation.

Known limitations

Pre-launch, the following are known to fall short of full WCAG 2.2 AA conformance and are scheduled for improvement:

Some marketing-site diagrams use SVG without complete text alternatives. We are adding accessible descriptions and where relevant a text-only equivalent.
The dashboard widget embedded in Metabase inherits aspects of Metabase's UI that we do not control; accessibility there depends in part on Metabase upstream.
Charts and visualisations generated by the assistant are being upgraded to expose underlying data tables for screen-reader users.

This list is not exhaustive. We do not warrant full WCAG conformance pre-GA; specific accessibility commitments at GA will be set out in the engagement.

How to report an accessibility issue

If something is blocking you, please tell us. Email hello@jubi.my with:

The page or feature affected and the URL where applicable.
The assistive technology and browser you were using (e.g. "NVDA on Firefox 122 on Windows 11").
What you expected to happen and what happened instead.

We'll acknowledge reports promptly and work on material barriers in a reasonable timeframe. If the proper fix takes a while, we'll often offer a workaround so you're not stuck in the meantime.

Alternative formats

Need our published materials (architecture documents, security overview, terms, privacy notice) in large print, plain text, or a screen-reader-optimised version? Email hello@jubi.my and we'll do what we can.

Procurement accessibility documents

For procurement teams that require an Accessibility Conformance Report (ACR) under the Voluntary Product Accessibility Template (VPAT) format, or a section-by-section EN 301 549 statement, email hello@jubi.my for the current version. We will indicate where conformance is partial and what we are working on.

Accessibility issues: hello@jubi.my · ACR / VPAT requests: same address

Disclaimer. This page describes our current accessibility intent and posture. It is not a warranty. We do not commit to remedying every reported issue, to a specific remediation timeline, or to full WCAG 2.2 AA conformance prior to GA. Specific accessibility commitments applicable to a given customer are set out in the customer engagement and supersede anything stated on this page. Where this statement is required to align with a specific regulation (such as the EU Accessibility Act, Section 508, or local equivalents), the customer is responsible for assessing applicability to its use case and configuring its deployment accordingly.