Accessibility

We want everyone to be able to use our content and services.
That is why we follow the Web Content Accessibility Guidelines (WCAG) 2.2, conformance level AA
and the European Accessibility Act (EAA).

Scope

This statement applies to the website vlip.me including its subpages.
Last updated: .

Compliance status

Parts of the website are already accessible. We are continuously working towards full WCAG 2.2 AA conformance.
At present, the following criteria are largely met:

  • Structured headings and a clear section layout
  • Meaningful keyboard navigation including a “skip to content” link
  • Responsive design, scalable font sizes and flexible layouts

Known issues & planned improvements

  • Navigation (duplicate links): In some viewports, navigation items appear twice.
    We are consolidating the navigation output and hiding redundant elements from screen readers.
  • Forms: All input fields will get visible <label for> elements,
    clear error messages (with ARIA relationships) and suitable type/autocomplete attributes.
  • Contrast & focus: We are checking button and link contrast on image backgrounds and strengthening
    visible focus outlines (:focus-visible) in line with WCAG 2.2.
  • Media: Subtitles/transcripts will be provided for embedded videos;
    decorative images get alt="", informative images precise alternative text.

Feedback & contact

Have you come across a barrier? Please write to us – we will respond as quickly as possible:

Assessment method

Accessibility is assessed regularly through manual testing (keyboard, screen reader)
and automated checks (WCAG checks). The results feed into our
development roadmap and are implemented step by step.

Enforcement procedure

If you do not receive a satisfactory response to your report,
you can contact the competent body under the European Accessibility Act.
On request, we will gladly tell you the responsible contact in Austria.

Roadmap (excerpt)

  1. Consolidate navigation (remove/hide redundant links)
  2. Add form labels, error messages & ARIA relationships
  3. Store a contrast and focus style guide in CSS
  4. Review alt texts; provide subtitles/transcripts
  5. Ongoing regression tests (WCAG 2.2 AA) before releases