Checked 8/31/2026 · https://www.chefkoch.de/
2 critical barriern · plus 1 to check.
How is the score formed? (100 starting points)
| No valid lang attribute on the <html> element | -18 |
| {n} CSS rule{nPlural} with possibly too low text contrast | -18 |
| Heading level skipped | -7 |
| {n} <h1> headings | -2 |
| Result | 55 / 100 |
Perceivable
{n} CSS rule{nPlural} with possibly too low text contrast
Required: 4.5:1 (normal) or 3:1 (large text). With an “assumed page background” the actual background could not be determined reliably — check in the browser if in doubt. Found among others: {examples}
.w-user-menu__context-menu-badge[data-v-aeb5c564]
This is what you should do: Darken the text colour or lighten the background until the relevant minimum value is reached. Never use colour as the only distinguishing feature.
Operable
Heading level skipped
Sequence: {seq}. Levels should not be skipped (h2 → h4).
h1–h6
This is what you should do: Assign the heading levels without gaps.
{n} <h1> headings
Several h1s make navigation via the heading list harder.
h1
This is what you should do: Reduce to one h1, lower the rest to h2.
Understandable
No valid lang attribute on the <html> element
Screen readers cannot determine the pronunciation.
<html>
This is what you should do: Specify the language, e.g. <html lang="en">.
Already handled correctly
- Textalternativen: keine automatisch erkennbaren Probleme
- A <main> landmark exists
Next steps
- No valid lang attribute on the <html> element. Specify the language, e.g. <html lang="en">.
- {n} CSS rule{nPlural} with possibly too low text contrast. Darken the text colour or lighten the background until the relevant minimum value is reached. Never use colour as the only distinguishing feature.
- Heading level skipped. Assign the heading levels without gaps.
- {n} <h1> headings. Reduce to one h1, lower the rest to h2.
Weekly re-scan, JS-rendered, email on new barriers — coming soon.
Create an accessibility statement →
Method & limits
On 8/31/2026 the HTML that www.chefkoch.de delivers on a first visit without login was checked, plus up to four linked CSS files from the same domain. Checked: colour contrast (from CSS), text alternatives, form labelling, names of controls, heading structure, page title and page language, zoom lock, duplicate ids, positive tabindex values, landmarks.
Not checked: anything that arises via JavaScript, keyboard operability, visible focus, focus order, screen-reader announcement, content behind login, subpages. The automated test finds roughly 20–35% of WCAG breaches — the rest needs a manual check. A snapshot, not a legal decision.