A
Level A
The foundational entry level. This covers core requirements such as usable structure, text alternatives, and keyboard access.
Accessibility
This page explains how the 2026 website is being aligned with the WCAG 2.2 requirements.
Current approach
Goal: understandable, robust, and clearly framed
We are developing the 2026 website with a focus on WCAG 2.2 Level AA. As of today, this serves as our working baseline and not yet as a blanket conformance claim for the entire website.
This follows the official W3C guidance for WCAG 2.2 conformance logos: logos help communicate a level, but they do not replace a reliable review and must not suggest W3C endorsement. To the best of our knowledge, we address the relevant requirements, while individual technical measures such as spam protection or external embeds still need regular review.
AA
Level AA
AA is the target level for the 2026 website. This includes sufficient contrast, clear focus handling, understandable form states, and consistent interaction patterns.
AAA
Level AAA
AAA represents an even more ambitious optimisation level. Not every page can realistically meet AAA completely, so we use it more as an additional quality compass.
What we take from the W3C guidance
- Conformance statements need a clearly defined scope, such as a specific website or a clearly delimited section.
- A WCAG logo should always be paired with understandable text and link to an explanation.
- W3C does not certify an individual website review. We explicitly avoid creating that impression.
What is already implemented on the 2026 website
- As of today, meaningful heading structure and landmarks for screen readers and keyboard navigation are implemented in the main parts of the site.
- As of today, we maintain German and English content including accessibility texts such as alt, aria-label, and embedded titles.
- As of today, embedded external content such as YouTube, Google Maps, and Sessionize is loaded in a privacy-friendly way only after consent or an active click and is not shown automatically.
- To the best of our knowledge, navigation, forms, and status messages use semantic markup and are designed for understandable interaction; technical components still remain under ongoing review.
Official reference
You can find the details about the official WCAG 2.2 logos and their correct use directly from W3C.
