Accessibility Statement

Last updated: February 2026

Our Commitment

Fantastic Forms is committed to ensuring that our service is accessible to people with disabilities. We believe everyone deserves equal access to the tools they use to communicate, collect information, and run their business — and we treat accessibility as an ongoing engineering responsibility, not a one-time task.

Standards We Work Toward

Our published forms — the surface that respondents actually fill out — are built with the following standards in mind:

  • WCAG 2.1 Level AA — Web Content Accessibility Guidelines published by the W3C.
  • Section 508 — U.S. federal accessibility requirements (references WCAG 2.0 AA).
  • ADA Title III — Americans with Disabilities Act, as interpreted by U.S. courts using WCAG 2.1 AA as the de facto benchmark.
  • EN 301 549 — the European Union harmonised accessibility standard.
  • WAI-ARIA 1.2 — Accessible Rich Internet Applications spec for semantic markup.

Features Already in Place

  • Keyboard-only navigation through every form field, including a "Skip to form" link that appears on first Tab.
  • Screen-reader announcements for required fields, validation errors, and progress changes (via role="alert", aria-live="polite", and role="progressbar").
  • Semantic landmark structure (<main>, labelled radiogroup / group wrappers for choice fields).
  • Proper <label> ↔ input binding via htmlFor/id so every input is unambiguously named.
  • aria-required, aria-invalid, and aria-describedby on text inputs to communicate state to assistive technology.
  • Visible focus indicators on every interactive element (default Tailwind focus-visible rings).
  • Right-to-left language support for Arabic, Hebrew, Persian, and Urdu.

Known Limitations

We will not claim full conformance we have not yet achieved. The following areas are actively being improved:

  • The signature pad and drawing canvas elements do not yet support keyboard-only entry.
  • The Ranked List drag-and-drop element does not yet expose ARIA grid semantics for keyboard reordering.
  • Some third-party embedded widgets (Calendly, Cal.com, SavvyCal, zcal, Mapbox, payment processor checkouts) follow their own provider's accessibility policies, not ours.
  • Custom themes set by form creators may not meet the WCAG 2.1 AA 4.5:1 text-contrast ratio. We surface contrast warnings in the builder but do not block publication.

Form Creator Responsibilities

Because Fantastic Forms is a no-code platform, the accessibility of an individual published form also depends on the choices its creator makes. We recommend creators:

  • Write clear question labels (avoid placeholder-only fields — placeholders disappear on input and aren't announced reliably).
  • Provide alternative text for any image elements they add.
  • Choose theme colors that meet the WCAG 4.5:1 contrast ratio for body text and 3:1 for large text and UI elements.
  • Avoid using color alone to convey meaning.

Reporting Accessibility Issues

If you encounter an accessibility barrier on Fantastic Forms, please tell us so we can fix it. We aim to acknowledge accessibility reports within 2 business days and address verified issues in our next release cycle whenever possible.

Contact us via with the subject line "Accessibility issue". Please include:

  • The page URL where you encountered the issue.
  • The assistive technology and browser you were using (e.g. NVDA + Firefox, VoiceOver + Safari).
  • A description of what you expected to happen and what actually happened.

Formal Approvals & Audits

This statement reflects our internal accessibility posture as of the date listed above. It has not been certified by an external auditor. We will update this page when third-party VPAT (Voluntary Product Accessibility Template) or independent audit conformance reports become available.