Scan any Craft CMS site against 16 WCAG 2.1 AA rules in seconds — nothing to install, no signup. Built for EU compliance.
16 automated rules covering images, links, forms, headings, language, viewport, contrast, ARIA misuse, and more — mapped to real WCAG success criteria.
Paste your URL, get a letter grade with every issue listed by severity. No account, no email, no waiting for an audit report.
The rule set targets what EU enforcement and enterprise procurement actually look at: WCAG 2.1 AA basics you can document today.
When your scan flags a failing rule, here is where to fix it:
| Issue | Where to fix in Craft CMS |
|---|---|
| Missing alt text on assets | Craft assets have an Alt Text field only if you define one — add an "altText" field to the asset volume and require it, then output {{ asset.altText }} in templates. |
| Low contrast text | Fix in your CSS/Tailwind config. If you use utility classes, audit the colour tokens against WCAG ratios once instead of case by case. |
| Missing heading structure | Headings come straight from your Twig templates. Enforce one H1 per template and use semantic H2/H3 in shared includes (cards, sections). |
| Missing form labels | Whatever form plugin or hand-written form you use, every input needs a visible |
| Generic link text ("read more", "click here") | In card/list templates, extend the link with visually hidden context ({{ entry.title }}) or an aria-label so screen-reader users hear what the link opens. |
| Missing page language | Set lang on the tag from the site locale — for multi-site setups output the current site's language dynamically. |
| Focus styles removed by CSS resets | CSS resets commonly strip outline. Restore :focus-visible styles globally in your stylesheet. |
Craft CMS ships with useful foundations — these approaches take you further:
Both free; run against rendered templates to catch contrast, labels and ARIA mistakes.
Because markup is fully developer-controlled, catching issues at PR time is cheaper than scanning later.
Make the alt-text field required in the asset volume settings so editors cannot publish images without it.
Accessibility is not a one-time fix — sites change through content edits, theme updates and new pages. Keep compliance sustainable:
Dig deeper into the compliance work that comes after the scan:
Automated scanning catches roughly a third of accessibility issues — but it catches the ones that are cheapest to fix first. For the complete picture, our e-book covers the full checklist plus a 14-day fix plan.