Ariada · Module

Module

Durchsuchen Sie die Auslieferungs- und Integrationsmodule von Ariada mit transparenten Angaben zu ihrem Deployment- und Distributionsstatus.

Modulspezifische Quellinhalte sind derzeit auf Englisch verfügbar.

0Geplant
236In Entwicklung
0Ausgeliefert
0Produktion

Module

In Entwicklung

.NET global tool + MSBuild task, in Ariada channel pack 11, exposes this public implementation purpose: .NET global tool and MSBuild task for running Ariada accessibility evidence gates from ASP.NET, Razor, Blazor, MVC, and static publish outputs.

In Entwicklung

1C-Bitrix module, in Ariada channel pack 21, exposes this public implementation purpose: Self-contained 1C-Bitrix module for presenting an Ariada accessibility gate. PHP never scans a page. An administrator either runs the preinstalled ariada executable supplied by @ariada-org/cli or consumes the CLI's scan.json CI artifact.

In Entwicklung

Adobe Experience Manager (AEM) integration, in Ariada channel pack 23, exposes this public implementation purpose: ariada-aem is an installable AEM content package for accessibility review in the authoring workflow. It runs the real @ariada-org/cli@0.1.0 against an allowlisted authored or published page, then shows impact counts, WCAG 2.2 criteria, EN 301 549 references, finding details, and an author-only full report.

In Entwicklung

Adobe XD plugin, in Ariada channel pack 13, exposes this public implementation purpose: Adobe XD export adapter and plugin panel fixture for Ariada CLI scans.

In Entwicklung

Alfred workflow, in Ariada channel pack 9, exposes this public implementation purpose: Alfred workflow scaffold for running Ariada accessibility scans from a launcher keyword.

In Entwicklung

Angular CLI builder + schematic, in Ariada channel pack 6, exposes this public implementation purpose: Angular CLI builder and schematic helpers for scanning build output with Ariada.

Asana app

S159
In Entwicklung

Asana app, in Ariada channel pack 17, exposes this public implementation purpose: Self-contained, thin Asana sink for JSON emitted by @ariada-org/cli or the Ariada GitHub Action. It creates or updates one Asana task per open finding in a target project, places tasks in severity sections, maps severity/rule ID to optional custom fields, and deduplicates by a stable SHA-256 finding fingerprint.

In Entwicklung

Astro integration, in Ariada channel pack 3, exposes this public implementation purpose: Astro integration that scans built HTML with Ariada and writes accessibility reports at build completion.

In Entwicklung

AWS Amplify integration, in Ariada channel pack 18, exposes this public implementation purpose: Thin AWS Amplify Hosting integration for @ariada-org/cli accessibility gates.

In Entwicklung

AWS Lambda layer / CodeBuild step, in Ariada channel pack 18, exposes this public implementation purpose: AWS CodeBuild and Lambda integration surface for the Ariada accessibility CLI.

In Entwicklung

axe-core custom ruleset published to npm, in Ariada channel pack 19, exposes this public implementation purpose: axe-core configuration payload for Ariada accessibility rules

In Entwicklung

Axure RP extension, in Ariada channel pack 13, exposes this public implementation purpose: Thin Axure RP HTML export adapter for the shared Ariada CLI scanner.

In Entwicklung

Azure DevOps extension, in Ariada channel pack 4, exposes this public implementation purpose: Thin Azure Pipelines task wrapping ariada scan. The task does not implement scanner logic; it shells out to the Ariada CLI and publishes the output directory as Azure Pipelines evidence.

In Entwicklung

Azure Static Web Apps integration, in Ariada channel pack 18, exposes this public implementation purpose: Azure Static Web Apps preview gate and report integration over @ariada-org/cli.

In Entwicklung

Babel plugin, in Ariada channel pack 5, exposes this public implementation purpose: Babel plugin adapter for source-visible Ariada JSX accessibility checks.

In Entwicklung

Backstage (Spotify) plugin, in Ariada channel pack 8, exposes this public implementation purpose: Backstage frontend plugin surface for Ariada accessibility findings.

In Entwicklung

Balsamiq integration, in Ariada channel pack 13, exposes this public implementation purpose: S126 is a documented Balsamiq export recipe plus a small Node wrapper. It does not add Balsamiq-side code because there is no Balsamiq plugin marketplace for a native Ariada plugin.

Bazel rule

S231
In Entwicklung

Bazel rule, in Ariada channel pack 24, exposes this public implementation purpose: Hermetic Bazel action wiring for the Ariada accessibility scanner CLI

In Entwicklung

Beehiiv newsletter/landing scan recipe, in Ariada channel pack 22, exposes this public implementation purpose: Shell-free Ariada URL and exported-HTML scan recipe for Beehiiv publications

In Entwicklung

BigCommerce app, in Ariada channel pack 16, exposes this public implementation purpose: This is a self-contained, thin BigCommerce embedded-app boundary. It owns the BigCommerce install/load/uninstall callbacks, signed-payload verification, Store Information URL lookup, and a small findings panel. It delegates accessibility scanning to the existing @ariada-org/cli; it does not contain scanner rules, WCAG interpretation, or a provider SDK.

In Entwicklung

Bit (bit.dev) integration, in Ariada channel pack 24, exposes this public implementation purpose: Native Bit build task for per-component Ariada accessibility scans of rendered output.

In Entwicklung

Bitbucket Pipe, in Ariada channel pack 8, exposes this public implementation purpose: This is the standalone, listing-grade Bitbucket Pipe. It is distinct from the earlier raw CI adapter: this directory contains the marketplace pipe layout (Dockerfile, pipe.yml, runner, and example pipeline).

In Entwicklung

Brevo (ex-Sendinblue) landing/email scan recipe, in Ariada channel pack 22, exposes this public implementation purpose: Brevo landing-page, campaign web-view, and exported-email accessibility scan recipe for Ariada.

In Entwicklung

BrowserStack integration, in Ariada channel pack 14, exposes this public implementation purpose: Thin BrowserStack remote-session adapter for Ariada accessibility scans and CI gates.

In Entwicklung

Bubble plugin, in Ariada channel pack 2, exposes this public implementation purpose: Bubble plugin scaffold and local evidence fixture for Ariada hosted scans.

In Entwicklung

Builder.io plugin, in Ariada channel pack 15, exposes this public implementation purpose: Builder.io editor adapter for Ariada accessibility scan results.

In Entwicklung

Campaign Monitor landing/email scan recipe, in Ariada channel pack 22, exposes this public implementation purpose: Campaign Monitor public-page and exported-email accessibility scan recipe backed by @ariada-org/cli.

In Entwicklung

Canvas LMS (LTI tool), in Ariada channel pack 23, exposes this public implementation purpose: Self-contained LTI 1.3 course accessibility scanner powered by Ariada

In Entwicklung

Capacitor plugin, in Ariada channel pack 20, exposes this public implementation purpose: Web-bundle-only Capacitor integration for the Ariada accessibility CLI.

