Skip to main content
Walkathon

Accessibility

Last audited:

Our target

Walkathon targets Web Content Accessibility Guidelines (WCAG) 2.2 conformance at level AAA on the public marketing surface, the sign-in flow, the campaign-creation wizard, and the public campaign pages. Where AAA isn’t achievable for a specific criterion, we document the exemption below.

Documented exemptions

The WCAG conformance rules allow specific criteria to be excluded where they can’t reasonably be met given the nature of the content. We exempt:

  • 3.1.5 Reading Level (AAA)for our Terms of Service and Privacy Policy pages. Legal text requires technical vocabulary that can’t be rewritten at lower-secondary reading level without losing precision. These pages meet AA on this criterion. All other text content (marketing, dashboard, wizard, campaign pages) aims at AAA.
  • 2.4.9 Link Purpose (Link Only) (AAA)for the “next” arrows in some lists. We surface the destination via accessible names and adjacent context; visually-only-presented arrows remain.

How we test

  • Automated: axe-core runs against every page in our Playwright end-to-end suite. New violations block the PR.
  • Keyboard: we test every interactive flow (sign in, wizard, refund, signup, log steps, kudos) using only the keyboard. All controls must be reachable, focusable, and have a visible focus style.
  • Screen reader: manual NVDA pass on Windows and VoiceOver pass on macOS per release for the surfaces above.
  • Reduced motion: we honour prefers-reduced-motion for animated counters and transitions.
  • Contrast: our palette helper enforces AAA contrast (7:1 for body text). The campaign-branding editor warns organisers when their chosen colours drop below AAA.
  • High-contrast theme: we provide a high-contrast theme that overrides palette colours with maximum-contrast values.

Known limitations

We’re aware of the following areas where we don’t yet meet our target:

  • Third-party Stripe Checkout pages aren’t directly under our control. Stripe targets WCAG 2.1 AA; we don’t guarantee AAA on those pages.
  • The browser’s native datetime-localcontrol doesn’t consistently meet AAA target-size requirements across all platforms. We’re evaluating a custom replacement.

Reporting an issue

If you find an accessibility issue, please tell us. We aim to acknowledge within 5 working days and to resolve issues with significant impact within 30 days. Contact details are in our footer.