Skip to main content

Integrations

Every tool in your workflow. Connected.

The audit trifecta: validate at design time in Figma, at code time in your editor, and at runtime in the browser. All feeding back into a single platform.

The audit trifecta.

Three stages of validation — design, code, and production — backed by the same contract.

1
figma

Design time

Figma plugin

Audit accessibility and validate contracts while you design. Catch WCAG issues before a Jira ticket is written.

2
vs-codecursor

Code time

VS Code extension + MCP server

Query contracts from your editor. Let AI assistants read your design specs directly. No more guessing what the designer meant.

3

Production

Browser extension

Audit live websites against your contracts. Catch divergences between design spec and what users actually see.

Figma plugin

figma

Validate contracts while you design.

The Figma plugin connects your design files to your Parlance contracts. Run accessibility audits, check WCAG compliance, and push design tokens — all without leaving Figma.

  • WCAG 2.2 contrast checking
  • Push design tokens to glossary
  • View contract status per component
  • Accessibility annotations
  • Works standalone — no account required for basic auditing

Figma plugin

Available in the Figma Community

Coming soon

VS Code · Cursor

vs-codecursor

Design specs, right in your editor.

The VS Code and Cursor extension brings your Parlance contracts directly into the editor. Query component specs, look up glossary terms, and validate your implementation — without switching context.

  • Inline contract view per component
  • Glossary term autocomplete
  • Validate implementation against spec
  • Quick-access token translations
  • Linked directly to your Parlance project
button.tsx

import { Button } from './button'

// 💡 Contract: Button (agreed)

// WCAG AA ✓ · focus-visible ✓

// variants: primary | secondary | ghost

MCP server

mcp-serverclaude-ai

Ask your AI assistant about your design specs.

The Parlance MCP server exposes your contracts to AI assistants via the Model Context Protocol. Ask natural language questions about your component specs, and get answers grounded in your actual contracts.

Works with:

Claude CodeCursorGitHub CopilotWindsurfCline

💬 Natural language queries

“What are the accessibility requirements for the Button component?”

Button requires WCAG AA contrast, visible focus indicator, and role="button". Touch target minimum 44×44px.

Browser extension

Coming soon

Audit live sites in Chrome and Safari.

The browser extension will bring contract validation to production. Overlay your component contracts on live sites, flag divergences from the agreed spec, and run WCAG checks without leaving the browser.

  • Overlay contracts on live components
  • Real-time WCAG compliance checking
  • Flag divergences from agreed spec
  • Export audit results to Parlance
  • Available for Chrome and Safari

Browser extension

Chrome + Safari · In development

We're building this now. Sign up to be notified when it launches.

Connect your entire workflow.

Parlance connects with the tools your team already uses.

githubgitlab

GitHub · GitLab

Available

Sync contracts with your repository. Auto-generate PR descriptions from contract changes. Flag divergent components in pull requests.

slack

Slack

Available

Route notifications to your team channels. Get alerts when contracts become divergent, when audits complete, or when a new contract is proposed.

jiralinear

Jira · Linear

Team+

Automatically create tickets from audit failures. Link contracts to existing issues. Track compliance work alongside product work.

Start free. Connect everything.

The Figma plugin and VS Code extension work standalone — no account required for basic WCAG auditing.

Create a free account to connect integrations, sync contracts, and share with your team.

Get started free