CycleFlow
Log inSign up

Legal

Accessibility Statement

Last updated: May 26, 2025

CycleFlow is committed to making its website and service accessible to everyone, including people with disabilities. We are working towards conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, which is the standard referenced by the Americans with Disabilities Act (ADA), the European Accessibility Act (EAA), and the UK Equality Act 2010.

Our current status

CycleFlow is partially conformant with WCAG 2.1 Level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard. We are actively working to address known gaps.

What we have done

  • Semantic HTML structure with proper heading hierarchy throughout the application
  • Full keyboard navigation support for all interactive elements in the dashboard
  • Visible focus indicators on all interactive controls
  • Sufficient colour contrast ratios for text on both light and dark themes
  • Dark mode support to reduce eye strain
  • Responsive layout that reflows correctly at 320px width and 400% browser zoom
  • Alternative text on all meaningful images
  • Form inputs labelled correctly with associated <label> elements
  • ARIA roles and attributes used where native HTML semantics are insufficient

Known limitations

We are aware of the following areas that do not yet fully meet WCAG 2.1 AA:

  • Rich text editor: The TipTap-based editor used to write changelog entries has limited screen reader support in some configurations. We are monitoring TipTap's upstream accessibility improvements.
  • Embeddable widget: The embeddable changelog widget may not be fully keyboard-navigable in all host environments. Improvements are planned.
  • Complex data tables: Some dashboard tables do not yet include full row/column header associations for screen readers.

Technical approach

CycleFlow is built with Next.js and React. We use Tailwind CSS for styling and Radix UI primitives for interactive components, which provide accessible-by-default behaviour including focus management and ARIA attributes. We test using keyboard-only navigation and screen reader spot checks with VoiceOver (macOS/iOS) and NVDA (Windows).

Feedback and contact

We welcome feedback on the accessibility of CycleFlow. If you experience barriers that prevent you from using any part of the service, or if you find that we do not meet an accessibility requirement, please contact us:

We aim to respond to accessibility feedback within 5 business days and to resolve issues within 30 days where possible.

Formal complaints

If you are not satisfied with our response, you may contact the relevant enforcement body in your jurisdiction:

  • United States: US Department of Justice, Civil Rights Division
  • European Union: Your national accessibility enforcement authority under the European Accessibility Act
  • United Kingdom: Equality and Human Rights Commission (EHRC)

Roadmap

We plan to commission a formal third-party WCAG 2.1 AA audit once the product reaches a stable feature set. Results and a remediation plan will be published here. Our goal is to reach full WCAG 2.1 AA conformance within 12 months of launch.