In Entwicklung

Carrd integration, in Ariada channel pack 15, exposes this public implementation purpose: Thin S142 adapter over @ariada-org/cli. It scans one Carrd published URL and maps the CLI JSON result to a typed result with a severity-based CI gate. Carrd sites are normally one page, so the boundary is explicitly published-site/page.

In Entwicklung

Changesets / release hook, in Ariada channel pack 24, exposes this public implementation purpose: Changesets release hook that blocks versioning and publishing when the Ariada accessibility gate fails.

In Entwicklung

Chromatic integration, in Ariada channel pack 14, exposes this public implementation purpose: Chromatic Storybook adapter for per-story Ariada accessibility reports and combined CI gates.

In Entwicklung

Chrome DevTools panel, in Ariada channel pack 4, exposes this public implementation purpose: - A manifest fragment showing the required Chrome extension entry point: devtoolspage: "devtools.html". - A validation script that checks the existing Chrome extension build has: - a DevTools page that creates the ariada panel; - a panel that targets chrome.devtools.inspectedWindow.tabId; - scan requests routed through the existing background/content

In Entwicklung

CI adapters for non-GitHub CI (new builds), in Ariada channel pack 1, exposes this public implementation purpose: GitLab CI/CD component for the Ariada differential accessibility gate.

In Entwicklung

ClickUp app, in Ariada channel pack 17, exposes this public implementation purpose: Self-contained ClickUp task sink for Ariada accessibility findings.

In Entwicklung

Cloudflare Pages/Workers build integration, in Ariada channel pack 8, exposes this public implementation purpose: This is the first Cloudflare-native Ariada channel. It is distinct from earlier Vercel/CI references: Pages builds can call build-step.sh, and Workers can proxy a managed hosted scan API call without embedding secrets in source.

In Entwicklung

CodeSandbox / StackBlitz integration, in Ariada channel pack 9, exposes this public implementation purpose: CodeSandbox and StackBlitz recipe for running Ariada in an in-browser development workspace.

In Entwicklung

Concrete CMS package, in Ariada channel pack 21, exposes this public implementation purpose: This directory contains a self-contained Concrete CMS 9 package. It accepts a configured site URL and either:

In Entwicklung

Confluence app (Atlassian), in Ariada channel pack 23, exposes this public implementation purpose: Forge Custom UI and authenticated remote scanner for Confluence page accessibility.

In Entwicklung

Contentful app, in Ariada channel pack 7, exposes this public implementation purpose: Contentful App Framework scaffold for editor-side accessibility checks. The app expects a rendered preview URL and sends that URL to the Ariada scan API.

In Entwicklung

Cordova plugin, in Ariada channel pack 20, exposes this public implementation purpose: Thin Cordova www-bundle integration for the Ariada accessibility CLI.

In Entwicklung

Craft CMS plugin, in Ariada channel pack 7, exposes this public implementation purpose: Craft 5 plugin scaffold for scanning rendered entry URLs through the existing Ariada CLI or hosted scan API.

In Entwicklung

Cypress plugin, in Ariada channel pack 14, exposes this public implementation purpose: Cypress custom command and Node task for running Ariada accessibility scans from Cypress suites.

In Entwicklung

Dart/Flutter pub package (Flutter web), in Ariada channel pack 11, exposes this public implementation purpose: The package is deliberately thin. It shells out to the shared @ariada-org/cli, reads multi-domain-report.json, prints a Dart-friendly summary, and returns a CI exit code:

In Entwicklung

Dash component, in Ariada channel pack 10, exposes this public implementation purpose: Dash helper package that scans a running Dash app URL with the shared Ariada CLI.

In Entwicklung

Datadog integration, in Ariada channel pack 19, exposes this public implementation purpose: S180 is a self-contained TypeScript consumer of Ariada CLI JSON. It converts one strict result object into Datadog metric series and, when the accessibility gate fails, one Datadog event. There is no Ariada runtime dependency and no Datadog SDK dependency.

In Entwicklung

DigitalOcean App Platform integration, in Ariada channel pack 18, exposes this public implementation purpose: Production-oriented DigitalOcean App Platform job wrapper for @ariada-org/cli.

In Entwicklung

Directus extension, in Ariada channel pack 7, exposes this public implementation purpose: Directus extension scaffold for item-level accessibility scans. The extension maps a collection item to a rendered front-end URL and sends that URL to Ariada.

In Entwicklung

Discord bot, in Ariada channel pack 9, exposes this public implementation purpose: Discord bot scaffold for posting Ariada accessibility gate results. It does not host scan logic. A slash command or CI webhook provides an Ariada CLI result and the bot renders that result as a Discord embed.

In Entwicklung

Django app, in Ariada channel pack 10, exposes this public implementation purpose: Reusable Django app for running Ariada accessibility scans from manage.py. It renders Django routes with the Django test client, serves that rendered HTML through a temporary localhost server when needed, and delegates scanning to the shared @ariada-org/cli.

In Entwicklung

DNN (DotNetNuke) module, in Ariada channel pack 23, exposes this public implementation purpose: A production-native DNN Platform module for editors and portal administrators. It scans the current rendered page with the real Ariada OSS CLI, Playwright, and axe analyzer, then shows pass/fail, top WCAG findings, and a permission-checked full report. It does not implement scanner rules in C and does not call a hosted Ariada service.

In Entwicklung

Docker image (GHCR + Docker Hub), in Ariada channel pack 3, exposes this public implementation purpose: This directory contains the Docker packaging for the Ariada CLI.

In Entwicklung

Docusaurus plugin, in Ariada channel pack 6, exposes this public implementation purpose: Docusaurus plugin that scans static build output with Ariada.

In Entwicklung

Dorik integration, in Ariada channel pack 15, exposes this public implementation purpose: Production thin adapter over @ariada-org/cli. It scans a published Dorik site URL, maps the CLI JSON into a stable result, and returns a deterministic severity gate. It contains no scanner rules and makes no vendor-authenticated calls.

In Entwicklung

Drupal module, in Ariada channel pack 2, exposes this public implementation purpose: Drupal 10/11 module that runs Ariada accessibility scans from the admin UI and from Drush. The module is a thin adapter: it does not implement scanning logic. It calls the Ariada CLI locally, or an explicitly configured hosted scan endpoint.

In Entwicklung

Eclipse plugin (Marketplace), in Ariada channel pack 9, exposes this public implementation purpose: Eclipse plugin scaffold for turning Ariada CLI findings into IDE markers. It is thin by design: Ariada CLI owns scanning, and the plugin maps returned findings onto Eclipse marker concepts.

Ecwid app

S148
In Entwicklung

Ecwid app, in Ariada channel pack 16, exposes this public implementation purpose: Production thin adapter for an Ecwid external app. The OAuth callback and server-side token exchange identify the store; the readstoreprofile REST permission resolves the Instant Site or configured storefront URL. The adapter then sends PDP, PLP, cart, and checkout URLs to the existing @ariada-org/cli and renders its accessibility findings in an Ecwid

