Deque

dequelabs/axe-accessibility·1 plugin

Let your coding agent analyze UI for WCAG issues, remediate in the loop, and verify fixes via Deque’s axe-powered MCP workflow.

Overview

deque is a plugin marketplace for the Ship phase that adds Deque’s axe-accessibility toolkit so agents analyze, remediate, and verify WCAG-related UI issues over MCP.

What is this marketplace?

Deque axe accessibility plugin for coding agents (v0.1.0)
MCP workflow: analyze → remediate → verify in the agent loop
WCAG-oriented accessibility testing without treating a11y as a separate manual chore
Powered by axe MCP Server patterns with room for expanded Deque plugins over time
Keywords span accessibility, a11y, wcag, remediation, and mcp
Marketplace lists 1 plugin (axe-accessibility v0.1.0)
Documented MCP workflow steps: analyze, remediate, verify

Compatible agents: Claude Code, Cursor, Codex, any compatible agent

What problem does it solve?

Shipping accessible UI often becomes a late manual audit that coding agents skip unless accessibility is wired into their daily build-and-fix loop.

Who is it for?

Solo builders shipping customer-facing web apps or marketing sites who use Claude Code with MCP and need continuous WCAG-oriented feedback.

Skip if: Backend-only APIs, native mobile stacks without the supported axe MCP UI path, or teams that want a one-time PDF audit with no agent integration.

What do I get? / Deliverables

After you register the marketplace plugin, your agent can run axe-driven analyze-remediate-verify cycles on UI changes before you ship.

Installed axe-accessibility plugin from the deque marketplace
Repeatable analyze → remediate → verify accessibility runs in agent sessions
Reduced manual a11y audit churn before ship

Plugins in this marketplace

1 plugin — install individually after you add the marketplace.

PluginVersion

Axe AccessibilityDeque's accessibility toolkit for coding agents. Get accessible UI effortlessly - your agent builds, tests, and remediates accessibility in the loop, so it's never a separate, manual chore. Currently powers the axe MCP Server analyze -> remediate -> verify workflow; expanding over time.0.1.0

Recommended Marketplaces

AccesslintAccessLint/skills

accesslint is an AccessLint plugin marketplace that ships one plugin pairing WCAG 2.2 discovery with agent-driven remedi…54 stars

Agentic Pluginsjustjoheinz/agentic-plugins

agentic-plugins is a small Claude Code marketplace by justjoheinz with two complementary build-time plugins. ramsify gui…

Ai Design Componentsancoleman/ai-design-components

ai-design-components is a large Claude marketplace curated by Anton Coleman (Palo Alto Networks affiliation in metadata)…372 stars

Balkan Family Tree MarketplaceViaScopi/balkan-family-tree-plugin

The ViaScopi balkan-family-tree marketplace delivers one development plugin that teaches Claude Code how to work with Ba…

Bmad Dux Visual ArchitectYash-1511/bmad-dux-visual-architect

bmad-dux-visual-architect is a MIT-licensed Claude Code marketplace built around the dux plugin, a visual architecture s…1 stars

Cc Frontend Skillsoikon48/cc-frontend-skills

cc-frontend-skills is a one-plugin Claude marketplace curated by oikon48 for solo builders who want their agent to stop …68 stars

Journey fit

Primary fit

Deque positions the toolkit for build-test-remediate-verify in the shipping path, so Ship is the canonical shelf even when you run checks during implementation. Accessibility remediation is treated as ongoing review and verification of UI quality, aligned with code review rather than pure load testing.

How it compares

Deque axe MCP accessibility loop, not a multi-agent research or team-swarm orchestration marketplace.

Common Questions / FAQ

Who is Deque for?

Frontend-leaning solo builders and small teams who want Deque’s axe tooling inside Claude Code agents while they ship UI.

When should I use Deque?

Use it during implementation and pre-launch review whenever you change components, forms, or flows that must meet accessibility expectations.

How do I add Deque to my agent?

Add the Deque marketplace to Claude Code, enable the axe-accessibility plugin, connect the axe MCP Server per Deque’s setup, then run analyze → remediate → verify from your agent session.