Accessibility Statement

Our goal is for the site to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. Accessibility is part of how we design and build, not a check at the end. In practice that means:

• every page works with a keyboard alone, with a visible focus indicator
• text and controls meet AA colour contrast against the dark background
• headings, landmarks and labels give screen readers a clear structure
• form errors are announced and explained next to the field they belong to
• all important content is real text in the page, never only inside an animation or a 3D scene

Parts of the site use animation, smooth scrolling and 3D graphics. All of it is decorative, and you can switch it off:

• Turn on the reduced motion setting on your device (Windows: Settings › Accessibility › Visual effects › Animation effects off. macOS and iOS: Settings › Accessibility › Motion › Reduce Motion. Android: Settings › Accessibility › Remove animations).
• With that setting on, the site stops smooth scrolling, camera moves and physics, and shows still images instead of 3D scenes.
• On older or low-power devices, and when your browser saves data, the site automatically shows a lighter version without 3D.

We test with automated tools and a keyboard. Testing with screen readers is still to come, and we already know of these limitations:

• The playful drag-and-throw areas (for example the service chips on the contact page) need a mouse or touch screen. Everything they do is also available another way, such as the form's own service options.
• Legal pages are currently only available in English.
• We haven't yet had the site audited by people who use assistive technology every day. That audit is planned, and we'll list what it finds here.

If something on the site is hard or impossible for you to use, please tell us. Email [email protected] or call +49 151 72234980, and mention the page and what happened. We'll reply within five working days and, where we can, send you the information in a form that works for you.

This statement is based on a self-assessment during development: automated checks with Lighthouse (which uses axe) on every page, keyboard testing, and tests at screen widths from 375 to 1920 pixels with reduced motion on and off.