In Entwicklung

Electron app integration, in Ariada channel pack 20, exposes this public implementation purpose: Electron renderer integration for the Ariada accessibility CLI.

In Entwicklung

Eleventy (11ty) plugin, in Ariada channel pack 6, exposes this public implementation purpose: Eleventy plugin that scans generated site output with Ariada.

In Entwicklung

Elixir Hex package (Phoenix), in Ariada channel pack 11, exposes this public implementation purpose: ariadaphoenix is a thin Hex package for Phoenix applications. It adds mix ariada.scan, which shells out to the shared @ariada-org/cli scanner and parses the JSON result for CI-friendly gate output.

In Entwicklung

Emacs package (MELPA), in Ariada channel pack 9, exposes this public implementation purpose: Emacs package scaffold for running the Ariada accessibility CLI and surfacing findings in a compilation buffer.

In Entwicklung

esbuild plugin, in Ariada channel pack 5, exposes this public implementation purpose: esbuild plugin that scans emitted HTML with Ariada accessibility checks.

In Entwicklung

ESLint plugin, in Ariada channel pack 2, exposes this public implementation purpose: ESLint 9 flat-config plugin for source-detectable ariada accessibility checks.

In Entwicklung

Expo plugin, in Ariada channel pack 20, exposes this public implementation purpose: Web-only Expo export integration for the Ariada accessibility CLI.

In Entwicklung

ExpressionEngine add-on, in Ariada channel pack 21, exposes this public implementation purpose: S203 is a self-contained ExpressionEngine 7.2+ control-panel add-on. It stores one configuration per EE site, runs a preinstalled @ariada-org/cli process or consumes a CI-produced scan.json, validates the Ariada CLI v1 envelope, and shows a bounded pass/fail summary with top violations.

In Entwicklung

FastAPI middleware, in Ariada channel pack 10, exposes this public implementation purpose: Reusable FastAPI/Starlette middleware and CLI bridge for running Ariada accessibility scans against FastAPI routes. The integration renders FastAPI routes with TestClient, serves that rendered HTML through a temporary localhost server when needed, and delegates scanning to the shared @ariada-org/cli.

In Entwicklung

Figma plugin (new build), in Ariada channel pack 1, exposes this public implementation purpose: Local Figma plugin for design-time Ariada accessibility checks. It scans the current Figma selection and reports design-mappable issues for contrast, target size, text alternatives, and semantic layer metadata before a design becomes code.

In Entwicklung

Finish the Shopify app to listing-grade, in Ariada channel pack 1, exposes this public implementation purpose: Shopify admin app backend for running accessibility checks on a merchant storefront. It exposes a Node HTTP server, a small embedded admin page, a full discover - scan - gate pipeline, scan history, a downloadable HTML report, and the three mandatory Shopify privacy webhooks.

In Entwicklung

Firefox Add-ons (AMO) listing, in Ariada channel pack 9, exposes this public implementation purpose: web-ext lint is the preferred AMO-style validation when web-ext is installed. This machine does not have web-ext, so the local gate validates the MV3 contract and builds a reproducible unsigned package.

In Entwicklung

Flask extension is Ariada's browser review surface in channel pack 10. It gives reviewers a named surface for running accessibility checks and evaluating evidence in the workflow represented by Flask extension.

In Entwicklung

Fly.io integration, in Ariada channel pack 18, exposes this public implementation purpose: Production-oriented Fly.io release and scheduled-check wrapper for @ariada-org/cli

In Entwicklung

Framer plugin, in Ariada channel pack 4, exposes this public implementation purpose: Framer plugin scaffold for local Ariada design-time accessibility checks.

In Entwicklung

Gatsby plugin, in Ariada channel pack 6, exposes this public implementation purpose: Gatsby plugin that scans public build output with Ariada accessibility checks.

In Entwicklung

Ghost integration, in Ariada channel pack 7, exposes this public implementation purpose: Webhook receiver for Ghost Custom Integrations. It scans the rendered published post URL through Ariada after post.published.

In Entwicklung

GitBook integration, in Ariada channel pack 12, exposes this public implementation purpose: Thin GitBook URL/export scanner wrapper over @ariada-org/cli.

In Entwicklung

Gitea/Forgejo Action, in Ariada channel pack 8, exposes this public implementation purpose: This stream packages Ariada as a Gitea/Forgejo Actions-compatible action. Gitea Actions are mostly compatible with GitHub Actions, so this action uses the composite action.yml shape and calls @ariada-org/cli.

In Entwicklung

GitHub Codespaces / devcontainer Feature, in Ariada channel pack 8, exposes this public implementation purpose: This is a GitHub Codespaces / Dev Containers Feature that installs @ariada-org/cli in a development container. It is packaging only; scanning remains in the published CLI.

In Entwicklung

GitLab CI/CD Component (GitLab CI Catalog), in Ariada channel pack 8, exposes this public implementation purpose: This directory packages Ariada as a GitLab CI/CD Catalog component, not as the raw GitLab template from the earlier CI adapter work. Consumers include templates/ariada.yml as a versioned component and pass typed spec:inputs.

In Entwicklung

Gitpod integration, in Ariada channel pack 9, exposes this public implementation purpose: Gitpod recipe for running Ariada accessibility scans when a cloud workspace opens or when a developer runs the scan task manually.

In Entwicklung

Glide integration, in Ariada channel pack 15, exposes this public implementation purpose: This is a thin published-URL recipe over @ariada-org/cli. It scans the URL of a published Glide app/page; it does not reimplement accessibility rules or inspect a private Glide editor project.

In Entwicklung

Go module (go install), in Ariada channel pack 11, exposes this public implementation purpose: The module is deliberately thin. It shells out to the shared @ariada-org/cli, reads multi-domain-report.json, prints a Go-friendly gate summary, and returns a CI exit code:

In Entwicklung

Google Cloud Build step, in Ariada channel pack 18, exposes this public implementation purpose: Thin Google Cloud Build gate and report-only adapter for @ariada-org/cli.

In Entwicklung

Gradle plugin (Java/Kotlin), in Ariada channel pack 11, exposes this public implementation purpose: gradle-ariada is a thin Gradle adapter for the shared @ariada-org/cli. It does not implement scanning rules. It registers an ariadaScan task that invokes ariada scan, reads the generated scan.json, prints a Gradle-native summary, and can fail the build when findings cross the configured gate.

In Entwicklung

Grafana plugin / datasource, in Ariada channel pack 19, exposes this public implementation purpose: Production-importable Grafana dashboard and validation gates for Ariada accessibility metrics.

In Entwicklung

Grav (flat-file) plugin, in Ariada channel pack 21, exposes this public implementation purpose: Grav Ariada is a self-contained Grav 1.7 plugin that renders a strict, read-only Ariada accessibility gate in classic Grav Admin. PHP never scans the site. It either reads one pre-generated scan.json file or launches the official @ariada-org/cli as an argument vector and reads that CLI artifact.

