Despite our efforts, we are currently unable to offer certain content in a fully accessible form. This applies in particular to:
- Older PDF documents, Office files, and videos published before the deadlines set by Directive (EU) 2016/2102. These documents and media may lack proper structure, alternative texts, or accessibility features such as subtitles or audio descriptions.
- Complex or legacy content that cannot be quickly adapted due to technical or resource-related limitations.
On this website, form fields are not always fully accessible. In some cases, input fields (<input> – excluding the types image, submit, reset, button, or hidden), selection fields (<select>), or text areas (<textarea>) may not be properly associated with a corresponding label.
A correct association is given when:
- a visible <label> element exists with a for attribute matching the id of the form control,
- the <label> element directly wraps the form control and no other inputs,
- a non-empty title attribute is used, or
- a non-empty aria-labelledby attribute is present.
There may also be isolated cases where the contrast between text and background does not fully meet the requirements of the Web Content Accessibility Guidelines (WCAG). Specifically, text may have a contrast ratio below 4.5:1 (or below 3:1 for large or bold text). WCAG requires that both foreground and background colors are defined or inherited to provide sufficient contrast. When text appears over background images, a background color must be defined (typically via CSS) to ensure readability if the image is disabled or fails to load.
Please note that some contrast issues cannot be detected by automated tools (such as WAVE), particularly in cases where CSS transparency, gradients, or filters are used. Higher contrast levels as required by WCAG Level AAA (at least 7:1 for normal text and 4.5:1 for large text) are not consistently achieved.
We are continuously working to identify and reduce these accessibility barriers.
