The EAA is in force.Keep the proof of what you did.
Inclusive Forge scans your whole buyer journey with WooCommerce-specific accessibility rules, tells you which part of your theme or checkout to change and how — never an overlay widget — and keeps an evidence folder an auditor can read.
Your checkout works. For whom?
The same checkout, seen through different eyes — weak sight, keyboard only, a screen reader. Every lens reveals its own barrier, and every fix is one line of markup that you make and the evidence ledger records.
14px text and grey-on-grey dissolve. The fix is not a widget — it is contrast tokens in the theme, and the rows read again.
The focus ring walks the tab path and gets trapped circling the mini-cart. The fix frees it — Tab reaches Pay.
Postcode, editAn unnamed field is just “edit”. A label bound to the input is one line of markup — and the postcode field has a name.
the scanner filed this one as WCAG 3.3.2 on #billing_postcodeFind the barriers, fix them for real, keep the paper.
A scanner that states its own coverage, fixes that live in your theme rather than in a browser script, and a ledger an auditor can read.
Buyer-journey scanner
Home → product → cart → checkout, tested with WooCommerce-specific accessibility rules, not a generic page crawl.
Fix steps, not overlays
Every finding names the element and the change to make in your theme or checkout markup. Overlay widgets are discredited — we don't ship one.
Accessibility statement
You write the accessibility statement, in German, French and English, for you and your adviser to review before it goes live. We keep its versions and dates and publish it.
The auditor folder
A hash-chained journal of findings and fixes with dates — proof you acted, ready to hand over.
Monthly monitoring
Themes update, plugins change, regressions creep in. The scanner re-walks the journey every month.
Built for EU stores
Made for shops the law actually covers — EU stores with 10+ staff or €2M+ turnover.
Thirteen of the fifty. We would rather say so.
No scanner can check WCAG by machine alone, and a vendor implying otherwise is selling you a court date. 13 of the 50 criteria are automated here; for every one of the rest the coverage page names the manual work that remains.
13 of 50 checked automatically
8 WooCommerce rules and 7 general ones, run against reference fixtures with a precision gate — a rule that cries wolf is worse than no rule.
Connect the store, run the scan, fix and re-test.
Scan the journey
Connect your store; the scanner walks home, product, cart and checkout like a real buyer.
Fix it in your theme
Each finding comes with the repair for your theme or checkout. You make the change; nothing is papered over in the browser.
Keep the evidence
Mark the finding as fixed, then re-test. The journal records your note first and the re-test result after the finding. Publish your statement and leave monitoring on. When the auditor asks, you open the folder.
Mark it fixed. Watch the chain get longer.
Nothing in this ledger is ever edited or deleted: a fix is a new line whose hash carries the previous one. That is what makes the folder worth handing to an auditor — and what makes «we fixed it» something you can check rather than something you say.
-
#1
scan.completed
30 pages · 14 findings · score 62
37c57e5f -
#2
finding.found
critical · WCAG 3.3.2 · #billing_postcode
15638de7 -
#3
finding.fixed
label element bound to the postcode input
cbc94d86
each line carries the one before it
prev 15638de7 → cbc94d86
Marking it fixed does not turn the old line green — the finding stays on the record, and the fix is filed after it. An audit trail that can be tidied up is not one.
Speaks the standards
Three pages, no account
Give us a storefront address. We look at the home page, one product and the checkout, and email you the number of findings, counted by severity.
The EAA is not a someday. It applies now.
Directive (EU) 2019/882, in force for services since June 2025. We work to EN 301 549 and document the work; no tool can certify you compliant, and anyone who says otherwise is selling something.
Not legal advice. The figures above come from the project’s sourced fact sheet; where we have not read the source, we quote no amount.
Less than one afternoon of a lawyer.
No upsells, no surprises.
What happens after you pay
Two e-mails
The first is from Avakode, with your licence key. Within a couple of minutes a second one follows, with a link that signs you in to your portal at app.inclusiveforge.com. The link works once and lasts 24 hours.
Connect the store
Install the free Inclusive Forge plugin (version 1.3.2 or newer) on the store and paste the Site token and the Webhook secret from the Companion plugin panel of your portal under Settings → Inclusive Forge. Without the plugin, add the store in the portal and prove ownership by hand. The scanner confirms you own the store before it runs a full scan: by the ownership tag on your home page, or by a file you add.
No sign-in e-mail?
Open app.inclusiveforge.com/activate and enter the e-mail address you paid with and the key. The sign-in link goes to that address.
Already paid? Open the portal · Activate with your key
What runs where in Inclusive Forge
Which work happens inside your own install, what leaves it, what needs a paid plan, and what a lapsed licence leaves behind.
What the free tier does inside your own install
- The WordPress plugin adds `<meta name="inclusiveforge-verify" content="…">` to your site head, from a value you paste in.
- You paste the site token and the webhook secret from your Inclusive Forge account into the plugin settings; the webhook secret is stored encrypted.
- Your last scan is rendered in wp-admin from what the plugin already stored.
- "Re-test now" is a request to the service, not a scan inside your install.
What leaves your site when a feature is on, and where it goes
- Scanning runs on Cloudflare Workers with Browser Rendering and axe-core, not in your WordPress install: your page is fetched and rendered there.
- A scan of a site needs proof you own it, or an explicit request for a one-off public exposure check behind a rate limit and Turnstile.
- Ownership is proved by the verification meta tag on your home page, printed by the plugin or added to your theme by hand, or by a file at `/.well-known/inclusiveforge-verify.txt`.
- Scan traffic to your site happens only inside the scan pipeline, through Queues; a portal request makes no scan call of its own.
- Asking for a sign-in link does send one message out: your e-mail address goes to the mail provider Resend, in a POST to `api.resend.com`, because that letter carries the link.
- The one-off public exposure check posts your Turnstile token to `challenges.cloudflare.com` before the request is queued.
- When you press Re-test now, the plugin sends a signed request with your site token and your site address to `app.inclusiveforge.com`; it carries no page content.
- When a key is checked, on connecting a store or on `app.inclusiveforge.com/activate`, Inclusive Forge sends it to the Avakode licence service at `api.avakode.com`.
What needs Pro, credits or an outside service
- Inclusive Forge is a hosted service: tenants, scans, findings and the journal live in D1, screenshots and evidence packs in R2.
- Findings are mapped axe → WCAG 2.1 AA → EN 301 549 by a table the service ships.
- There is no Pro add-on to install: the plan lives with your account, not on your site.
What happens when the licence lapses
- A sign-in link you ask for works once and stops working after 15 minutes.
- The sign-in link in the e-mail that opens your account after payment works once and lasts 24 hours.
- A portal session lasts 30 days.
- Refunds: within 14 days of a payment you can ask for a refund in full, by email, the same 14 days as in Avakode's refund policy.
- When a licence is cancelled, refunded or expires, scans and re-tests stop, and the portal says which of the three it is. A payment that is being retried does not stop them.
- Your findings, journal and evidence pack stay in the portal for as long as the account exists; access is not time-limited.
How long data is kept, and how you take it out
- Webhook deliveries that reached a settled status are deleted after a cutoff.
- Evidence packs and screenshots are stored in R2 and downloadable from the portal.
- Scans and findings are kept indefinitely; findings and the ledger are append-only and nothing deletes them.
- Screenshots are stored in R2 and nothing in the codebase deletes them.
- Export is the per-site journal page, printable from the browser; there is no bulk download across sites.
What European stores ask us first
An evidence folder you can hand to an auditor.
The companion plugin proves you own the store and publishes your accessibility statement; the scans, the findings and the evidence pack live in your portal. Every paid plan includes priority email support while your licence is active.
One forge. Twelve tools. One fire.
Every tool is forged in the same workshop — one AI engine, one design language, one account. Take more off the wall and the whole set gets cheaper.
Lang Forge
AI translation & multilingual sites
Explore
Rank Forge
AI SEO & content optimization
Explore
Form Forge
AI forms, flows & submissions
Explore
Field Forge
Custom fields + GraphQL
Explore
Guard Forge
WordPress security & threat defence
Explore
Velocity Forge
Core Web Vitals, safely
Explore
Draft Forge
AI drafts, on your schedule
Explore
Cascade Forge
Automation that runs in your site
Explore
Clearway Forge
See, serve & control AI shoppers in WooCommerce
Explore
Profit Forge
Money audit for WooCommerce
Explore
Renew Forge
UK subscription rules for WooCommerce Subscriptions
Explore
Forge Builder
Pick two or more tools and the price drops — up to −35% on the full set.
Build my set