In Entwicklung

Grunt plugin, in Ariada channel pack 5, exposes this public implementation purpose: Grunt multi-task adapter for Ariada HTML accessibility scans.

In Entwicklung

Gulp plugin, in Ariada channel pack 5, exposes this public implementation purpose: Object-mode Gulp adapter that scans each HTML Vinyl file with Ariada and attaches findings to file.ariadaFindings.

In Entwicklung

Hexo plugin, in Ariada channel pack 12, exposes this public implementation purpose: Hexo aftergenerate adapter that scans generated public output with the Ariada CLI.

In Entwicklung

Histoire / Ladle addon (Storybook-alternatives), in Ariada channel pack 24, exposes this public implementation purpose: Headless Ariada accessibility runner and setup contracts for Histoire and Ladle stories.

In Entwicklung

Homebrew formula/tap, in Ariada channel pack 3, exposes this public implementation purpose: This directory is the ready-to-copy tap layout for ariada-org/homebrew-tap.

In Entwicklung

HubSpot CMS app/module, in Ariada channel pack 22, exposes this public implementation purpose: HubSpot Marketplace App Home, CMS module, and signed external scan service for Ariada CLI

In Entwicklung

Hugo module, in Ariada channel pack 12, exposes this public implementation purpose: Thin Hugo module and post-build Ariada CLI evidence wrapper.

In Entwicklung

Ionic integration, in Ariada channel pack 20, exposes this public implementation purpose: Thin Ionic web integration for the @ariada-org/cli accessibility scanner.

In Entwicklung

Jekyll plugin, in Ariada channel pack 12, exposes this public implementation purpose: Thin Jekyll plugin for running Ariada evidence scans after a Jekyll site is written. The plugin registers a :site, :postwrite hook, then delegates to the shared @ariada-org/cli scanner. It does not implement scanning rules in Ruby.

In Entwicklung

Jenkins plugin, in Ariada channel pack 4, exposes this public implementation purpose: The agent must have ariada on PATH, or pass cli: '/path/to/ariada'.

In Entwicklung

JetBrains plugin (new build), in Ariada channel pack 1, exposes this public implementation purpose: JetBrains IDE adapter for Ariada. The plugin adds a Tools menu action and an Ariada tool window that invokes the existing @ariada-org/cli scanner for a project URL and lists returned findings.

In Entwicklung

Jira app (Atlassian Marketplace), in Ariada channel pack 17, exposes this public implementation purpose: Thin Atlassian Forge-compatible sink for ariada CLI/Action JSON. It creates one Jira Bug per finding, maps WCAG/EN 301 549 context into Jira ADF, labels the issue with severity/rule/fingerprint, and skips matching open issues.

In Entwicklung

Joomla plugin, in Ariada channel pack 2, exposes this public implementation purpose: Joomla 5 administrator component for running Ariada scans from a CMS admin surface. The component is intentionally thin: it stores scan settings, invokes the configured Ariada CLI or a compatible hosted scan endpoint, and renders the latest JSON report in Joomla administrator.

In Entwicklung

JSR (jsr.io) package publish, in Ariada channel pack 8, exposes this public implementation purpose: JSR-facing TypeScript adapter that builds shared @ariada-org/cli scanner commands for Deno and TS-first consumers.

In Entwicklung

JupyterLab extension, in Ariada channel pack 10, exposes this public implementation purpose: JupyterLab UI bridge for scanning rendered notebook output with Ariada.

In Entwicklung

Kirby (flat-file) plugin, in Ariada channel pack 21, exposes this public implementation purpose: Self-contained Kirby 4/5 plugin that presents a strict Ariada accessibility result in a dedicated Panel area. It either consumes a configured CI artefact or launches the external @ariada-org/cli; PHP never implements or substitutes an accessibility scan.

In Entwicklung

Kit (ex-ConvertKit) landing/newsletter scan recipe, in Ariada channel pack 22, exposes this public implementation purpose: Kit landing-page, newsletter-page, and exported-broadcast accessibility scan recipe for Ariada.

In Entwicklung

Klaviyo landing/email scan recipe, in Ariada channel pack 22, exposes this public implementation purpose: Klaviyo hosted-page and exported-email accessibility scan recipe backed by @ariada-org/cli.

In Entwicklung

LearnDash (WordPress LMS) add-on, in Ariada channel pack 23, exposes this public implementation purpose: Production WordPress add-on. It discovers published LearnDash courses and lessons, delegates scans of their rendered URLs to the existing @ariada-org/cli executable, stores normalized findings in post meta, and surfaces summaries and full reports in LearnDash administration.

Lerna task

S230
In Entwicklung

Lerna task, in Ariada channel pack 24, exposes this public implementation purpose: Production Lerna task glue for the real Ariada accessibility CLI

In Entwicklung

Liferay portlet, in Ariada channel pack 23, exposes this public implementation purpose: Ariada for Liferay is a Liferay 7.4 MVC portlet for public-sector, university, and enterprise portal authors. It scans the current portal page with the real Ariada CLI and presents pass/fail status, the highest-severity WCAG and EN 301 549 findings, and a full JSON report link inside Liferay.

In Entwicklung

Lighthouse CI integration, in Ariada channel pack 14, exposes this public implementation purpose: Combined Lighthouse CI and Ariada accessibility gate wrapper.

In Entwicklung

Linear integration, in Ariada channel pack 17, exposes this public implementation purpose: Self-contained Linear sink for Ariada accessibility findings.

In Entwicklung

Lit dev integration, in Ariada channel pack 24, exposes this public implementation purpose: Lit shadow-DOM accessibility checks for @web/test-runner backed by the real Ariada scanner.

In Entwicklung

Litmus email-HTML a11y integration, in Ariada channel pack 22, exposes this public implementation purpose: Litmus exported-email HTML accessibility scanner backed by the real Ariada CLI and analyzer runtime.

In Entwicklung

Lunacy plugin, in Ariada channel pack 13, exposes this public implementation purpose: Lunacy plugin adapter that scans selected layers through the Ariada CLI.

In Entwicklung

Magento / Adobe Commerce module, in Ariada channel pack 4, exposes this public implementation purpose: Thin Magento 2 module scaffold for Ariada scans of category, product, cart, and checkout pages. It delegates scanning to the Ariada CLI or an explicitly configured hosted scan endpoint.

In Entwicklung

Mailchimp landing/campaign scan recipe, in Ariada channel pack 22, exposes this public implementation purpose: Mailchimp published-page and exported-email accessibility scan recipe backed by @ariada-org/cli.

In Entwicklung

MailerLite landing/email scan recipe, in Ariada channel pack 22, exposes this public implementation purpose: MailerLite published-page and exported-email accessibility scan recipe backed by the real Ariada CLI scanner.

In Entwicklung

