What we've shipped, what we're building, what we're not doing

Working in production, used by real (early) adopters.

• axe-core 4.11 scanner

  WCAG 2.0 / 2.1 / 2.2 A+AA evaluation, headless Chromium via Playwright. Same engine as the GitHub Action, the CLI, and the MCP server.

• GitHub Action

  Composite action on the Marketplace as asafamos/axle-action. Posts a sticky PR comment with violations, fails the check at configurable severity.

• create-issues mode

  Opt-in axle-action mode that opens / updates / closes GitHub Issues per violation, deduped by axe rule + first-node selector. Treat it like Renovate, for accessibility.

• Claude fix suggestions in PR comments

  With with-ai-fixes: true, the PR comment includes a per-violation diff suggesting how to remediate. Diffs are HTML-level (current → fixed), and apply cleanly for static markup; React/Vue/template-engine apps need a human in the loop for the source mapping.

• axle-mcp Model Context Protocol server

  npm install -g axle-mcp. Wires Claude Desktop / Cursor / Cline / Continue.dev to axle. Two tools: scan_url, explain_violation. Stdio transport. Verified end-to-end.

• VS Code extension

  asafamos.axle-a11y on the Microsoft Marketplace. Command palette scan, in-editor webview with the report, share to /r/<id>.

• axle-storybook addon

  axle-storybook on npm. Storybook 7/8/9 compatible, runs axe against every story, panel UI with severity badges.

• Hosting plugins — Netlify / Cloudflare Pages / Vercel

  Build-time integration plugins on npm. Each fails the deploy when violations cross the threshold. Low download counts so far — surface, not yet adopted.

• WordPress plugin (AsafAmos Accessibility Scanner)

  axe-core runs entirely in the WP admin browser via a hidden iframe. Free version on the WordPress.org directory (under review at time of writing).

• /api/scan + /api/fix hosted endpoints

  Public hosted scanner. 3 scans/day/IP free, unlimited with an axle API key. Powers the web /free-scan form, the MCP server, the Slack App, and the ChatGPT GPT.

• /r/<id> shareable certificate URLs

  Every scan produces a public permalink with custom OG image. 30-day TTL. Used as a viral primitive in cold emails, Jira tickets, EAA conformance bundles.

• Hebrew accessibility statement generator

  /statement runs locally in the browser, generates a תקנה 35-aligned Hebrew statement. No upload, no signup.

• OpenAPI 3.1 spec + .well-known/ai-plugin.json

  Public API spec at /openapi.yaml. ChatGPT GPT builders, Claude tool-use, OpenAPI→MCP bridges all import from here.

Promised in marketing copy, partly built, not 'done'. We'd rather tell you here than have you discover it during a sales call.

• Auto-opening fix PRs (not just Issues)

  The marketing copy on /why-axle calls out 'Claude opens a PR per violation'. Today, the create-issues mode opens GitHub Issues with the AI fix in the body. The next phase is to map the AI diff back to the source file (HTML / JSX / Vue template) and open a real draft PR. Hard part is the selector→source mapping for templating engines. Plan: ship for static HTML first, then JSX/TSX with a heuristic, then templating engines via plugin contracts.

• Slack App (hosted listing)

  /slack landing + /axle scan slash command code is shipped (see packages/axle-slack/). The hosted Slack App Directory listing is in the pipeline. Self-host works today.

• EU multilingual statement pack

  Hebrew statement ships. The /pricing $299 Business tier promises German / French / Italian / Spanish / Dutch / Portuguese / Swedish / Polish. The infrastructure is in place; per-country translations + legal review for each are in progress. Don't promise day-one delivery on this tier yet.

• Cal.com / Calendly demo booking

  /demo currently uses a pre-filled mailto with a context-gathering template. Direct calendar booking will replace it once the booking tool is set up.

• ChatGPT GPT publishing

  OpenAPI spec is live (3.1.0, validated). The actual GPT publication is blocked by an OpenAI workspace-side bug on the owner account. Will retry once OpenAI resolves on their side.

• Reddit account recovery

  Posts from u/SwapVideoTeam were auto-filtered by Reddit (looks like a shadowban from posting cadence on a fresh account). Migration plan: post via a different channel until the account is whitelisted via Reddit appeals.

Things we won't build, with our reason. Saves both sides time on calls.

• Replacing axe DevTools Pro at the enterprise tier

  Deque's product is mature and integrated. axle isn't trying to win that fight. For teams with budget for axe DevTools Pro and an existing relationship with Deque, run both for a month and pick.

• An accessibility overlay widget

  Never. Overlay widgets do not work. The FTC settled accessiBe at $1M in January 2025 specifically for deceptive claims about overlay widgets. axle scans the served HTML — the only thing regulators actually evaluate. See /why-not-overlay.

• A managed dashboard with SSO, RBAC, audit logs

  axle is a CI tool that uses GitHub / Linear / Jira as the dashboard. If you need a single-pane-of-glass managed dashboard, look at Tenon.io or axe Watcher.

• A general-purpose AI coding tool

  axle generates fixes for a specific class of violations using axe-core's rule taxonomy. It is not a general code-generation tool. For that, use Cursor / Claude Code / Copilot — and install axle-mcp into them so accessibility is one of the things they can call.