Checked 8/31/2026 · https://t3n.de/
1 critical barrier · plus 3 to check.
How is the score formed? (100 starting points)
| {n} CSS rule{nPlural} with possibly too low text contrast | -18 |
| No <h1> heading in the delivered HTML | -7 |
| Heading level skipped | -7 |
| {n} duplicate id attributes | -7 |
| Result | 61 / 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}
.ebmex, .deetqq
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
No <h1> heading in the delivered HTML
Each page should begin with exactly one h1. On pages built via JavaScript the h1 may only appear in the browser — then check in the rendered DOM.
body
This is what you should do: Insert a meaningful <h1> as the first heading (ideally already server-side).
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.
Robust
{n} duplicate id attributes
e.g. {examples}. Breaks label-for and aria links.
[id]
This is what you should do: Assign unique ids.
Already handled correctly
- Textalternativen: keine automatisch erkennbaren Probleme
Next steps
- {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.
- No <h1> heading in the delivered HTML. Insert a meaningful <h1> as the first heading (ideally already server-side).
- Heading level skipped. Assign the heading levels without gaps.
- {n} duplicate id attributes. Assign unique ids.
Weekly re-scan, JS-rendered, email on new barriers — coming soon.
Create an accessibility statement →
Method & limits
On 8/31/2026 the HTML that t3n.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.