Check · real browser · WCAG 2.1/2.2 · arts. 12, 18, 32, 37 of the act
Check your website
Enter an address. We open the page in a real browser — on desktop, on a phone and at 320 px — take screenshots, measure what the code alone cannot show, and check the code. A result in 20–60 seconds, no sign‑up. The report link is valid for 90 days.
What we check
In the browser
Actual text contrast after backgrounds are composited (up to 12 samples per page), focusable‑but‑hidden elements, suppressed focus outline (a scan of the stylesheets), positive tabindex, endless animations and missing prefers-reduced-motion, autoplay, touch targets under 24×24 px, the smallest font size, horizontal scrolling on a phone (390 px) and at 320 px, video without captions, frames without a title, tables without headers, duplicate ids, language changes.
In the code
Document language, title, viewport and zoom blocking, meta refresh, image alternatives (and alts that are file names), link and button names, "here/more" links, field labels and placeholder‑as‑label, one h1 and heading order, empty headings, a main landmark, a skip link, valid ARIA roles, broken ARIA references, marquee/blink, legacy plugins, a page without HTTPS.
From the act
Whether the page is a shop (e‑commerce signals → art. 18), whether there is accessibility information (art. 32(2)(1)), a link to the terms, a contact channel for complaints (art. 37(1)), structured data and its validity (informational).
Around the page
Technologies (CMS, shop platform, frameworks), load time and first paint, number of requests, desktop/phone screenshots, up to 20 other pages found by following links — marked as needing their own check.
Every finding has a weight (critical, serious, moderate, minor, information), a WCAG criterion, an EN 301 549 clause and an article of the act, a location in the code (e.g. form#checkout > button.pay) and — in the paid version — fix instructions. The 0–100 score orders urgency; the status under the act (no significant gaps / gaps / serious non‑compliance) says whether a consumer complaint would have grounds.
What an automated tool cannot check
Around 30–50 % of WCAG criteria need a person: whether an image alternative makes sense, whether the heading order matches the content, whether an error message helps, whether one can buy with a screen reader from start to finish. Our report is honest about what it did not check — the "not checked" section is not counted as "met". The whole‑site check covers every page of the purchase process and gives fix instructions; a manual audit with a screen‑reader user — on request. The whole protocol — choosing the sample, testing with a keyboard and a screen reader, and what survives in the documentation — is on the Testing page.
Privacy of the check
We only check public pages; addresses on private networks are refused. We store the address, result, screenshots and findings for 90 days so the report link works. Aggregate, non‑personal information about the website (domain, score, platform, whether it is a shop) goes into the shared website database of the Castomo ecosystem — without findings, without screenshots, without personal data. Your e‑mail, if given, is used to send the report and — only with consent — for contact. Privacy policy. Limits: 3 checks a minute and 20 a day per IP address; the same address within 10 minutes returns the same report.