アクセシビリティ

We want CapyDB to be usable by everyone who has to operate a database, including people using screen readers, keyboard-only navigation, magnification, or reduced-motion settings. This statement is written honestly: it names what does not work yet rather than claiming a conformance level we have not earned.

The marketing site, the documentation site, and the dashboard are built against EN 301 549 and the Web Content Accessibility Guidelines 2.1 at Level AA, which is the standard the European Accessibility Act points to.

Partially conformant. Most of the site and dashboard meet WCAG 2.1 AA; the exceptions below are known and tracked. "Partially conformant" means some content does not fully conform - it does not mean the standard was ignored.

• -Full keyboard operation of the marketing site and the primary dashboard flows, with a visible focus ring on every interactive element
• -Semantic landmarks and headings, so a screen reader can skip between regions rather than reading the page linearly
• -Colour contrast checked against the AA thresholds in both the dark marketing surface and both dashboard themes
• -prefers-reduced-motion honoured: the animated grid, the live indicators, and the page transitions all stop
• -Text resizes to 200% without loss of content or function, and layouts reflow rather than requiring horizontal scrolling
• -Form fields carry programmatic labels, and errors are announced rather than shown only in colour
• -The interface is available in eight languages, with the document language declared correctly for assistive technology

• -The SQL editor in Studio is a code-editing component; its keyboard model is workable but its screen-reader announcements are incomplete
• -Some observability charts convey trend information visually; the underlying numbers are available as text nearby, but not yet as an equivalent tabular alternative in every view
• -A small number of dense operational tables in the dashboard require horizontal scrolling below roughly 400 CSS pixels
• -The generated API reference on the documentation site inherits the heading structure of its generator, which is not always ideal for navigation
• -Third-party components in the sign-in flow are configured for accessibility but are not fully under our control

The company operating CapyDB is a microenterprise as the European Accessibility Act defines one, which places its services outside the Act's mandatory service requirements. We publish this statement and work to the standard anyway, because the reason to do it does not depend on the exemption.

Where a fix is genuinely disproportionate for a team of this size - typically a deep rewrite of a third-party editing component - we say so here rather than leaving the gap unexplained, and we provide an alternative route to the same task through the CLI or the API.

Every operation available in the dashboard is also available through the CLI, the HTTP API, the SDK, and the MCP server. If a visual surface blocks you, a text one will not: creating projects, running SQL, taking backups, restoring, and managing keys are all scriptable.

If you hit a barrier, tell us what you were trying to do, what stopped you, and what you were using. Email is the accessible channel and reaches a person directly; you do not need to use the web form, and you will not be asked to file a ticket in a tracker.

We aim to acknowledge accessibility reports within five working days and to say what we are going to do about it, including when the answer is that we cannot fix it soon.

If our response is unsatisfactory, you may escalate to the national authority responsible for enforcing accessibility requirements in your country. In Greece, market surveillance for the European Accessibility Act sits with the authorities designated under the Greek transposition of Directive (EU) 2019/882.

Prepared by self-evaluation: automated checks across the site and dashboard, plus manual keyboard and screen-reader passes on the primary flows. It is reviewed when a significant interface change ships, and at least annually.