Accessibility
We build websites that everyone should be able to use. That means our own site has to say where it stands. This statement covers what we test, what works, and what does not yet.
1. Scope
This statement covers codeaeffchen.com and its German counterpart codeaeffchen.de, including the articles, the glossary entries and the browser tools at codeaeffchen.com/tools/.
It is voluntary. Codeäffchen is not a public sector body under the German accessibility regulation for information technology, and we do not run an online shop. We publish it anyway, because accessibility is something we sell.
2. Conformance status
This website is partially conformant with the Web Content Accessibility Guidelines version 2.1, level AA. The limitations listed in section 4 are known to us.
“Partially” is deliberate. Some requirements can be checked automatically, the rest cannot. We have not commissioned an external audit and have not run tests with screen reader users. What we claim here is what we measured.
3. How we test
Testing does not happen once a year, it happens on every change. Before every release and on every proposed code change, the following runs automatically:
- axe-core across 47 pages, one representative per page type in both languages, checked against the WCAG 2.0 A and AA and WCAG 2.1 A and AA rule sets plus axe's best-practice rules (such as heading order and unique page regions). Every page is loaded twice, at 1280 and at 390 pixels wide, because some violations only appear in the mobile layout.
- The contact form in its open dialog, because a dialog has its own requirements for focus and labelling.
- Keyboard operation: the skip link to the main content, a visible focus indicator, and the ARIA attributes of the mobile menu.
- Contrast ratios are recalculated whenever we change colours. Most recently that raised the comment colour in code blocks from 3.05 to 5.04.
A proposed change that introduces a violation is rejected before it goes live.
4. What does not work yet
Without JavaScript
All text, articles, glossary entries and navigation are fully readable without JavaScript. Nothing is revealed by script. The contact form submits without JavaScript too. It is then sent as an ordinary form, with one extra step: a page summarising what will be sent, which you confirm with a single click. That keeps out automated messages that submit a form only once. Until 22 September 2026 the button did nothing here. That was a defect and it is fixed. Two limitations remain:
- Email addresses are readable but not clickable. We assemble them by script to keep spam bots out. Without JavaScript you see the spelled-out form using “(at)” and “(punkt)”. Typing it works, clicking it does not open a mail client.
- The tools do not calculate. The generators at /tools/ run in your browser. The explanation and the instructions stay readable, the output does not appear.
If you would rather call or write, the phone number and postal address are in the imprint.
Automated testing has limits
A testing tool finds missing labels and weak contrast. Whether an alternative text actually describes the image, whether a heading order makes sense, or whether wording stays understandable is beyond it. We pay attention to that, we cannot guarantee it.
Page types not covered
Automated testing takes one representative per page type, not every single page. New page types are added to the list. An individual page can still slip through.
Third-party content
Client testimonials come from Google reviews and are quoted verbatim. We have no influence on their language or readability.
5. Reporting a barrier
If you run into something you cannot use, tell us. It helps to know the address of the page, what you were trying to do, and what you are using: browser, operating system and any assistive technology.
We reply as soon as we can. Our service hours are Monday to Friday, 8 am to 6 pm Central European Time. We do not promise a fixed deadline, because we could not always keep it. If we fix a barrier, we will let you know.
6. If our answer does not satisfy you
For products and services covered by the German Accessibility Strengthening Act (Barrierefreiheitsstärkungsgesetz), the market surveillance authority of the federal states for the accessibility of products and services is responsible. It accepts reports from consumers.
Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen, Magdeburg, Germany, www.marktueberwachung.de.
7. Status of this statement
Prepared on 21 September 2026 based on a self-assessment. It will be revised whenever our testing or our findings change.