Skip to content
A11y Audit — WCAG 2.2

FAQ

What’s the difference from Stark?

Section titled “What’s the difference from Stark?”

Stark is a comprehensive accessibility tool for designers with many features (annotations, color blindness simulation tests, accessible component library). It’s an excellent tool, but its price ($99/month in 2025 for the solo plan, $299/month for teams) is difficult to justify for agencies or freelancers who don’t specialize in accessibility.

A11y Audit focuses on WCAG 2.2 auditing and PDF report generation at an accessible price. If you need Stark’s advanced features (annotations, component library), Stark remains a better option. If you primarily want to detect violations and produce a report for your client, A11y Audit is more suitable.

Does the tool certify EAA compliance?

Section titled “Does the tool certify EAA compliance?”

No. A11y Audit is an audit aid tool. It does not issue certifications and does not guarantee compliance with the EAA (European Accessibility Act).

What the plugin does: it automatically checks WCAG 2.2 AA criteria measurable in Figma (contrast, sizes, structure). What the plugin does not do:

  • It does not audit the HTML/CSS code of your final application
  • It does not test accessibility with screen readers (NVDA, VoiceOver, JAWS)
  • It does not check criteria requiring real interaction (keyboard navigation, focus management, ARIA)
  • It does not replace the expertise of a human accessibility auditor

EAA compliance requires a complete audit of the developed application, not just the mockup. The PDF report explicitly states which criteria are covered and which require manual verification.

Does my Figma file data leave Figma?

Section titled “Does my Figma file data leave Figma?”

No. The plugin runs 100% inside Figma’s browser environment. All analyses are performed locally, within the Figma plugin context.

  • No mockup data is sent to our servers
  • The PDF report is generated locally and downloaded directly to your browser
  • The only data transmitted to our servers is license management data (email, license identifier) to validate your subscription

You can verify this in airplane mode: the plugin continues to work for audits (only license validation requires an occasional connection).

WCAG 2.2 vs EAA vs EN 301 549 — what are the differences?

Section titled “WCAG 2.2 vs EAA vs EN 301 549 — what are the differences?”

These three standards are related but distinct:

WCAG 2.2 (Web Content Accessibility Guidelines) is the international technical standard published by the W3C. It defines success criteria organized into 3 levels (A, AA, AAA). Version 2.2 introduced new criteria in 2023, particularly for mobile interfaces (criteria 2.5.7 and 2.5.8).

EAA (European Accessibility Act, Directive 2019/882/EU) is a European directive that imposes legal accessibility obligations on certain sectors (banking services, e-commerce, transport, media, telecommunications, etc.). It relies on the EN 301 549 standard, which is itself based on WCAG 2.1 AA (with some adaptations). Since June 2025, it applies to companies selling digital services in Europe.

In practice for your projects: target WCAG 2.2 AA. This covers EAA requirements for the vast majority of criteria.

What should I do with “criteria requiring manual verification”?

Section titled “What should I do with “criteria requiring manual verification”?”

The PDF report includes a checklist of criteria that cannot be automatically verified in Figma. These criteria require:

  1. Manual review by a designer: verify logical reading order, navigation consistency, relevance of alternative texts
  2. Testing on the developed application: keyboard navigation, screen readers, resizing, real-world contrast
  3. An accessibility expert for projects subject to strict legal obligations

If your client is subject to EAA obligations, recommend a complete audit by a certified organization after launch.

Support for bugs

Section titled “Support for bugs”

If you encounter a bug or unexpected behavior:

  1. Close and reopen the plugin (most issues resolve this way)
  2. Check that Figma is up to date (Help → Check for updates)
  3. If the issue persists, send an email to [email protected] specifying:
    • The version of Figma you’re using
    • Your operating system (macOS / Windows)
    • A description of the issue and, if possible, a screenshot

Pro and Team users receive priority support (response within 24 business hours). Free users are handled within 72 business hours.

Is the plugin compatible with FigJam and Penpot?

Section titled “Is the plugin compatible with FigJam and Penpot?”

No. A11y Audit works only in Figma Design (.fig files). It is not compatible with:

  • FigJam: FigJam files are collaborative whiteboards, not design mockups, and don’t have the properties needed for auditing (text styles, measurable backgrounds, layer hierarchy)
  • Penpot: Penpot is a different open-source tool from Figma. A Penpot version is under consideration but not yet available

How do I cancel my subscription?

Section titled “How do I cancel my subscription?”

You can cancel at any time from your LemonSqueezy customer portal:

  1. Check your subscription confirmation email — it contains a link to your customer portal
  2. In the portal, click “Manage subscription” → “Cancel”
  3. Cancellation takes effect at the end of the current period (monthly or annual)
  4. You retain access to Pro features until the end of the paid period

If you have trouble, write to [email protected] and we’ll handle the cancellation manually.