Skip to main content
Back to venven

Accessibility Statement

Last reviewed: October 12, 2026. Next scheduled review: January 2027.

The standard

VenVen is built and tested to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. That covers venven.io, the VenVen app operators use, and the pages and embedded booking forms that operators share with their own customers: booking pages, inquiry forms, quotes, contracts, and payment steps. VenVen is built to work with current versions of Chrome, Safari, Firefox and Edge, on desktop and phone, and with the screen readers built into those platforms.

How VenVen is tested

The October 2026 review included:

  • Automated WCAG 2.2 AA checks (axe-core) on every public page and every app page, at desktop and phone widths, run against the live site.
  • A code review of keyboard access, focus order and visibility, form labels and error messages, screen reader names and announcements, and motion.
  • Keyboard-only walkthroughs of the booking, inquiry, quote, contract and payment steps, plus reflow at 320 pixels wide, 200% zoom, and increased text spacing.

Issues found in that review were fixed before this statement was updated, apart from the items listed under Known limitations. The next review adds screen reader walkthroughs (VoiceOver and NVDA) of the booking and quote steps.

These checks are re-run after releases that change a page or a form, and the full review repeats at least every three months. This statement is updated after each review.

What is in place

  • Pages and forms are built to work with a keyboard alone, with a visible focus indicator on every control.
  • Dialogs keep keyboard focus inside while open, close with Escape, and return focus to the control that opened them.
  • Form fields are labelled; required fields and errors are stated in text and announced to screen readers, not shown by color alone.
  • Date, time and address pickers follow the standard ARIA patterns, so screen readers hear the chosen value.
  • Text is set to meet WCAG contrast minimums, including on booking pages and quotes that use an operator's own brand colors: VenVen adjusts a color that would be too light to read.
  • The one element that moves on its own, the booking preview on the home page, has a pause control, stops while hovered or focused, and does not play when the device asks for reduced motion. Other animation is turned off under reduced motion.
  • Status messages, such as saved changes and sent requests, are announced to screen readers.
  • Pages reflow on small screens and at 200% zoom without sideways scrolling.
  • Each page declares its language and has one main heading and a main content landmark, so screen reader users can jump straight to the content.

Known limitations

  • Services VenVen connects to are built and maintained by those companies: Stripe (customer payments), Polar (subscription checkout), Square and Google Calendar (optional operator integrations).
  • Operators add their own photos, menus and text to their pages. VenVen writes the image descriptions for the layouts it draws and uses an operator's photo captions as the descriptions for gallery photos. Text an operator writes is the operator's own.
  • Some charts on the operator dashboard are not yet fully described to screen readers. The key numbers are also shown as text.
  • The event day sheet, a PDF operators can download, is not tagged for screen readers. The same details are on the event page.

Book or get help another way

Anyone who cannot use a VenVen booking page, form or quote can reach the business directly, or contact VenVen, and the request will be completed by phone or email instead. There is no extra charge, and the same dates, prices and terms apply.

Report a barrier or request an accommodation

Include the page address, the device and browser or screen reader, and what happened, if you can. Every accessibility report gets a reply within 2 business days, and a fix or a working alternative as soon as possible after that.