Accessibility

Accessibility statement

What we aim for

We orient ourselves towards the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. This statement describes the position as of 15 August 2026 and is based on a self-assessment — there has been no review by an independent body so far. Where we do not reliably meet a requirement, that is stated below.

What is implemented

• Keyboard operation: every control can be reached with the tab key and triggered with Enter or Space. The mobile menu is a real button and reports its state via aria-expanded. There are no keyboard traps and no reordering via positive tabindex values.
• Visible focus: the active element is highlighted with a clear outline.
• Skip link: at the very start of every page there is a link that skips the navigation and goes straight to the content.
• Contrast: text consistently reaches at least the ratio required for level AA; in body text the values are 5.3:1 and above.
• Magnification: zoom is not blocked. Pages work down to 375 pixels wide without horizontal scrolling.
• Structure: every page has exactly one main heading, plus regions for header, navigation, content and footer.
• Motion: anyone who has set reduced motion in their operating system gets animations and smooth scrolling switched off. There are no auto-playing media and no flashing content.
• Forms: all calculator input fields have an associated label; fields with no effect on the result have been removed or hidden.
• Language: every page is marked up as German or English in its source.

Known limitations

Honesty is more useful here than a declaration of conformity:

• Screenshots contain text within the image. The app views show headings and figures as part of the graphic. Their alternative text so far describes only in general terms what is shown and does not reproduce the text it contains. The content shown does, however, appear in the surrounding text of the page.
• No independent review. There is no report from a testing body and no testing with people who rely on assistive technology. All statements above rest on our own measurements in the browser.
• Screen readers only partly tested. The structure has been checked; a full run with common screen readers is still outstanding.
• The app is not covered by this statement. It refers exclusively to ryvion.de.

Feedback and contact

If you encounter a barrier — an element that cannot be reached with the keyboard, insufficient contrast, an unclear label — please report it to support@ryvion.de. A short description with the page reference is enough.

We record every report and improve accordingly. As a one-person project we cannot promise a fixed deadline, but we will reply and say when we plan to address it.

Last updated: 15.08.2026