Accessibility statement

Our commitment

We measure this website and the auria app against the Web Content Accessibility Guidelines 2.2, conformance level AA. That is the benchmark referenced by the German Accessibility Strengthening Act and the European standard EN 301 549.

This statement is given voluntarily. It describes the actual state, not the desired one, including where we do not yet meet the requirements.

Current state

This website is largely conformant with WCAG 2.2 level AA. The following is in place:

• A “Skip to content” link as the first element on every page. It becomes visible as soon as you press Tab and skips past the navigation and language switcher
• Full keyboard operation with a visible focus ring on every interactive element. The ring is two-tone and therefore also visible against the light violet gradient
• Questions and answers as a native disclosure element that also works without JavaScript
• Alternative text for meaningful images; purely decorative graphics are hidden from screen readers
• The waitlist form has labelled fields, announces errors through a live region, and marks invalid input. The hidden anti-spam field is removed from the tab order and cannot get in your way
• Reduced-motion preferences respected, including in the consent dialog
• A layout without horizontal scrolling from 320 px viewport width
• A sensible heading structure with no skipped levels and exactly one H1 per page
• Labelled navigation landmarks so screen reader users can jump between them
• The language switcher announces in full which language is active and where the switch leads, not just “DE” and “EN”
• The consent dialog is keyboard operable and can be dismissed without agreeing. It does not block the page behind it: the legal notice and privacy notice stay reachable before you decide
• The language of each page is declared in the document; all content exists in German and English

Measured contrast ratios

We checked the colour values on 13 August 2026. For flat surfaces by calculation using the method set out in WCAG 2.2; for the four sections carrying the violet gradient we measured the pixels as actually rendered instead. The gradient differs in brightness at every point, so a calculation based on an average would be worthless. We tested at five viewport widths from 320 to 1920 pixels, each time at the least favourable point behind every block of text.

On the dark page background:

• Headings: 17.4:1
• Body text: 11.5:1
• Muted text: 9.3:1
• Violet links: 6.4:1
• White text on the violet button: 7.7:1
• White text on the gradient button: 5.3:1, and 4.6:1 in its hover state

On the four gradient sections (hero, “The moment”, “Set up auria”, waitlist), the worst value measured in each case was:

• Body and small text: at least 5.1:1 (requirement 4.5:1)
• Large headings: at least 3.5:1 (requirement 3:1). The tightest value is the light part of the main heading on very narrow screens

These values rely on a dark reading veil over the gradient areas, plus text that previously sat dark on a light gradient being switched to light tones. Without those two changes, body text there measured 3.5 to 3.9:1 and individual dark elements as low as 1.6:1.

Known limitations

We know about these points and are working on them. We name them here rather than leaving them out:

• No test with assistive technology. The site has not yet been worked through with VoiceOver, NVDA, or JAWS. What is stated above rests on the implementation in code, a keyboard check, and calculated contrast values, not on a test with real assistive tools.
• No test by disabled users. A test with people who rely on assistive technology daily has not taken place. It is the most meaningful check there is, and it is missing.
• The auria app has not been assessed. This statement describes the website. For the app in its test phase there is no reliable assessment yet. We know that we support Dynamic Type and honour the reduced-motion system setting; that is not the same as having tested it.
• The consent dialog comes from a third-party library. We adjusted its colours, focus ring, and motion behaviour, checked keyboard operation, and corrected an incorrect attribute that hid the page content from screen readers. For its remaining screen-reader behaviour we currently rely on the vendor’s own statements.

How this statement was prepared

This statement was prepared on 13 August 2026. It is based on a self-assessment: a review of the code, keyboard operation, a structural check in the browser, and a measurement of the rendered pixels for every piece of text on the gradient areas, at five viewport widths.

What surfaced was fixed:

• The skip link was missing entirely
• The focus ring was a single violet tone and, at 1.8:1 against the violet gradient, effectively invisible
• Body text on the gradient areas measured 3.5 to 3.9:1, and the gradient button 3.0:1
• Once the gradient areas were darkened, the situation reversed for dark text: the colour accent in the main heading and the small section labels dropped to between 1.6 and 2.7:1 and were switched to light tones
• An attribute in the consent dialog hid the page content from screen readers while the dialog was open
• The language switcher announced only “DE” and “EN”, without context
• The footer links had small targets on phones and were enlarged to a minimum height of 44 pixels

No assessment by an independent body has taken place.

Reporting a barrier

If you notice something that cannot be operated or read, write to us at hello@uxflows.de. Helpful but not required: which page, which device, which assistive technology.

We confirm receipt within five working days and reply substantively within one month, either with a fix or with an honest assessment of when one is coming. You can also reach us on the telephone number in our legal notice.

This voluntary statement does not promise a particular conciliation route. Any statutory complaint or enforcement routes that apply in the specific case remain unaffected. Please feel free to contact us first so that we can reproduce and fix a barrier quickly.