Make (Integromat) app, in Ariada channel pack 17, exposes this public implementation purpose: Self-contained Make app definition and event mapper for Ariada reports.

In Entwicklung

Marvel integration, in Ariada channel pack 13, exposes this public implementation purpose: Thin Marvel prototype export/API adapter for the shared Ariada CLI scanner.

In Entwicklung

Maven plugin (Java), in Ariada channel pack 11, exposes this public implementation purpose: Thin Maven build-gate adapter over the shared @ariada-org/cli scanner.

In Entwicklung

MCP registry packaging for the MCP server, in Ariada channel pack 1, exposes this public implementation purpose: Model Context Protocol (MCP) server exposing the ariada OSS accessibility scanner pipeline as discoverable tools for AI coding assistants. Open source under EUPL-1.2.

In Entwicklung

mdBook preprocessor, in Ariada channel pack 12, exposes this public implementation purpose: mdBook post-build adapter and pass-through preprocessor for Ariada scans.

In Entwicklung

Medusa plugin, in Ariada channel pack 16, exposes this public implementation purpose: Thin Medusa v2 admin plugin boundary over the shared Ariada CLI.

In Entwicklung

Microsoft Edge Add-ons listing, in Ariada channel pack 9, exposes this public implementation purpose: Blocked: Microsoft Edge Add-ons submission requires Partner Center access and store review.

In Entwicklung

Microsoft Teams app, in Ariada channel pack 9, exposes this public implementation purpose: Teams app scaffold for surfacing Ariada accessibility scan results in a channel. It does not run a scanner inside Teams. CI or a user command provides Ariada CLI JSON, and this app renders that result as an Adaptive Card.

In Entwicklung

MkDocs plugin, in Ariada channel pack 10, exposes this public implementation purpose: MkDocs plugin that scans generated site HTML with the shared Ariada CLI.

MODX extra

S198
In Entwicklung

MODX extra, in Ariada channel pack 21, exposes this public implementation purpose: Ariada is a self-contained MODX Revolution Extra that displays an accessibility report for the configured public site in a Custom Manager Page (CMP). PHP does not implement or perform an accessibility scan. It either:

In Entwicklung

Monday.com app, in Ariada channel pack 17, exposes this public implementation purpose: Self-contained monday.com board item sink for Ariada accessibility findings.

In Entwicklung

Moodle plugin, in Ariada channel pack 23, exposes this public implementation purpose: A Moodle 4.5+ local plugin that queues Ariada accessibility scans for rendered course-page URLs and presents WCAG 2.2 and EN 301 549 findings to teachers and administrators. All capture and analysis is delegated to the OSS @ariada-org/cli; this plugin does not reimplement scan rules.

n8n node

S165
In Entwicklung

n8n node, in Ariada channel pack 17, exposes this public implementation purpose: n8n community nodes for routing Ariada accessibility scan reports

In Entwicklung

NativeScript plugin, in Ariada channel pack 20, exposes this public implementation purpose: Host-side Ariada CLI adapter for HTML rendered in a NativeScript WebView.

In Entwicklung

Neovim/Vim plugin, in Ariada channel pack 4, exposes this public implementation purpose: Self-contained Lua plugin that delegates accessibility scanning to the Ariada CLI and maps its JSON report to vim.diagnostic and the quickfix list. Scanner and rule logic remain in Ariada core/CLI; this integration is only an editor adapter.

In Entwicklung

Netlify build plugin, in Ariada channel pack 4, exposes this public implementation purpose: Netlify Build Plugin that scans the published site with the ariada accessibility CLI after build.

In Entwicklung

Next.js plugin / integration, in Ariada channel pack 6, exposes this public implementation purpose: Next.js integration that scans exported or built HTML with Ariada accessibility checks.

In Entwicklung

Nextra plugin, in Ariada channel pack 12, exposes this public implementation purpose: Thin Nextra docs integration that scans exported HTML with the shared Ariada CLI.

In Entwicklung

nopCommerce plugin (.NET), in Ariada channel pack 16, exposes this public implementation purpose: Self-contained nopCommerce 4.70 plugin adapter for the existing Ariada CLI. It resolves four configured storefront URLs (PDP, PLP, cart, checkout), starts the CLI as a bounded child process, parses its JSON output, and renders pass/fail, top findings, EAA / EN 301 549 tags, and report links in the nopCommerce admin. It does not contain or reimplement the

In Entwicklung

Notion integration, in Ariada channel pack 17, exposes this public implementation purpose: Self-contained Notion sink for Ariada CLI JSON. It creates one page per finding in a designated database and updates an existing page when its SHA-256 fingerprint (ruleId, page URL, selector, HTML) matches a prior scan. It never runs the scanner.

In Entwicklung

Nuxt module, in Ariada channel pack 6, exposes this public implementation purpose: Nuxt module that scans generated output with Ariada accessibility checks.

Nx plugin

S227
In Entwicklung

Nx plugin, in Ariada channel pack 24, exposes this public implementation purpose: Nx executor and generator for cacheable accessibility gates backed by the Ariada CLI.

In Entwicklung

October CMS (Laravel) plugin, in Ariada channel pack 21, exposes this public implementation purpose: Self-contained October CMS v3/v4 backend plugin for viewing accessibility results from @ariada-org/cli. It can either run the Node CLI against one configured public site URL or consume a JSON report generated by CI. PHP never crawls or audits the target itself.

In Entwicklung

Open edX XBlock/plugin, in Ariada channel pack 23, exposes this public implementation purpose: openedx-ariada is an Open edX XBlock for course authors and staff. It runs the real @ariada-org/cli@0.1.0 scanner against a rendered course or unit URL and shows impact counts, WCAG criteria, EN 301 549 references, top findings, and a staff-only full report.

In Entwicklung

OpenCart extension, in Ariada channel pack 16, exposes this public implementation purpose: Self-contained OpenCart 3.x admin module for scanning a storefront's product, category, cart, and checkout URLs with the existing @ariada-org/cli.

In Entwicklung

OpenTelemetry instrumentation, in Ariada channel pack 19, exposes this public implementation purpose: OpenTelemetry metrics and traces for existing Ariada CLI scan JSON.

In Entwicklung

pa11y-compatible adapter (drop-in for pa11y users), in Ariada channel pack 19, exposes this public implementation purpose: Pa11y-compatible CLI and report translation layer over the Ariada CLI

In Entwicklung

Package the VS Code extension for publish, in Ariada channel pack 1, exposes this public implementation purpose: Visual Studio Code extension surfacing accessibility findings inline in HTML, JSX, TSX, Vue, Svelte, and Angular templates. Open source under EUPL-1.2.

In Entwicklung

PagerDuty integration, in Ariada channel pack 19, exposes this public implementation purpose: PagerDuty Events API v2 consumer for Ariada CLI gate results

In Entwicklung

Parcel transformer/reporter, in Ariada channel pack 5, exposes this public implementation purpose: Parcel reporter adapter for Ariada build-output accessibility scans.

