Questions, not guesses
Nine manual WCAG checks asked in plain language. Text over a background image, where contrast can’t be measured, becomes a question rather than a quiet pass. Your answers stay through re-scans.
Can everyone read your Craft site? Most sites fail at least one person. Audit them against WCAG 2.2, fix them, keep the evidence.
If you had to squint at this line, you already understand the product.
When a client, a procurement team or a regulator asks whether the site meets WCAG, find out from inside Craft, fix what’s wrong, and have the evidence to show them.
For Craft CMS 5. Try Pro free on any dev domain, or check one page with the free checker.
An animated example: a bakery blog post with seven accessibility problems is scanned, each problem is flagged, and each is then fixed. The list of problems is alongside.
Page report: “Sourdough season is back”
Ready to scan this entry.
Somebody is going to ask.
A client forwards an email asking whether the site meets WCAG. A procurement form wants a VPAT before it’ll go any further. The European Accessibility Act came in, and somebody has finally asked what’s been done about it.
Craft will tell you whether an entry saved. It won’t tell you whether someone on a screen reader or a keyboard can get through the page.
94.8%
of the top million home pages have WCAG failures that can be detected automatically.WebAIM Million, 2025
27%
of people in the EU aged 16 and over report some form of disability. That’s a quarter of your audience.Eurostat
0
days since the European Accessibility Act started applying, on 28 June 2025. Its benchmark is EN 301 549, and the plugin scores against it.Directive (EU) 2019/882
It checks the colours other tools never see.
Every automated checker reads the rendered page, and a rendered page is always at rest. A link that goes unreadable on hover, a focus colour weaker than the resting one, a selection colour nobody can read: none of these turns up in an ordinary automated audit.
Accessibility Audit reads hover, focus and selection colours out of your stylesheet and measures each one against the background the element actually sits on.
Hover over this link, tab to it, or select some of this text. The row for the state you’re in lights up.
See this season’s bake schedule- At restA
- HoverA
- FocusA
- SelectionA
See the page the way your visitors do.
The plugin’s page report has colour-blindness and low-vision filters built in. Try them on this whole site: pick a condition, scroll around, then switch it off from the bar at the bottom.
It lives where the fixes happen.
The SaaS crawlers watch your site from outside and hand you a report. This plugin sits inside the Craft control panel, next to the field an editor needs to change.
Standard and Pro
Know what to fix first
Issues grouped by rule and by page, ordered by how many points each fix adds to the score.
Every rule is tagged with difficulty and who’s likely to fix it (content, design or development), so you can scope the work before you quote for it.
Standard and Pro
Every occurrence, pointed at
Each issue is highlighted in a live preview and in the page source, with the template it came from. Switch between desktop and phone width to see where each one shows up.
The element sidebar shows the same score and a re-scan button on every entry, right where the editing happens.
Pro
The report procurement asks for
A VPAT or ACR filled in from your own scans. Each criterion shows what the scans covered, over how many pages, and what no scanner can establish.
No criterion is ever marked “Supports” for you. You sign off each one, and Claude can draft the remarks from real findings.
Standard and Pro
The statement the law requires
The public accessibility statement required in the EU and UK, built to your jurisdiction’s model, with the compliance claim held to what your evidence supports.
It’s in both editions on purpose. A legal obligation shouldn’t sit behind an upgrade.
Pro
Plain language, measured
Reading ease and grade level against WCAG 3.1.5. The preview marks hard sentences, adverbs and passive voice as you write, and suggests plainer wording.
English sites only.
Standard and Pro
Check the palette before the page
A contrast analyser, a colour-blindness simulator, and a grid showing the contrast of every combination in your palette at once.
It never claims more than it knows.
Automated checks catch about a third of WCAG failures. That’s true of every tool, this one included. So the scanner does its part properly, and hands you the rest as plain questions.
No overlay. Ever.
Nothing is injected for visitors. In 2025 the FTC ordered accessiBe to pay $1 million over claims its widget made sites compliant. The front-end overlay here is for logged-in admins only.
Your data stays yours
Scans, scores and VPAT content live in your own database. AI is optional and uses your own Anthropic API key. No key, no calls, and nothing leaves the install.
Standard finds the issues. Pro proves they’re fixed.
Standard covers one site and up to 100 pages. Pro adds the history and reports you need when someone asks for evidence.
| Feature | Standard | Pro |
|---|---|---|
| WCAG 2.2 scanning: 28 PHP rules plus axe-core at desktop and phone width | Up to 100 pages | Unlimited |
| Hover, focus and selection contrast | ||
| A, AA and AAA scoring, with EN 301 549 | ||
| Dashboard, issues, page reports and element sidebar | ||
| Human-review checks | ||
| Entries, categories, Commerce products and custom elements | ||
| AI alt text and asset audit | ||
| Colour tools | ||
| Accessibility statement | ||
| Scan on save, scheduled sweeps and console commands | ||
| Sites | Primary only | All sites |
| Scan history | 30 days | Unlimited |
| Permanent record of resolved issues | ||
| Server-side browser scanning with headless Chrome | ||
| Readability (WCAG 3.1.5) | ||
| VPAT / ACR report | ||
| Email and Slack alerts | ||
| CI/CD score endpoint | ||
| Overlay for Next, Nuxt, Astro and static front ends |
See prices on the Plugin Store
Try Pro free on any dev domain. Switching editions keeps your scans and settings.
One licence. No meters.
No traffic metering and no per-seat pricing. Standard covers up to 100 pages. Pro has no page limit, so a 40-page brochure site and a 40,000-page catalogue cost the same, scanned as often as you like.
| Tool | What it is | Pricing |
|---|---|---|
| Siteimprove | Enterprise crawler suite | Quote only, reported $12k to $70k a year for accessibility alone |
| Deque axe DevTools | Browser extension and CI tooling | Pro around $45 per user per month |
| AudioEye | Automation, overlay and legal support | $49 to $799 a month, metered by traffic |
| accessiBe, UserWay and other overlays | JavaScript widgets injected into the page | About $490 to $3,990 a year per site |
| Accessibility Audit | Craft-native scanner, reports, statement and VPAT | One plugin licence. Standard up to 100 pages, Pro unlimited |
Need to audit fifty sites across six CMSs, scan PDFs, or buy a human audit with legal support? A SaaS platform earns its keep there. Read the full comparison
We checked this page too. See for yourself.
This button runs real checks against the page you’re reading, in your browser. The bakery demo is left out, because it’s broken on purpose.
- Images with alt textnot run
- Buttons with a namenot run
- Links with a namenot run
- Heading levels in ordernot run
- Page language setnot run
- Unique IDsnot run
- Landmarks presentnot run
Your first report in minutes.
Install
From the Plugin Store in your control panel, or with Composer.
Scan
Go to Accessibility, then Overview, and choose Scan all pages. Craft’s queue does the rest in the background.
Fix
Start with the rules that add the most points. Editors see their issues on the entry itself.
Needs Craft CMS 5 and PHP 8.2 or later. Installation guide
Install and scan
composer require johnhenry/craft-accessibility-audit php craft plugin/install accessibility-audit php craft accessibility-audit/audit/scan-all
Stop a deploy that makes things worse (Pro)
curl -s -H "Authorization: Bearer $A11Y_CI_TOKEN" \ https://example.com/actions/accessibility-audit/ci/check { "success": true, "passing": true, "score": 92, "threshold": 90 }
Questions
Is there an accessibility checker for Craft CMS?
Yes. Accessibility Audit is a Craft CMS 5 plugin that checks every page against WCAG 2.2 at level A, AA or AAA from inside the control panel, using 28 PHP rules plus axe-core on the rendered page. To try it on one page first, use the free accessibility checker, which runs the same PHP engine.
Does the European Accessibility Act apply to my website?
If you sell consumer services in the EU, quite possibly. Since 28 June 2025 it has covered e-commerce, online banking, e-books, passenger transport booking and more. Microenterprises providing services, with fewer than 10 staff and turnover or balance sheet under €2 million, are exempt. Its benchmark standard, EN 301 549, includes WCAG 2.1 AA, and the plugin scores against both. This isn’t legal advice, so check with your own adviser if you’re unsure.
What’s the difference between WCAG 2.1 and 2.2?
WCAG 2.2, published in October 2023, adds nine success criteria, including focus not obscured, minimum target size and accessible authentication, and removes 4.1.1 Parsing. A site that meets 2.2 AA also meets 2.1 AA. The plugin scores against 2.2.
Can it produce a VPAT or accessibility conformance report?
Yes, on Pro. It fills in a VPAT, also called an Accessibility Conformance Report or ACR, from your own scans, including the EN 301 549 clauses. Each criterion shows what the scans covered and what still needs a person, and you export it as a print-ready document or through your own template.
Will this make my site compliant?
No tool can do that on its own, and anyone who says otherwise is selling an overlay. Automated checks catch about a third of WCAG failures. The plugin catches those, asks you plain questions about the rest, and keeps a record of what you decided.
What does it scan?
Every element with a public URL: entries, categories, Craft Commerce products and custom element types. Pages with no element behind them, such as search results and paginated archives, are scanned too once you list them in settings.
Do I need AI?
No. Scanning, scoring, reports, the statement and the VPAT all work without it. Add your own Anthropic API key and Claude will draft alt text, VPAT remarks and plainer wording. It never picks a conformance level for you.
Does it work with headless or heavily cached sites?
Yes. Pro runs the admin overlay on Next, Nuxt, Astro or static front ends from a single script tag. If you use Blitz, the overlay stays out of the page cache.
Who can see the results?
There are four permissions: viewing reports, running scans, editing the VPAT and editing the statement. Scans only run on elements the person asking can view, and the front-end overlay only shows for logged-in admins.
Is the control panel translated?
The control panel and VPAT export are in English, German, French, Spanish, Italian and Dutch. Scan findings are in English.