Accessibility statement

Core tasks should be easy to use with clear navigation, plain language, and practical help.

We aim for accessible, predictable journeys across sign-in, bookings, venue discovery, and group participation.

Navigation and controls

Priority flows stay keyboard-complete, screen-reader-friendly, and consistent across products.

  • All interactive elements reachable via Tab / Shift+Tab.
  • Focus-visible outlines on every focusable control.
  • Skip-to-content link on every page.
  • ARIA landmarks used for major regions (main, nav, footer).

Support disclosure

Accessibility and support requests explain what is shared, who can see it, and what happens next.

  • Share-scope summary before confirmation.
  • Audience list before you confirm (event team, front-of-house, catering).
  • Support status visible on the pass view.

Arrival and day-of support

Travel guidance, backup access details, and quiet help options stay close when timing matters.

  • Pass view works offline-first with cached content.
  • BLE check-in is a silent tap — no interaction wall.
  • Support-escalation path reachable from the pass.

Feedback loop

When we find a gap, we fix the page or flow rather than expecting people to work around it.

  • Post-event fulfilment feedback captured per support dimension.
  • Issues are tracked so venues and product teams can improve the experience.
  • Accessibility gaps tracked as inclusion debt.

Visual and reading comfort

Colour contrast meets WCAG 2.2 AA ratios. A dyslexia-friendly mode is available that increases word-spacing, letter-spacing, and line-height for improved readability.

  • Text scales to 200% without horizontal scrolling.
  • prefers-reduced-motion media query respected.
  • prefers-color-scheme dark mode supported.
  • Dyslexia-friendly defaults: wider spacing, OpenDyslexic-compatible glyphs.

Conformance target

The platform targets WCAG 2.2 AA across the main journeys. Any gaps are logged, prioritised, and fixed in release work.

  • Success criteria: 1.3.1, 1.4.3, 1.4.11, 2.1.1, 2.4.3, 2.4.7, 2.5.8, 3.2.6, 4.1.2.
  • Audit cadence: quarterly automated + annual manual review.
  • Testing: axe-core CI gate on frontend changes + manual VoiceOver/NVDA sweep.