Accessibility Statement

KubixDesiney wants everyone - including people using a screen reader, a keyboard only, or with low vision or color-vision differences - to be able to find a product, read our documentation, and reach our team. This page is an honest account of where the site stands, not a claim of finished work.

1. Conformance target

We measure this site against the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA.

2. Conformance status

KubixDesiney is partially conformant with WCAG 2.2 AA. "Partially conformant" means some parts of the site meet Level AA and some do not - we would rather tell you exactly which is which than claim a badge we have not earned. Section 4 below lists every gap we currently know about.

3. What we've done

This statement follows a full audit of the codebase on the date below. In that audit we:

• Measured the contrast of every text color against the surfaces it actually sits on. Body text, muted text, and status colors all measure at or above 4.5:1 (large headings and UI controls at or above 3:1). We found and fixed two colors that fell short: the "Delete account" button and heading, now switched to the site's already-audited alert red (5.5:1+ on our dark surfaces), and the default link color inside this page and our other legal pages (Privacy, Terms, Cookies, Sub-processors), which measured 4.27:1 and is now 7.1:1.
• Connected every form field on the site to its visible label with a properhtmlFor/id pairing (roughly 60 fields, across the sign-up, sign-in, checkout, support-ticket, demo-request, review, and account-management forms), so a screen reader announces "Work email, edit text" instead of just "edit text."
• Made the FAQ accordion on the support page keyboard-operable - it was a clickable <div> with no keyboard handler; it is now a real button with aria-expanded and aria-controls.
• Added a visible-focus-respecting Escape key and a proper aria-labelledby to the dialog used for demo requests, quote requests, and account deletion, and gave decorative icons (the arrow, check, and brand marks used throughout the site) aria-hidden so a screen reader doesn't announce an unlabeled graphic next to text that already says the same thing.
• Gave toast confirmations (e.g. "Demo requested") a live region, so they're announced instead of only appearing visually.
• Confirmed the motion and scroll-reveal system (which briefly hides content until it animates into view) cannot leave content permanently invisible: it has a 2.5-second fallback if the animation script never loads, a further backstop if the reveal observer stalls, and a plain-CSS fallback for anyone with "reduce motion" set in their operating system.
• Verified the product documentation tabs and the star-rating review widget already use correct tab/tabpanel roles, arrow-key navigation, and a labeled rating control.

4. Known gaps

These are the issues we know about and have not yet fixed. We'd rather list them than hide them:

• Reading order on the product page. On a product's detail page, the product name (the page's heading level 1) sits inside a sidebar card that comes after the "About" and "Key capabilities" sections in the underlying markup, even though it appears first visually. A screen reader user hears those two sections before ever hearing the product's name.
• Keyboard focus is not trapped inside dialogs. The demo-request, quote-request, and similar pop-up dialogs close with Escape and are properly labeled, but repeatedly pressing Tab can still reach links in the page behind the dialog rather than looping back to the start of the dialog.
• Product screenshots and the demo video. Screenshot alt text is written by whoever uploads the image in the admin panel, so its quality varies by product; and the demo video is not yet captioned (as of this writing, the video itself has not been recorded).
• The checkout address-lookup field. Typing an address at checkout shows suggestions from OpenStreetMap in a custom list. The list is fully usable visually and by click, but it does not yet use the standard combobox/listbox roles that tell a screen reader "these are suggestions for the field above."
• A few hover-only link and button colors. The color some links and outline buttons switch to specifically on hover measures just under 4.5:1 (about 4.3:1) against our darkest background. The resting (non-hover) color is unaffected and passes.
• The staff admin console (the internal dashboard our own team uses to manage products, tickets, and orders) has had the same obvious fixes applied - labeled fields, hidden decorative icons - but has not had the same depth of audit as the public site, since it is not customer-facing.

We do not use auto-playing audio, and we have no known keyboard traps that prevent leaving a component entirely (only the dialog-focus gap described above).

5. Third-party content

Address suggestions at checkout come from OpenStreetMap, and a confirmed order's pin is shown in an embedded Google Maps frame. We do not control the accessibility of either third-party service.

6. How we tested

This assessment combined a manual code review of every interactive component (keyboard reachability, focus visibility, label and error association), measured color-contrast ratios computed against the actual background colors used in production (not estimated), a check of heading order on every public page, and a review of the motion/animation system for content that could be left hidden. It was not a full assistive-technology test pass (e.g. a structured run through with a screen reader on every flow) - that is on our list, not yet done.

7. Reporting a barrier

If you hit something on this site that doesn't work with the way you browse - a screen reader, keyboard only, voice control, magnification, or anything else - please tell us. Email [email protected] with the page URL and what happened; a note on what device, browser, or assistive technology you were using helps us reproduce it faster.

Our commitment: we will acknowledge your report within 3 business days, and follow up with either a fix or a plan and timeline within 30 days. We are a small team - this is the honest pace we can commit to, not a marketing number.

8. This statement

This statement was prepared and last assessed on September 9, 2026, against the codebase as it stood that day. We will revisit it whenever we make a meaningful change to the site's pages, components, or design system, and at least once every 12 months regardless.