Skip to main content

Accessibility Statement

Last updated: April 27, 2026

What we build to

VenVen targets WCAG 2.1 Level AA. A lot of operators run their business from a phone in one hand at an event, so keyboard access, reduced motion, and screen reader support get tested against the real tools, not just the marketing pages.

Accessibility Features in VenVen

VenVen includes the following accessibility features built into the product:

  • Reduced motion support: All CSS animations and scroll-driven effects respect the prefers-reduced-motion media query globally. When the operating system preference is set, transitions, scroll reveals, and decorative motion are disabled automatically. No in-app toggle required.
  • Tab through any page and you get a consistent visible focus ring on buttons, links, inputs, and selects, so it's always clear which control is active.
  • Keyboard-accessible modals: All modals use a DialogWrapper component that traps keyboard focus inside the dialog, supports Escape to close, and returns focus to the triggering element on dismissal.
  • Semantic HTML and ARIA landmarks: Pages use proper heading hierarchy (h1 through h3) and semantic landmark elements (header, main, nav, footer) for screen reader navigation.
  • Minimum 44x44px touch targets: All interactive elements on mobile meet or exceed the 44x44px minimum touch target size recommended by WCAG.
  • Toast notifications with aria-live: Dynamic feedback (saves, errors, undo actions) is delivered through a toast system that uses aria-live regions so screen readers announce content changes without requiring focus.
  • Every form field has a real <label>; we never rely on placeholder text alone to say what a field is for.
  • Color never carries meaning by itself. Status indicators, errors, and categories always pair the color with a text label or icon.

Compatibility

We test VenVen in current Chrome, Safari, Firefox, and Edge. VenVen is built on standard, labeled form controls, so screen readers, magnification, and speech-recognition tools should work throughout; if one doesn't, tell us and we will fix it.

Known Limitations

We are actively improving accessibility. Known limitations include:

  • Some older PDF exports may not be fully accessible to screen readers.
  • Third-party integrations (Square, Google Calendar) may have varying accessibility levels outside our control.
  • Certain data visualizations on the analytics dashboard may not convey all information to screen readers yet.

If you encounter a barrier not listed here, please let us know so we can address it.

Feedback

We welcome your feedback on the accessibility of VenVen. Please let us know if you encounter accessibility barriers:

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

Formal Complaints

If you are not satisfied with our response to your accessibility concern, you may escalate your complaint by contacting us directly at support@venven.io with "Accessibility Complaint" in the subject line.