Skip to main content

Accessibility Statement

Last updated: February 25, 2026

Our Commitment

Formalingo is committed to ensuring that our platform is accessible to everyone, including people with disabilities. We believe that digital accessibility is a right, not an afterthought, and we work continuously to improve the experience for all users regardless of ability or technology.

Conformance Status

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. These guidelines explain how to make web content more accessible to people with disabilities.

Formalingo is partially conformant with WCAG 2.1 Level AA. We are actively working to identify and address gaps, and our accessibility improvements are ongoing.

Accessibility Features

We have implemented the following accessibility measures across the platform:

  • Semantic HTML with proper heading hierarchy throughout all pages
  • ARIA labels and landmarks for screen reader navigation
  • Keyboard navigation support for all interactive elements
  • Sufficient colour contrast ratios for text and UI components
  • Focus indicators visible on all interactive elements
  • Responsive design that works with browser zoom up to 200%
  • Alt text on all meaningful images
  • No content that flashes more than three times per second

Accessibility Widget

We have integrated the UserWay Accessibility Widget across all pages. You can activate it at any time using the accessibility button in the navigation bar. The widget provides tools including:

  • Screen reader optimisation
  • Keyboard navigation assistance
  • Contrast and colour adjustments
  • Text size and spacing controls
  • Pause animations
  • Reading guide and focus mode
  • Dyslexia-friendly font

Known Limitations

While we strive for full accessibility, some areas of the platform are still being improved:

  • The AI-powered form builder editor uses complex drag-and-drop interactions that may present challenges for keyboard-only users — we are working on keyboard-accessible alternatives.
  • Some third-party embedded components (such as payment processors and analytics) may not fully meet WCAG 2.1 AA standards; we raise accessibility requirements with those vendors.
  • Rich-text content fields may have incomplete ARIA descriptions in some contexts — this is being addressed in upcoming releases.

Technical Approach

Formalingo is built with React and Next.js and relies on the following technologies for accessibility:

  • HTML5 semantic elements
  • WAI-ARIA 1.2 roles, states, and properties
  • CSS media queries including prefers-reduced-motion and prefers-color-scheme
  • Focus management on dynamic content updates (modals, drawers, toasts)

Feedback & Contact

We welcome feedback on the accessibility of Formalingo. If you experience any barriers or have suggestions for improvement, please reach out:

We try to respond to accessibility feedback within 5 business days.

Formal Complaints

If you are not satisfied with our response, you may contact the relevant national accessibility enforcement body in your country. In the United States this is the U.S. Department of Justice (ADA). In the EU, national supervisory authorities handle complaints under the European Accessibility Act.