Campaid · Accessibility

Accessibility at Campaid

What we have built, what we have not, and how to tell us when something does not work. Last updated August 6, 2026.

Our aim

Campaid is built for students, and students use the web in every way there is — with a screen reader, by keyboard alone, at 400% zoom, one-handed on a phone, or with motion turned off because it makes them ill. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA.

We want to be straight about the word “aim”. Plenty of sites this size claim full conformance; almost none have been audited. We would rather tell you exactly where we are, because a promise we cannot back is worth less to you than an honest one.

What is in place today

  • Keyboard navigation

    Every page starts with a “Skip to content” link, so you can jump past the navigation without tabbing through it. Pop-up dialogs keep keyboard focus inside them while open and return it when they close, so you cannot get lost behind a dialog.

  • Screen readers

    Status messages, errors and confirmations are announced rather than only shown — including when a form refuses to submit. Decorative icons and emoji are hidden from screen readers instead of being read aloud by name.

  • Colour and contrast

    Text is checked against the WCAG AA contrast minimums, and we treat a contrast regression as a bug to fix rather than a preference. Status is never communicated by colour alone — a paused listing says “paused”, it is not just a different shade.

  • Motion

    If your device is set to reduce motion, our animations respect that setting and stop moving.

  • Touch targets

    Buttons and controls are sized so they can be tapped reliably on a phone rather than requiring a precise press.

  • Structure

    Pages declare their language, use real headings and landmarks, and label form fields properly, so assistive technology can navigate by structure rather than guesswork.

What we have not done yet

  • We have not had an independent accessibility audit. Everything above is our own testing, so treat it as a good-faith description rather than a certification.
  • We have not tested every page with every screen reader and browser combination. If you use one and something does not work, telling us is genuinely the fastest way it gets fixed.
  • Some newer areas of the site have had less accessibility review than the main flows.
  • Files that other people upload — photos, screenshots of tickets — may not carry useful descriptions, because they come from other users rather than from us.

Tell us about a problem

If any part of Campaid is difficult or impossible for you to use, tell us. You do not need to know the technical name for the problem — “I can’t get to the pay button with my keyboard” is a perfect bug report. If it helps, tell us the page, the device or software you were using, and what you expected to happen.

Two ways to reach us

support@campaid.net (opens your email app)

Or use the feedback form on our homepage — no email app needed.

We reply within 5 business days. If something is stopping you from completing a payment or getting your money, say so and we will treat it as urgent.

If we cannot fix something quickly, we will tell you what the hold-up is and offer to help you finish what you were doing another way in the meantime.

Related