Answers to the questions people actually ask us.

inklu scans your web app or codebase against WCAG 2.2, finds accessibility violations, and opens pull requests on your GitHub repo that fix them. It is a tool for engineering teams that want accessibility baked into the normal code-review workflow instead of handled by a separate team or a runtime overlay.

axe-core is the open-source detection engine we use under the hood (v4.11), alongside 50+ proprietary rules of our own. axe DevTools (from Deque) recently added AI-assisted remediation through their MCP server. The difference is workflow: axe DevTools is developer-facing (browser extension, IDE plugins, individual developer tooling), while inklu runs at the CI/PR level — it scans automatically on push, generates fixes, and opens the pull request so the team reviews a clean diff. If your team prefers in-browser spot-checking, axe DevTools is great. If you want automated scanning and fixes in your GitHub workflow, that is what inklu does.

HTML, CSS, JSX (including TSX), and SCSS today. Angular support is on the roadmap. The scanner works against rendered output, so if your framework compiles to HTML it will generally work — but the languages listed above are what we actively test and support.

We ship a GitHub Actions integration today. GitLab CI and CircleCI support are on the roadmap. If you run a different CI system and want to evaluate, reach out — we can work with you.

We are building an MCP server that will let AI coding agents (Claude Code, Cursor, etc.) call inklu for scanning and auto-fixes inside the agent loop. It is not publicly available yet. If you are interested in early access when it launches, join the waitlist or mention it during your demo.

WCAG 2.2 Level AA by default. We map findings to the specific success criteria so your team and your auditor can trace every finding back to the spec.

Yes. We generate formatted compliance reports for AODA (Ontario), ADA Title II (US state and local government), and the European Accessibility Act. These align with the WCAG 2.2 AA baseline each regulation requires.

We are not lawyers and the reports are not legal advice. They give your compliance team the documentation they need to support a filing.

Not yet — VPAT and ACR generation is on our roadmap. If you need a VPAT for procurement today, book a demo and we can discuss what we can do to help in the interim.

No, and no honest vendor should claim it does. Automated tooling catches a meaningful subset of accessibility issues — the commonly cited industry range is 30 to 50 percent. The rest requires human testing with assistive technology.

What inklu does is eliminate the violations that should never have shipped in the first place, so your human testers can focus on the judgment calls that actually need a person.

Overlay tools inject JavaScript at runtime to patch accessibility issues without modifying source code. Some users find value in them, particularly for sites where the source code is not accessible to the team. At the same time, disability advocacy organizations have raised concerns about how overlays interact with assistive technology, and regulators have scrutinized some overlay vendors' compliance claims.

inklu takes a different approach: we fix the underlying code. If your team owns the codebase and can review pull requests, fixing the source is the more durable path. If you do not have source code access, an overlay may be the only practical option for your situation.

A token is a unit of work. A web scan costs 2 tokens, a repo scan costs 8 tokens, and an auto-fix pull request costs 1 token. You choose how to spend them each month.

Scans pause until you upgrade to a higher plan. You can upgrade at any time and the change prorates immediately — no waiting for the next billing cycle.

Yes, up or down, any time. Upgrades prorate immediately; downgrades take effect at the next billing cycle so you keep the capacity you already paid for.

Coming soon. We intend to support both monthly and annual billing. Enterprise engagements can be structured annually today — ask during your demo.

Quoted per customer based on token volume and support needs. Book a demo and we will scope it together — we aim to have a written quote to you within a week.

Yes, but it starts with a demo. Book a 20-minute call and we will set your team up with 14 days and 50 credits — enough to run a few full repo scans and ship several auto-fix PRs on your own code. Self-serve signup is coming soon.

If you do nothing, your account pauses — scans stop, but your data stays. Pick any paid plan (Starter at $29, Growth at $99, Scale at $349, or Enterprise custom) to resume. No auto-charging, no re-onboarding.

Trial accounts get 50 credits and full access to every feature. If you need more time or credits for a thorough evaluation, let us know during the demo — we are flexible.

Book a demo if you are evaluating inklu for your team and want to start a 14-day trial. Join the waitlist if you are a solo developer or want to be notified when self-serve signup goes live.

No. Scans run on ephemeral infrastructure and source is purged after each run. Scan reports are also generated on the fly and are not persisted in long-term storage.

Scans run in our cloud infrastructure in US East.

No. inklu does not train any model on customer code. Your source is processed for scanning and fix generation only, then purged.

The inklu GitHub app requests user:email, read:user, repo, and read:org scopes. The repo scope grants read and write access to the repositories you select — this is required for opening pull requests. inklu never commits directly to your default branch; every fix goes through a pull request that your team reviews and merges.

Moe Als (design) and Henrik Hey (engineering), based in Toronto, Ontario. We built inklu because we kept watching engineering teams treat accessibility as an afterthought — not because they did not care, but because the tools made it painful. We wanted a tool that made the accessible path the default path.

Short for "inclusive."

Email hello@inklu.io for anything — sales, support, partnerships, a bug report, a thoughtful disagreement with something on this page. We read every reply.