In Entwicklung

Payload CMS plugin, in Ariada channel pack 7, exposes this public implementation purpose: Payload CMS plugin scaffold for document preview scans. It resolves the rendered front-end URL for a document and delegates scanning to the Ariada API.

In Entwicklung

Pelican plugin, in Ariada channel pack 12, exposes this public implementation purpose: Pelican plugin that scans the generated output/ directory with the shared @ariada-org/cli after Pelican finishes writing the static site.

In Entwicklung

Penpot plugin, in Ariada channel pack 13, exposes this public implementation purpose: Penpot plugin and export adapter for Ariada accessibility evidence.

In Entwicklung

Percy integration, in Ariada channel pack 14, exposes this public implementation purpose: Percy page-list adapter for Ariada accessibility scans and combined CI gates.

In Entwicklung

PHP Composer package + Laravel integration, in Ariada channel pack 11, exposes this public implementation purpose: Composer package scaffold for running Ariada accessibility scans from Laravel release workflows.

In Entwicklung

Plasmic plugin, in Ariada channel pack 15, exposes this public implementation purpose: Thin Plasmic code-component adapter for Ariada accessibility scans.

In Entwicklung

Playwright reporter/fixture, in Ariada channel pack 14, exposes this public implementation purpose: Playwright fixture, matcher, and reporter for Ariada accessibility scans.

In Entwicklung

Plone (Python) add-on, in Ariada channel pack 21, exposes this public implementation purpose: ariada.plone is a Plone 6 add-on that lets a site manager run an Ariada accessibility scan for a configured public site URL or display a previously generated Ariada CI report. Python does not implement accessibility scanning; it invokes the ariada binary provided by @ariada-org/cli or reads its scan.json artifact.

In Entwicklung

PostCSS plugin, in Ariada channel pack 5, exposes this public implementation purpose: PostCSS 8 plugin adapter for Ariada CSS-domain accessibility checks.

In Entwicklung

pre-commit / git-hook integration, in Ariada channel pack 2, exposes this public implementation purpose: pre-commit and Husky wrapper for running ariada accessibility gates on staged HTML and template files.

In Entwicklung

pre-commit.ci, in Ariada channel pack 8, exposes this public implementation purpose: pre-commit.ci activation requires installing the GitHub App on a repository. That is a founder/listing step.

In Entwicklung

PrestaShop module, in Ariada channel pack 4, exposes this public implementation purpose: Production-oriented PrestaShop 1.7/8 module shell for EAA storefront scans. It adds an Ariada EAA admin tab, validates a storefront URL, and delegates to a locally installed Ariada CLI. The module never accepts or stores store credentials and does not call a hosted service.

In Entwicklung

ProcessWire module, in Ariada channel pack 21, exposes this public implementation purpose: ProcessAriada is a self-contained ProcessWire 3 admin Process module for S202. It displays an Ariada accessibility gate result for one configured site URL. It either:

In Entwicklung

Prometheus exporter (a11y metrics), in Ariada channel pack 19, exposes this public implementation purpose: A self-contained TypeScript consumer for one Ariada CLI JSON scan document. It validates the document, replaces the current in-memory scan snapshot, exposes Prometheus text exposition at GET /metrics, and can optionally push the same registry to a Pushgateway.

In Entwicklung

ProtoPie plugin, in Ariada channel pack 13, exposes this public implementation purpose: Thin ProtoPie Cloud/Player host adapter for the shared Ariada CLI scanner.

In Entwicklung

Pulumi component, in Ariada channel pack 18, exposes this public implementation purpose: Pulumi TypeScript component for running Ariada accessibility scans

In Entwicklung

PWA manifest + service-worker a11y audit, in Ariada channel pack 20, exposes this public implementation purpose: Production-oriented PWA manifest and Ariada DOM audit wrapper

In Entwicklung

pytest plugin, in Ariada channel pack 10, exposes this public implementation purpose: pytest plugin for running Ariada accessibility scans inside a Python test suite.

In Entwicklung

Quasar integration, in Ariada channel pack 20, exposes this public implementation purpose: Production-oriented Quasar web-output wrapper for @ariada-org/cli.

In Entwicklung

Qwik integration, in Ariada channel pack 6, exposes this public implementation purpose: Qwik City Vite plugin wrapper that scans generated output with Ariada.

In Entwicklung

Railway integration, in Ariada channel pack 18, exposes this public implementation purpose: Thin Railway gate and report-only wrapper for @ariada-org/cli.

In Entwicklung

RapidAPI listing (scan-as-an-API), in Ariada channel pack 3, exposes this public implementation purpose: RapidAPI listing scaffold for the Ariada hosted accessibility scan API.

In Entwicklung

Raycast extension, in Ariada channel pack 9, exposes this public implementation purpose: Raycast extension scaffold for running the Ariada CLI from macOS launcher commands and showing scan results in a list-friendly shape.

In Entwicklung

React Native Web integration, in Ariada channel pack 20, exposes this public implementation purpose: A production-oriented, thin integration over @ariada-org/cli@0.1.0 for the browser output of React Native Web applications. It accepts either an already served HTTP(S) URL or a built web output directory. A directory is exposed on an ephemeral 127.0.0.1 port only while Ariada scans it.

In Entwicklung

Read the Docs build integration, in Ariada channel pack 8, exposes this public implementation purpose: This stream adds a Read the Docs build.jobs.postbuild wrapper that runs Ariada after documentation HTML is generated. The wrapper is a thin @ariada-org/cli launcher and does not implement scan logic.

In Entwicklung

Remix / React-Router integration, in Ariada channel pack 6, exposes this public implementation purpose: Remix and React Router framework Vite plugin wrapper for Ariada scans.

In Entwicklung

Render integration, in Ariada channel pack 18, exposes this public implementation purpose: A production-oriented Render adapter around @ariada-org/cli@0.1.0. This package is orchestration only: it resolves a target, invokes the published Ariada executable across an injected subprocess boundary, parses Ariada's JSON, and maps Ariada's result to a Render deploy outcome. It never implements scan rules, severity decisions, browser analysis, or

In Entwicklung

Rollup plugin, in Ariada channel pack 5, exposes this public implementation purpose: Rollup plugin that scans emitted HTML with Ariada accessibility checks.

In Entwicklung

Ruby gem + Rails engine, in Ariada channel pack 11, exposes this public implementation purpose: Ruby gem and Rails Railtie for running Ariada accessibility scans from Ruby projects. The adapter provides:

In Entwicklung

Rush plugin, in Ariada channel pack 24, exposes this public implementation purpose: Rush custom command integration for the real Ariada accessibility scanner

In Entwicklung

Rust crate (cargo), in Ariada channel pack 11, exposes this public implementation purpose: The crate is deliberately thin. It shells out to the shared @ariada-org/cli, reads multi-domain-report.json, prints a Cargo-friendly summary, and returns a CI exit code:

