EN

Not signed in

Sign in to save comparisons and suggest corrections.

Accessibility

Last reviewed 2026-08-04

This statement is made under the Barrierefreiheitsstärkungsgesetz (BFSG), which has applied since 28 June 2025. It is written honestly: the known problems are listed rather than omitted.

What we aim for

WCAG 2.2 level AA. Several decisions follow from it directly: every control you can tap is at least 44 by 44 pixels, focus is always visible, the navigation drawer traps focus and closes on Escape, and no meaning is carried by colour alone — every status that has a colour also has a word.

What that means in practice

The site works without JavaScript for reading, searching, changing language and opening the navigation. Text resizes to 200% without loss. Every icon is a drawn glyph with a text label beside it or an accessible name on it — never an emoji, which screen readers announce unpredictably.

Answers are written in plain language on purpose. Where an entry is served in a language other than the one you chose, it says so rather than letting you assume it was written for you.

What is not right yet

This section is kept truthful rather than short. Known limitations are listed here as they are found, with what we intend to do. If this list is empty it is because none are currently known — not because none exist.

Telling us

If something is unusable, write to the address below and say what you were trying to do. You will get an answer. If you are not satisfied with it, you can contact the enforcement body for the state where the provider is established.

Every entry cites its sources and shows when it was last checked. Where there is no verified answer, this site says so rather than guessing.