Accessibility statement
City Handbook is meant to work for everyone who needs it, including people who use a screen reader, a keyboard instead of a mouse, magnification or a machine translator. This statement says which standard we aim for, how we check it, and what we know is still wrong.
The standard we aim for
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, across the whole site, in all three interface languages (English, German and Turkish) and in both the light and the dark theme.
How far we are
The site is partially conformant with WCAG 2.2 level AA. Most of it is built and tested against that standard, but the limitations listed below are real, and nobody outside the project has audited it. We do not claim full conformance.
What we check, and how
Every change to the site has to pass these checks before it is published:
- An automated accessibility scan (axe) of every significant page, including the editor, the account pages and the admin area, in the light and the dark theme. No violation is allowed, apart from one documented exception (the map attribution line, listed below).
- Keyboard use: a link that skips to the main content, dialogs that keep focus inside, close with Escape and return focus to where you were, and map pins that can be reached and opened from the keyboard.
- Reflow: key pages work at 320 pixels wide (a 1280-pixel screen at 400% zoom) without scrolling sideways, and text stays readable with increased letter, word and line spacing.
- Colour contrast: every pair of the design's colour tokens is checked against the AA requirement, in both themes.
- Motion: a “Reduce motion” setting, in the footer and in your account settings, which follows your device's setting unless you choose otherwise.
- Touch targets: on key pages, controls are measured on a phone-sized screen against 44 by 44 pixels. The ones that are still smaller are listed and tracked (see below).
- Language: a page written in another language than the interface is marked with its language, so a screen reader pronounces it correctly.
What we have not checked
- Nobody has tested the site with a screen reader yet (NVDA, JAWS, VoiceOver or TalkBack). This is the largest gap.
- There has been no independent accessibility audit, and no testing with disabled users.
- The automated checks run in one browser engine (Chromium). Firefox and Safari are not tested automatically.
- Automated tools find only part of the barriers on a page. A clean scan is evidence, not proof.
Known limitations
- Maps are pictures. Every place on a city map is also listed as text with its address, and the pins can be reached from the keyboard, but how places lie in relation to each other is only shown visually.
- The small attribution line on maps comes from the map library and does not meet the contrast requirement. The map tiles come from OpenStreetMap and are not under our control.
- Some controls are smaller than 44 by 44 pixels on a phone, for example the footer links, the language buttons and some form fields.
- Pages are written by contributors. The editor points out accessibility problems while they write, such as skipped headings, unclear link text or tables without headers, but it does not stop a page from being published, and it cannot judge whether the text is clear.
- A passage in another language inside a page cannot be marked yet, so a screen reader may pronounce it in the page's language.
- Pages embedded on other websites follow the device's motion setting and the colour theme the embedding site chose, not the settings you chose here.
Tell us about a barrier
If something on this site does not work for you, or you need information in another form, please tell us which page it was and what happened. A person reads every message.
- Write to [email protected].
- Write to the contact address in the Impressum.
- For a problem on one particular page, you can also use the “Report” button on a guide, place or event page and choose “Other”. You do not need an account.
About this statement
We publish this statement voluntarily. We have not assessed whether a German or EU accessibility law requires it of this site.