In Entwicklung

Safari Web Extension, in Ariada channel pack 3, exposes this public implementation purpose: - macOS with Xcode command line tools - xcrun safari-web-extension-converter - Node.js and pnpm versions accepted by the monorepo

Saleor app

S150
In Entwicklung

Saleor app, in Ariada channel pack 16, exposes this public implementation purpose: Saleor App adapter that delegates storefront accessibility scans to the Ariada CLI.

In Entwicklung

Salesforce Commerce Cloud cartridge, in Ariada channel pack 16, exposes this public implementation purpose: Copy sfcc-ariada.config.example.json to sfcc-ariada.config.json, use real storefront URLs only in a private environment, install the shared CLI, then run:

In Entwicklung

Sanity studio tool/plugin, in Ariada channel pack 7, exposes this public implementation purpose: Sanity Studio plugin scaffold for scanning rendered Presentation/preview URLs. The Studio plugin owns editor wiring only; Ariada owns the scan.

In Entwicklung

Sauce Labs integration, in Ariada channel pack 14, exposes this public implementation purpose: Thin Sauce Labs session/CDP adapter for deterministic Ariada scan artifacts and CI gates.

In Entwicklung

Selenium integration, in Ariada channel pack 14, exposes this public implementation purpose: CDP-first Ariada accessibility scans for Selenium WebDriver JavaScript sessions.

In Entwicklung

Sentry integration, in Ariada channel pack 19, exposes this public implementation purpose: Deterministic Sentry reporting for Ariada CLI accessibility regressions

In Entwicklung

SharePoint integration, in Ariada channel pack 23, exposes this public implementation purpose: SharePoint Framework web part and packed Ariada scanner service for Microsoft 365

In Entwicklung

Shopware plugin, in Ariada channel pack 16, exposes this public implementation purpose: This is a thin Shopware 6 Administration adapter over the existing @ariada-org CLI. It resolves four merchant storefront entry points, delegates scanning to the CLI, and renders normalized pass/fail results in Administration. It does not implement accessibility rules or a second scanner.

In Entwicklung

SilverStripe module, in Ariada channel pack 21, exposes this public implementation purpose: S204 provides a Composer vendor module that displays validated Ariada accessibility results in SilverStripe CMS and, when explicitly enabled, at /accessibility/ariada.

In Entwicklung

Sitecore integration, in Ariada channel pack 23, exposes this public implementation purpose: Production-native Sitecore XM/XP authoring integration for Ariada accessibility scans.

In Entwicklung

Sketch plugin, in Ariada channel pack 2, exposes this public implementation purpose: Sketch plugin for local design-time accessibility checks on selected layers.

In Entwicklung

Slack app (gate/scan notifications), in Ariada channel pack 3, exposes this public implementation purpose: Slack app scaffold for Ariada accessibility scan requests and CI gate failure notifications. The local package is a thin adapter over Ariada hosted scan or CLI semantics; it does not fork scanner rules or run a separate scanner inside Slack.

In Entwicklung

Softr integration, in Ariada channel pack 15, exposes this public implementation purpose: Thin Softr published/authenticated-page adapter over @ariada-org/cli.

In Entwicklung

SolidStart integration, in Ariada channel pack 6, exposes this public implementation purpose: SolidStart Vite plugin wrapper that scans generated output with Ariada.

In Entwicklung

Sphinx extension, in Ariada channel pack 10, exposes this public implementation purpose: Sphinx extension that scans generated HTML documentation with the shared Ariada CLI.

In Entwicklung

Spree extension (Ruby), in Ariada channel pack 16, exposes this public implementation purpose: spreeariada is a thin Spree/Rails engine. It adds an admin scan page for product-detail (PDP), product-listing (PLP), cart, and checkout URLs, then delegates every scan to the shared @ariada-org/cli. It does not reimplement scanner rules, infer EAA coverage, or call Spree APIs.

In Entwicklung

Squarespace extension, in Ariada channel pack 2, exposes this public implementation purpose: Thin Squarespace extension scaffold for sending a published Squarespace site URL to the Ariada hosted scan API and rendering evidence back in an extension-style settings/results page.

In Entwicklung

standalone Lighthouse plugin, in Ariada channel pack 19, exposes this public implementation purpose: Lighthouse plugin that adapts Ariada accessibility scan output into scored Lighthouse audits.

In Entwicklung

Statamic addon, in Ariada channel pack 7, exposes this public implementation purpose: Statamic addon scaffold for scanning rendered entry URLs through the Ariada CLI or hosted API.

In Entwicklung

Statuspage / status-board integration, in Ariada channel pack 19, exposes this public implementation purpose: Dry-run-first Atlassian Statuspage adapter for Ariada CLI JSON results

In Entwicklung

Stencil output target, in Ariada channel pack 24, exposes this public implementation purpose: Stencil custom output target for real Ariada accessibility scans of rendered shadow-DOM components.

In Entwicklung

Storybook addon, in Ariada channel pack 3, exposes this public implementation purpose: Storybook addon that runs Ariada accessibility checks on rendered stories and reports findings in a panel.

In Entwicklung

Strapi plugin, in Ariada channel pack 7, exposes this public implementation purpose: Strapi plugin scaffold for entry-level rendered URL scans. The admin action and server route should pass a published front-end URL to Ariada; this package keeps that contract isolated and testable.

In Entwicklung

Streamlit component, in Ariada channel pack 10, exposes this public implementation purpose: Streamlit helper package that scans a running Streamlit app URL with the shared Ariada CLI.

In Entwicklung

Sublime Text package, in Ariada channel pack 4, exposes this public implementation purpose: Sublime Text package that runs the ariada accessibility CLI from the editor and shows the result in an output panel.

In Entwicklung

Substack publication/post scan recipe, in Ariada channel pack 22, exposes this public implementation purpose: Recipe-only Substack publication and post accessibility scans powered by the Ariada CLI

In Entwicklung

Super.so (Notion-site) integration, in Ariada channel pack 15, exposes this public implementation purpose: Thin published-URL adapter over @ariada-org/cli for sites rendered by Super.so from Notion pages. It does not implement scanning or call a Super.so API.

In Entwicklung

SvelteKit integration, in Ariada channel pack 6, exposes this public implementation purpose: SvelteKit Vite plugin wrapper that scans build output with Ariada.

In Entwicklung

SWC plugin/wrapper, in Ariada channel pack 5, exposes this public implementation purpose: JavaScript-side SWC pipeline wrapper for Ariada static JSX accessibility checks.

In Entwicklung

Swell integration, in Ariada channel pack 16, exposes this public implementation purpose: Thin Swell storefront integration over the shared @ariada-org/cli. Swell is a headless backend, so this adapter scans the connected frontend URL; it does not implement scanning rules or call Swell from the CLI.

In Entwicklung

