Skip to Content
Accessibility

Accessibility Conformance Report

Based on VPAT® Version 2.4

Product: Marka Email Generator (Figma Plugin) Version: Latest Report Date: May 2026 Description: Marka Email Generator is a Figma plugin that enables designers to build and export HTML emails directly to email service providers including Klaviyo, Mailchimp, and HubSpot. The plugin UI runs within Figma’s plugin panel environment.


Scope

This report covers the Marka Email Generator plugin UI, including its main panel, modals, tooltips, form inputs, and error states. It does not cover the Figma application itself, which has its own accessibility documentation published by Figma, Inc.


Applicable Standards

This report addresses conformance with the following standards:

  • WCAG 2.1 Level A and Level AA (Web Content Accessibility Guidelines)
  • Section 508 of the Rehabilitation Act (US)

WCAG 2.1 Conformance

Principle 1 – Perceivable

CriteriaConformance LevelRemarks
1.1.1 Non-text Content (A)SupportsInteractive controls include accessible labels. Icon-only buttons include descriptive title attributes.
1.2.x Time-based Media (A/AA)Not ApplicableNo audio or video content.
1.3.1 Info and Relationships (A)SupportsForm inputs are associated with labels. Error messages are associated with their respective fields via ARIA attributes.
1.3.2 Meaningful Sequence (A)SupportsContent is structured in a logical reading order.
1.3.3 Sensory Characteristics (A)SupportsInstructions do not rely solely on shape, color, or position.
1.3.4 Orientation (AA)Not ApplicablePlugin panel does not reorient based on device orientation.
1.3.5 Identify Input Purpose (AA)SupportsStandard input fields (email, text) use appropriate type attributes.
1.4.1 Use of Color (A)SupportsColor is not used as the sole means of conveying information. Error states include both color change and descriptive text.
1.4.2 Audio Control (A)Not ApplicableNo audio content.
1.4.3 Contrast (Minimum) (AA)SupportsThe plugin uses Figma’s injected CSS color variables, which are designed to meet contrast requirements across Figma’s light and dark themes.
1.4.4 Resize Text (AA)Partially SupportsText scales with Figma’s UI zoom. Some tooltip content may not scale at all zoom levels.
1.4.5 Images of Text (AA)SupportsNo images of text are used.
1.4.10 Reflow (AA)Partially SupportsThe plugin panel has a fixed minimum width as required by Figma’s plugin architecture. Content reflow within that width is supported.
1.4.11 Non-text Contrast (AA)SupportsUI components use Figma CSS variables with sufficient contrast for component boundaries and focus indicators.
1.4.12 Text Spacing (AA)SupportsNo CSS overrides prevent user-defined text spacing adjustments.
1.4.13 Content on Hover or Focus (AA)Partially SupportsTooltips appear on hover and are dismissable. Tooltip content persists while hovered. Some tooltips may not persist long enough for slow readers.

Principle 2 – Operable

CriteriaConformance LevelRemarks
2.1.1 Keyboard (A)SupportsAll interactive elements are keyboard accessible. Modals trap focus appropriately while open.
2.1.2 No Keyboard Trap (A)SupportsFocus is released from modals upon close. No keyboard traps present.
2.1.4 Character Key Shortcuts (A)Not ApplicableNo single-character keyboard shortcuts are implemented.
2.2.x Timing (A/AA)Not ApplicableNo time-limited sessions or auto-updating content.
2.3.x Seizures (A/AAA)SupportsNo flashing content. Modal and tooltip animations are subtle fades and do not exceed flash thresholds.
2.4.1 Bypass Blocks (A)Not ApplicablePlugin panel is a single-page UI without repeated navigation blocks.
2.4.2 Page Titled (A)SupportsThe plugin is clearly labeled “Marka Email Generator” in the Figma plugin panel header.
2.4.3 Focus Order (A)SupportsFocus order follows a logical top-to-bottom, left-to-right sequence. Modal focus is managed on open and close.
2.4.4 Link Purpose (A)SupportsAll links and buttons have descriptive labels.
2.4.6 Headings and Labels (AA)SupportsSections use appropriate heading hierarchy. Form labels are descriptive.
2.4.7 Focus Visible (AA)SupportsFocus indicators are visible using Figma’s native focus ring styles.
2.5.1 Pointer Gestures (A)Not ApplicableNo multi-point or path-based gestures.
2.5.2 Pointer Cancellation (A)SupportsActions are triggered on mouseup/click, not mousedown.
2.5.3 Label in Name (A)SupportsAccessible names match or include the visible label text.
2.5.4 Motion Actuation (A)Not ApplicableNo motion-based interaction.

Principle 3 – Understandable

CriteriaConformance LevelRemarks
3.1.1 Language of Page (A)SupportsPlugin UI language is English.
3.1.2 Language of Parts (AA)Not ApplicableNo multi-language content within the plugin.
3.2.1 On Focus (A)SupportsNo context changes occur on focus alone.
3.2.2 On Input (A)SupportsNo unexpected context changes occur on input.
3.2.3 Consistent Navigation (AA)SupportsNavigation and UI patterns are consistent across plugin views.
3.2.4 Consistent Identification (AA)SupportsComponents with the same function are identified consistently.
3.3.1 Error Identification (A)SupportsInput errors are identified with descriptive text messages adjacent to the affected field.
3.3.2 Labels or Instructions (A)SupportsAll form fields include visible labels and placeholder guidance where appropriate.
3.3.3 Error Suggestion (AA)SupportsError messages describe the issue and suggest corrective action where applicable.
3.3.4 Error Prevention (AA)Partially SupportsDestructive actions (e.g., removing configurations) prompt for confirmation. Not all irreversible actions include a review step.

Principle 4 – Robust

CriteriaConformance LevelRemarks
4.1.1 Parsing (A)SupportsPlugin UI is rendered within Figma’s webview environment. HTML output is generated for email clients, not for assistive technologies.
4.1.2 Name, Role, Value (A)SupportsInteractive UI components include appropriate ARIA roles, labels, and states. Custom controls communicate state changes.
4.1.3 Status Messages (AA)Partially SupportsSome status messages (e.g., export success, connection status) are displayed visually. Not all status messages are announced via ARIA live regions.

Section 508 Conformance

The Section 508 standards largely reference WCAG 2.0 Level A and AA criteria. Conformance levels are consistent with the WCAG 2.1 table above. The plugin does not include hardware, documentation provided as closed captions, or two-way voice communication, so those criteria are not applicable.


Notes

  • The plugin operates within Figma’s plugin sandbox (a webview). Accessibility of the Figma shell, canvas, and surrounding application is the responsibility of Figma, Inc.
  • This report is a voluntary self-assessment and has not been independently audited.

Conformance Level Key

LevelDefinition
SupportsThe functionality of the product meets the criterion without exception.
Partially SupportsSome functionality of the product does not meet the criterion.
Does Not SupportThe majority of product functionality does not meet the criterion.
Not ApplicableThe criterion is not relevant to this product.
Not EvaluatedThe product has not been evaluated against this criterion.
Last updated on