01 Architect · L2 Dev Tools

L2 Dev Tools — build-time accessibility enforcement

L2 Dev Tools is the Architect-tier build-time enforcement layer. IDE extensions (VS Code, JetBrains), eslint-plugin-jsx-a11y, stylelint a11y rules, GitHub Actions, GitLab CI, pre-commit hooks, and the @ariada-org/mcp-server live here. Engineers see findings as they type, in code review, and at merge time — nothing surfaces only after deploy. The proactive code-generation track (research roadmap) takes the next step: agents that emit accessible-by-default code from scratch, not just remediate after the fact.

What it does

  • IDE extensions

    VS Code and JetBrains plugins surface a11y findings inline, against the same WCAG 2.2 + EN 301 549 rule set the scanner-axes use. Engineers fix at the cursor, not after the build.

  • ESLint & stylelint enforcement

    Curated eslint-plugin-jsx-a11y + stylelint a11y rule packs land at the first commit. Failing rules block the local lint step long before a pull request opens.

  • MCP server

    @ariada-org/mcp-server exposes ARIADA scanners and rule explanations to Claude Code, Cursor, Windsurf, and any other MCP-aware client. Authoring agents can ask the platform before they emit code.

  • CI/CD gate

    The CI/CD gate ships as a GitHub Action / GitLab job / Bitbucket pipeline / Azure DevOps task. Differential thresholds — stricter for AI-authored code, looser for human-authored — reflect measured bug-density asymmetry.

  • Backlog optimizer

    The backlog optimizer orders the fix backlog as a MIP problem: regulator priority, severity, effort, deadline. Engineers work the highest-leverage issues first, not the loudest.

  • Proactive code generation

    A research-track capability: ARIADA agents emit accessible-by-default code from scratch — correct ARIA, valid landmarks, working focus order — rather than remediate inaccessible output after the fact. Defensive-publication track per the portfolio roadmap.

Layer mapping

L2 Dev Tools sits between L1 Design (handoff input) and the L3–L10 scanner-axes (deployed-surface output). The CI/CD gate and backlog optimizer are the productized surfaces that ride on this layer.
Axis Role Direction
L0 MindsetSource of the rules engineers internalize and the IDE / lint / CI surfaces enforceRead
L1 DesignHandoff input — design artifacts arrive already satisfying L0 + L1 enforcementRead
L2 Dev ToolsThis layer — IDE / lint / CI / MCP enforcementSource
L3 Testing (WCAG / EAA)The CI/CD gate consumes the same rule set the L3 scanner-axes emitFeeds
CI/CD gateDifferential AI-vs-human thresholds at the merge boundary — clamper.aiHosts
Backlog optimizerMIP backlog optimizer — orders fixes by regulator priority + severity + effort + deadlineHosts
AI authorship attributionPer-line attribution feed that drives the CI/CD gate's differential thresholdsRead

Filed IP

ARIADA holds filed-IP positions covering the L2 Dev Tools surface — specifically the differential CI/CD gate with AI-versus-human thresholds and the MIP-based backlog optimizer. Both are provisional applications pending conversion to non-provisional and PCT within the 12-month window. The proactive accessible code generation capability is on a defensive-publication-first research track and has not been filed as a provisional; it is referenced here as roadmap only.

Application numbers, claim counts, and PCT deadlines are available for accredited-investor due diligence on the Legal & IP page.

Differentiator

Linter and IDE-extension competition at this layer is narrow. eslint-plugin-jsx-a11y is open-source and excellent but rule-only — no per-line authorship, no differential gating, no MCP surface, no MIP optimizer, no proactive-generation track. IBM Equal Access has the only patent footprint in CI a11y enforcement that we have identified, and it does not cover authorship-conditional gating. ARIADA's L2 stack — differential CI gate, MIP backlog optimizer, MCP server, and proactive-generation research track — sits in space competitors have not occupied.

Cross-references

  • L0 Mindset — the rules

    Opensource bible and brand-bibled LMS that engineers internalize before the IDE plugin matters. See L0 Mindset →

  • L1 Design — handoff input

    Figma / Adobe / Sketch / Canva plugins that ensure handoff artifacts arrive already accessible. See L1 Design →

  • CI/CD gate

    Marketplace standalone product: clamper.ai. Differential thresholds for AI-vs-human authored code. See CI/CD gate →

  • Backlog optimizer

    MIP backlog scheduler that orders fixes by regulator priority, severity, effort, and deadline. See backlog optimizer →

  • AI authorship attribution

    Per-line author signal that drives the CI/CD gate's differential thresholds and the backlog optimizer's effort estimates. See AI authorship attribution →

  • Pipeline overview

    All Architect / Detect / Remediate modules in one place. See all modules →

Enquire about the dev stack Visit clamper.ai

Source-level remediation only — agentic suggestions are not autonomous deployments; pull requests require client merge. Not a legal certification body. For accredited certification, customers consult a notified body or registered auditor.