Accessibility statement

Goal and status

We want this website to be usable by everyone — with a keyboard, with a screen reader, at high magnification, with limited colour vision. The standard we work towards is WCAG 2.2 Level AA.

This is not a declaration of conformity. It is a self-assessment: there has been no external audit and no full run with a screen reader, so we do not certify that the site meets Level AA. What we did measure is listed below with numbers, computed on every build. What we did not test is under “Known limitations” — and we would rather write that down than claim a status nobody has checked.

What is implemented

Operating without a mouse

• Every function is reachable by keyboard; there are no mouse traps.
• Keyboard focus is always visible — a two-pixel ring in the accent colour with an offset, not the browser default that often disappears.
• A “skip to content” link sits at the very top. On the long legal pages it saves a dozen tab stops.
• The mobile menu closes with Esc, and focus returns to the menu button. While it is open, the rest of the page is hidden from keyboard and screen reader.

Structure and screen readers

• Each page has exactly one main heading, and heading levels are not skipped.
• The document declares its language as en. The one German passage — the provider details on the Impressum — carries its own lang="de", so a speech synthesiser switches voice for it.
• Every control has a label, even where it shows only an icon.
• The reading order in the source matches the visible order — with two deliberate exceptions, both of which put the screen-reader order ahead of the visual one. On the legal pages the table of contents comes first in the source and sits on the right of the screen, so you hear the jump list before the text instead of after it. On the home page, the sentence about weight history comes before its screenshot in the source and sits to the right of it on wide screens, so you hear the point before the picture. Nothing else is reordered.

Seeing and zooming

• Body text is 17 pixels, not 14. Line length and line height are set for readability.
• Zooming is not disabled. Every page was measured at 320, 360 and 640 CSS pixels — the widths behind WCAG 1.4.10 (Reflow) and 200 % zoom. None of them requires sideways scrolling.
• The site has a single, light appearance and no toggle — and therefore no second variant that gets less scrutiny.
• Information is never conveyed by colour alone.

Motion and controls

• If “reduce motion” is set in the operating system, movement is reduced to a single soft fade when the page loads — nothing slides, and nothing is tied to scrolling. Without that setting, the home page has exactly two movements: the headline appears word by word once, and one screenshot follows your own scrolling. Nothing blinks, loops or moves on its own.
• Header controls measure at least 44 × 44 pixels, all others at least 24 × 24 — that is success criterion 2.5.8 at Level AA.
• Wide tables scroll within themselves rather than pushing the whole page sideways. The scrolling area is focusable and named — otherwise the hidden columns would be out of reach without a mouse. A gradient at the edge shows that more is there; at 393 pixels wide that can be up to 32 per cent of the table.

Measured contrast ratios

Contrast is not a matter of taste but a number. All 39 colour pairs that can be formed from the colours of this site are computed on every build — if one falls below the threshold, the build fails. The page background is a gradient, so every value below is computed against its darkest point (#f0f8ff), not against white.

Weakest text pair: --accent / page gradient. Weakest graphic: --accent / page gradient — a graphic, for which WCAG 1.4.11 requires 3:1, not 4.5:1.

For comparison: Level AA requires 4.5:1, Level AAA requires 7:1. 27 of the 39 pairs reach AAA.

Known limitations

A statement is only honest if it also says what is missing:

• No external audit. There has been no third-party review and no testing with affected users. Everything here is self-measured.
• No screen reader run end to end. What can be checked mechanically is checked, and re-checked on every build: the document language, exactly one main heading per page, a label on every control, the reading order in the source, and the background being hidden while the menu is open. A full pass with VoiceOver, NVDA, JAWS or TalkBack is still outstanding — we would rather write that here than claim it.
• The legal texts remain difficult. We wrote them as plainly as the subject allows, but a privacy policy is not plain language. There is no easy-read version.
• No sign language videos. Nothing on this site is spoken, so there is no audio to interpret — but the legal texts are long, and a signed summary would help. It does not exist yet.
• This statement covers the website only. It does not cover the iPhone app, where iOS accessibility features apply and which we have not fully audited.

Report a barrier

If you hit something that does not work — tell us. It is the fastest way to get it fixed, and we take it seriously.

Report a barriersupport@cal3d.appUsually answered within two working days. Telling us the page and the assistive technology is enough.

If you need any content from this site in another form — as plain text or read aloud — write to us as well. We will provide it.