Accessibility Statement

What published forms provide

• Every field is a native HTML control with a programmatic label; required state and validation errors are announced to assistive technology.
• Full keyboard operation: Tab/Shift-Tab between fields, Space/Enter on choices and buttons, no keyboard traps, visible focus rings.
• Multi-page forms keep a logical focus order between pages; progress is exposed as text, not colour alone.
• Themes: default themes meet the AA contrast ratio (4.5:1). Owners who customise colours are responsible for keeping contrast — we recommend checking with a contrast tool before publishing.
• Layouts reflow to 320px wide without horizontal scrolling and respect browser zoom up to 400%.
• No content flashes; animations respect prefers-reduced-motion.
• Anti-abuse checks use Cloudflare Turnstile, which normally completes without any visual puzzle.

Known limitations

• The drag-and-drop field palette in the builder also supports adding fields by click, but reordering by keyboard is limited today. Reordering via the field settings panel is the accessible path.
• The signature field requires pointer or touch input; owners should keep it optional or provide an alternative for respondents who cannot draw.
• File-upload previews and some third-party embeds (payments via Stripe Checkout, embedded videos) are governed by those providers' accessibility.
• Content that form owners write — question wording, images and their alt text, link text — is the owner's responsibility.

Compatibility

Published forms are tested with current versions of Chrome, Firefox, Safari and Edge, with VoiceOver on macOS and iOS, and with NVDA on Windows. Forms depend on JavaScript being enabled.

Feedback and alternative access

If you hit a barrier — as a respondent filling in a form or as an owner building one — tell us and we will fix it or provide the content another way. Include the form link and the assistive technology you use.

We aim to acknowledge accessibility reports within 2 business days.