Accessibility Statement

Conformance status

WCAG 2.2 Level AA, partially conformant. “Partially conformant” is the W3C’s term for “meets the standard except for the parts named below”, and it is the honest word here: the gaps in the last section are real and we would rather you read them from us than discover them yourself.

This is a self-evaluation, carried out on 6 November 2026. No external auditor has reviewed Source, and there is no VPAT. If your procurement process needs one, write to us — we would rather answer specific questions about the surfaces you depend on than publish a document that averages them.

What we measured

Before 6 November 2026 nothing had been audited, which is its own answer and not a good one. What the first pass consisted of:

• axe-core 4.10 run against every publicly reachable route: the landing page, pricing, the legal documents including this one, sign in, sign up, password reset and the 404 page. No critical or serious violations remain on them.
• A contrast audit of every colour token in both themes, computed from the stylesheet rather than eyeballed, and held in place by a test so a future palette change cannot quietly drop below AA. It found three pairings under the standard, two of which are fixed: secondary text set on a muted background, and the focus ring itself, which was below the 3:1 minimum that makes it visible at all.
• A keyboard-only pass over the kanban board, where moving a ticket between columns is the product's most load-bearing gesture. It can now be done entirely from the keyboard, and the focus ring was raised to meet the 3:1 non-text contrast minimum it was previously under.
• Charts are drawn as SVG that carries no text, so each one now also publishes the numbers it plots as a table for screen readers.

What is not done

These are open. They are listed because a reviewer would find them anyway, and because a statement that only lists successes tells you nothing about the product.

• No screen-reader pass. Nothing in Source has been driven end to end with NVDA, JAWS or VoiceOver, so there will be places where the markup is technically correct and the experience is still poor.
• The signed-in application has not had an automated accessibility run. axe needs an authenticated browser session to reach those routes and that is not wired into CI yet, so the board, the ticket dialog, the editor and the settings screens have been audited by review and by hand rather than by tooling.
• The whiteboard (Excalidraw) and the page graph (React Flow) are drawing surfaces rendered to a canvas and an SVG. Neither exposes its contents to assistive technology, and a drawing is not something we can usefully describe automatically. The underlying pages are fully readable without the graph.
• The rich-text editor (TipTap) has not been tested with assistive technology. Its toolbar is reachable by keyboard; whether the document model is announced sensibly while editing is unverified.
• Two colour pairings are still under AA and both are deliberate rather than unnoticed. The one coloured word on the marketing page — the four-hue gradient on “agents” — reaches 3.0–3.8:1 on white, which is the standard for the large heading it was designed for and not for the two places it also appears in 13px body copy. And in dark mode, destructive text on a hovered destructive button is 3.83:1. Both need a visible colour change to fix; neither has been made yet.
• There is no VPAT. This statement is what we have instead, and it is deliberately more specific than one.

Telling us about a barrier

If something in Source blocks you, email neuvikon@gmail.com. It reaches a person rather than a help desk, the same inbox as everything else on these pages. Tell us the screen and what you were trying to do; if you use assistive technology, naming it and its version saves a round trip.

We do not have a committed response window for accessibility reports and will not invent one. In practice the inbox is read daily by the person who writes the code.

Scope

This statement covers the Source web application at https://www.neuvikon.space and the marketing and legal pages on the same site. It does not cover the neuvikon command-line tool, which is a terminal program and inherits whatever your terminal provides, nor the third-party services named in our sub-processor list, each of which publishes its own statement.