Symfony bundle (PHP), in Ariada channel pack 11, exposes this public implementation purpose: Symfony bundle for running Ariada accessibility scans from bin/console. The bundle adds an ariada:scan {url?} command, reads defaults from Symfony configuration, and delegates scanning to the shared @ariada-org/cli.

In Entwicklung

Tauri integration, in Ariada channel pack 20, exposes this public implementation purpose: A production-oriented Tauri web-frontend wrapper for @ariada-org/cli.

In Entwicklung

Terraform provider, in Ariada channel pack 18, exposes this public implementation purpose: A thin Terraform Plugin Framework provider that runs the installed @ariada-org/cli executable. It does not implement browser capture, WCAG rules, finding classification, scoring, or pass/fail policy.

In Entwicklung

TestCafe plugin, in Ariada channel pack 14, exposes this public implementation purpose: Thin TestCafe integration for running an Ariada scan against the current page.

In Entwicklung

Tilda integration, in Ariada channel pack 15, exposes this public implementation purpose: Production thin adapter over @ariada-org/cli for a Tilda published page. It invokes the existing Ariada Playwright scan with --browser chromium and --domains accessibility; this is the CLI's rendered-page boundary, suitable for Tilda's zero-block and lazy-loaded sections. The adapter only maps the CLI JSON result and applies the severity gate. It does not

In Entwicklung

tox / nox integration, in Ariada channel pack 10, exposes this public implementation purpose: Thin Python helper for running Ariada accessibility scans from tox or nox.

In Entwicklung

Trello Power-Up, in Ariada channel pack 17, exposes this public implementation purpose: Self-contained S160 thin integration. It maps Ariada report findings to one Trello card per fingerprint, adds a severity label, and links the report. Existing cards are deduplicated by an Ariada fingerprint marker in the description.

In Entwicklung

Turbopack/Next loader integration, in Ariada channel pack 5, exposes this public implementation purpose: Turbopack does not expose a stable third-party plugin API for whole-output scanning. This integration ships the reachable path today: run Ariada as a post-build step over .next or static exported HTML.

In Entwicklung

Turborepo integration, in Ariada channel pack 24, exposes this public implementation purpose: Cache-aware Turborepo task wrapper for the real Ariada accessibility scanner.

In Entwicklung

Typedream integration, in Ariada channel pack 15, exposes this public implementation purpose: Thin typed adapter over @ariada-org/cli for a caller-supplied Typedream published URL. It does not reimplement scanning, call a Typedream API, or handle credentials.

In Entwicklung

TYPO3 extension, in Ariada channel pack 2, exposes this public implementation purpose: TYPO3 12/13 extension that exposes Ariada accessibility scans in two places:

In Entwicklung

Umbraco package (.NET), in Ariada channel pack 7, exposes this public implementation purpose: Umbraco 13+ package scaffold for back-office rendered page scans. It keeps the .NET package outside the pnpm workspace and delegates scanning to Ariada.

In Entwicklung

UXPin integration, in Ariada channel pack 13, exposes this public implementation purpose: Thin UXPin HTML export adapter for the shared Ariada CLI scanner.

In Entwicklung

Vercel Marketplace integration, in Ariada channel pack 8, exposes this public implementation purpose: This package is the marketplace-grade Vercel integration stream. It is distinct from earlier Vercel application packages: it models a Vercel Checks integration that receives deployment.ready, calls the hosted Ariada scan surface, and posts a deployment check payload.

In Entwicklung

Vite plugin, in Ariada channel pack 3, exposes this public implementation purpose: Vite plugin that scans dev HTML and production build output with Ariada accessibility checks.

In Entwicklung

VitePress plugin, in Ariada channel pack 12, exposes this public implementation purpose: VitePress build hook that scans rendered docs output with the shared Ariada CLI.

In Entwicklung

VuePress plugin, in Ariada channel pack 12, exposes this public implementation purpose: VuePress plugin that scans generated documentation output with the shared Ariada CLI.

In Entwicklung

WebdriverIO service, in Ariada channel pack 14, exposes this public implementation purpose: WebdriverIO service for Ariada accessibility scans and policy reporting.

In Entwicklung

Webflow app, in Ariada channel pack 2, exposes this public implementation purpose: Thin Webflow Designer/Data app adapter for Ariada hosted scan semantics. The adapter prepares Webflow OAuth and page scan requests, normalizes Ariada findings for a Designer panel, and includes a local fixture that represents the panel while the real Webflow app account and marketplace review are unavailable.

In Entwicklung

Webpack plugin, in Ariada channel pack 5, exposes this public implementation purpose: Webpack plugin that scans emitted HTML with Ariada accessibility checks.

In Entwicklung

Webstudio integration, in Ariada channel pack 15, exposes this public implementation purpose: This is a production thin integration over @ariada-org/cli for a Webstudio static export. It is intentionally local and deterministic: the adapter finds exported .html pages, sorts them by relative path, invokes one Ariada CLI scan, and maps the JSON output to a severity gate. It does not contain scanner rules.

In Entwicklung

Whimsical integration, in Ariada channel pack 13, exposes this public implementation purpose: Thin export-then-scan recipe for Whimsical boards. Whimsical does not provide a first-party plugin SDK, so this package contains Node glue for exported board artifacts instead of in-product code.

In Entwicklung

winget + Scoop manifests, in Ariada channel pack 4, exposes this public implementation purpose: Release-gated templates and validation tooling for installing the Ariada CLI through Windows Package Manager (winget) and Scoop.

Wix app

S10
In Entwicklung

Wix app, in Ariada channel pack 2, exposes this public implementation purpose: Local Wix dashboard fixture for Ariada hosted scan integration.

In Entwicklung

WooCommerce extension is Ariada's browser review surface in channel pack 3. It gives reviewers a named surface for running accessibility checks and evaluating evidence in the workflow represented by WooCommerce extension.

In Entwicklung

WordPress.org core plugin (general site-scan), in Ariada channel pack 7, exposes this public implementation purpose: General WordPress site-scan plugin for administrators who need to check rendered pages and posts for WCAG/EAA issues. It is intentionally separate from the WooCommerce channel.

Zapier app

S163
In Entwicklung

Zapier app, in Ariada channel pack 17, exposes this public implementation purpose: Self-contained Zapier Platform CLI integration for Ariada reports.

In Entwicklung

Zed editor extension, in Ariada channel pack 3, exposes this public implementation purpose: Zed extension scaffold for surfacing Ariada accessibility findings as editor diagnostics.

In Entwicklung

Zeplin extension, in Ariada channel pack 13, exposes this public implementation purpose: Live Zeplin registry submission is blocked here. Publishing requires a Zeplin account/workspace and either interactive zem publish review or a ZEMACCESSTOKEN configured by the founder. The closest available host surface is the recorded export fixture in tests/fixtures/zeplin-export.json.

In Entwicklung

Zola integration is Ariada's workflow integration in channel pack 12. It gives reviewers a named surface for running accessibility checks and evaluating evidence in the workflow represented by Zola integration.